Elavon Capture Retail Transaction UML

Elavon specific low-level representation of Retail Transaction produced by Forward Transformation Process within Settlement Process.
During Generation Process, Elavon specific interchange message is generated from this object for settlement. Consequently, all fields of the object are mapped into message segments/elements.

This value is used to facilitate transaction routing on Elavon.

0 = Manually entered transaction originated at a device capable of reading track 1 or 2
1 = Inquiry originated at a track 1 magnetic stripe reading device (capable of reading track 1 or 2 data)
2 = Inquiry originated at a track 2 magnetic stripe reading device
3 = Inquiry originated at a Proximity payment reading device
4 = Inquiry originated at a MICR device

Total amount of the transactions including discount and tax. The transaction amount in the cardholder’s currency in 9(10)v99 format.

This field contains the Approval Code for an approved transaction.
Note: If the Response Code on the auth. is not equal to "AA" or “AP” the contents of this field are ignored.

This value is used to indicate the source for the authorization response. The values in this response message are subject to additions.

For On-Line transactions, the codes are supplied by the Issuer and are returned by Elavon in the response message for all on line approvals
For Off-Line transactions, this is a one character field in the list below contains the Authorization Source code:

9 = No Authorization Source Code. This is used for non-authorized transactions, such as Credit Card Returns
E = Off-Line Approval. This is used when the approval code is manually entered, such as on a Referral or Force Transaction
6 = Off-Line approval, POS generated the approval.

This value contains the address verification response code returned in response message as a result of an AVS Request. It is also a required value for a terminal-based settlement, if returned in the authorization response.

This field is used to indicate to the POS which transactions should be captured in the local Shadow file.

0 = Do not Capture – Authorization Only
1 = Capture Transaction in Shadow File (EDC)
2 = Capture Transaction in Shadow File (EDC)

This value is used for Debit Returns to indicate that the Debit Purchase is in the current batch.

The credit card number.

This field represents the expiration date of the card used in the transaction. Usually printed on it's front side.

Format: MMYY.

This field is used to indicate the method used to obtain / verify the cardholder’s identity.

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

This field is used to pass additional data for specific industries and/or market segments.

This value contains the Card verification response code returned in Authorization Response. It is also a required value for a terminal-based settlement message, if returned in the authorization response.

M = Match
N = No match
P = Not Processed
S = Issuer indicates that CVV2 data should be present on the card, but the merchant has indicated that the CVV2 data is not present on the card (Visa Only)
U = Issuer not certified or registered to process card verification

This is a unique code that is used by the Merchant to denote the specific parsing rules for the merchant defined data that is contained in the Format Data field.

The Format Code field is used to denote different parsing structure for this field, if necessary.

000 = ECS Data – Format A
001 = ECS Data – Format B
002 = ECS Enhanced Transaction Data
003 = POS Logistics – Equipment Data
004 = POS Logistics – Statistics Data

This is a unique code that is used by the Merchant to denote the specific parsing rules for the merchant defined data that is contained in the Format Data field.

This field contains information in first type of format.

This is a unique code that is used by the Merchant to denote the specific parsing rules for the merchant defined data that is contained in the Format Data field.

This field contains information in third type of format.

This is a unique code that is used by the Merchant to denote the specific parsing rules for the merchant defined data that is contained in the Format Data field.

This field contains information in second type of format.

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

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.

Original amount authorized for this transaction in 9(8)v99 format, or the amount of cashback for debit card transaction.

This data will be as received during the original authorization processing. It will not be present for off line transactions. This is a “retain and return” value for terminal-based settlement messages.

The actual date of the transaction.

The actual time of the transaction.