EFT T Tech Batch Transaction UML

Represents EFT T Tech batch transaction.

Transaction Date (Time stamp not included)

We use value AUTH

Address information

Total amount of the transactions including discount and tax.

We use such values for this field:
DDA (when AccountClassifier is CHECKING),
Savings (when AccountClassifier is SAVING)

The number of each batch

Reference to the entity that represents real-time financial transaction.

Number of the customer's check.

We use such values for this field:
BUSINESS, PERSONAL

Customer's city

We use such values for this field:
PPD - for personal
CCD - for company

Collection service such as guarantee, charge back to merchant, NOC’s, etc

Company name

Customer's name

Reference to the entity that represents EFT T-Tech batch information.

Customer's email

Identifier of the object used for references; auto-incremented integer value.

Customer's last name

Code of Merchant Account to which instance of this object is attributed to. Depending on the context, Merchant Account Code field may contain either Merchant Code or Merchant Account Code.
The field is primarily used for data partitioning and data management, to make it easy to determine the ownership of a record within the database.

Populated with NOC changes

Populated with NOC changes

Populated with NOC changes

We use value S for this field

Customer's phone number

Date, when the return was received

This field will contain the description of the return based on the value Return Reason Code

This field will contain one of the standard codes used to describe the reason for returning the entry

Type code of return. We use R (return) or C (notification) values

Customer's state

Transaction Date - date, when the transaction was created

Transaction Id. The number can rollover naturally but should not be reset to a starting value for each transmission

Transaction Code

This field identifies the transaction type. We use values:
Credit, Debit

ZIP or postal code of the mailing address.