Elavon EISOP Auth Retail Transaction UML

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

System Trace Audit Number (STAN).

Transaction date and time.

Expiration date of the credit card or bank account number.

PAN (Primary Account Number).

POS data code.

Function code.

Reason code.
The reason code identifying the decline.

Reconciliation date.

Reconciliation number.

Processing code.
Submitted on all Canadian debit transactions to indicate the transaction type.

Acquiring institution IC code.

Track 2.

Retrieval reference number.

Contains approval code for an approved transaction.

Note: If response code of the authorization is not equal to "AA" or “AP”, the content of this field is ignored.

Contains approval code for an approved transaction.

Note: If response code of the authorization is not equal to "AA" or “AP”, the content of this field is ignored.

Action code.

Total amount of the transaction.

Transaction amount.

Card acceptor terminal identification.

Card acceptor merchant ID.

Card acceptor location name and address.

Additional private data.

The Elavon Date and Time will be returned to the POS or partner host system in the event of an approval of a sale transaction. This data must be provided to the Elavon host in the event of a reversal of the aforementioned sale transaction. This sub-field must be populated irrespective of whether single or dual message processing is used.

The Elavon RRN field will be returned to the POS or partner host system in the event of an approval of a sale transaction. This data must be provided to the Elavon host in the event of a reversal of the aforementioned sale transaction. This sub-field must be populated irrespective of whether single or dual message processing is used.

The Elavon STAN will be returned to the POS or partner host system in the event of an approval of a sale transaction. This data must be provided to the Elavon host in the event of a reversal of the aforementioned sale transaction. This sub-field must be populated irrespective of whether single or dual message processing is used.

Additional private data.

Transaction currency code.
Represents transaction ISO currency code used in the foreign exchange rate message.

PIN data.

Used to indicate a secondary “cashback” amount associated with the transaction.

ICC data.

ICC data.

Reserved private data.

Reserved private data III.

Reserved private data III.
Authorization characteristic indicator.

Reserved private data III AVS result code.

Reserved private data III.

Reserved private data III CVV result code.

Reserved private data III.
Identification number of the purchased product.

Reserved private data III.

System Trace Audit Number (STAN)
Unique number of transaction. This value should be unique on the partner’s host system within a 24 hour period.

Reserved private data III.
Track data condition code.

Reserved private data III.
The code of the initial transaction. Provided by the processor.

Reserved private data III.

Reserved private data III.

Reserved private data III.
The CPS validation code returned on the original authorization response.

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

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.

ISO message type.

Reference to the entity that represents a group of real-time transactions which must be settled together.