Elavon EISOP Capture Retail Transaction UML

Represents capture/settlement transaction as it is defined in Elavon EISOP's realtime processing specification.

Required in order to qualify the transactions for Visa custom payment services rates.

If data is not present, spaces must be entered.

The code of authorization.
If no authorization code is received, spaces must be entered.

00 = Off-line by terminal (no on-line auth);
01 = On-line to acquirer;
02 = Voice (referral);
10 = EMV-compliant, Offline by terminal chip approved;
11 = EMV-compliant, On-line to acquirer;
12 = EMV-compliant, Voice (referral).

AVS result code returned from the card issuer.

N = No Match
The match is not exact because the post code and/or the addresses do not match.

U = Unavailable Address
Information is unavailable or the Issuer does not support AVS. Acquirer has representment rights.

F = Exact Match
The match is exact; both the address and the post code matches. No representment rights.

Banknet reference date returned on the original authorization response.

For MasterCard transactions: MMDD.
Otherwise spaces must be entered.

Must be present in combination with the next two fields: 'Financial Network Code' and 'BankNet Reference'.

Banknet reference number that is returned on the original authorization response.

For MasterCard transactions.
Otherwise spaces must be entered.

Last two digits must be space filled.

Card or bank account number of the client.

Only valid for UnionPay value received from UnionPay in the authorization response.

Format: MMDDHHMMSS
If data is not present, spaces must be entered.

Only valid for UnionPay value received from UnionPay in the authorization response.

Format: Julian Day
If data is not present, spaces must be entered.

Represents the amount of "cashback" operation which is not higher than the transaction-amount in the TDR.
Same currency as in the TDR is used.

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

Indicates whether the room reservation is confirmed.

The CVV2, CVC2, or CID result code.

Price of the booked room.

Date when the room check-in is set.

Date when the room check-out is set.

DBA city for the dynamic merchant of the transaction (if payment facilitator processing is used).

Left justified with trailing spaces.
For non-dynamic merchant information submitters spaces must be entered.

DBA country code of the dynamic merchant of the transaction (if payment facilitator processing is used).

Numeric ISO 3166.
Space filled for non-dynamic merchant information submitters.

Allows a merchant to dynamically change the “Doing Business As” (DBA) name on each transaction submitted to the host for authorization and settlement.

The use of the dynamic DBA (dDBA) field is restricted by Elavon and requires prior approval to participate in the program. Values that are sent in this field by merchants that are not approved for use of this field will be ignored by the host prior to authorization and the value currently “on file” with Elavon will be used.

Left justified with trailing spaces.
For non-dynamic merchant information submitters spaces must be entered.

Dynamic state code of the merchant.

DBA street address of the dynamic merchant of the transaction (if payment facilitator processing is used).

Left justified with trailing spaces.
For non-dynamic merchant information submitters spaces must be entered.

Sub-merchant ID allocated by the payment facilitator for the dynamic merchant of the transaction (if payment facilitator processing is used).

Numeric ISO 3166.
Space filled for non-dynamic merchant information submitters.

DBA ZIP code of the dynamic merchant of the transaction (if payment facilitator processing is used).

Left justified with trailing spaces.
For non-dynamic merchant information submitters spaces must be entered.

Reference to the entity that represents a group of Elavon EISOP Capture Retail Transaction objects that are settled together as a group within a single file.

Contains the card account number's expiration date. Used for key entered authorizations and terminal-based settlements only.

For MasterCard transactions.
Otherwise spaces must be entered.

Secondary identifier of the hotel folio that can be used to cross-reference records between UniPay and integrated systems.

Indicator that is transmitted from the card to the terminal in the response of GET PROCESSING OPTIONS command for the sake of being forwarded to the issuer.

Secondary amount of the transaction (e.g. cash amount) as provided by the terminal to the card.

Returned by the chip (ICC) in response to a “Generate AC” command.

Used to indicate the capabilities of the card to support specific functions within the application.

Counter maintained by the application in the ICC, indicates the number of transactions processed by the card application.

A distinguishing number used to separate cards with the same PAN. If data is not present, spaces must be entered.

Indicates the type of cryptogram and the actions to be performed by the authorization system.

Result of last cardholder verification procedure performed.

Contains the card application identification code for the card application from ISO 7816-5, selected by the terminal.

Unique and permanent serial number assigned to the IFD by the manufacturer.

Contains proprietary application data for transmission to the issuer in all transaction messages. Retrieved from the card.

Identifies the results of the Issuer Script Execution.

Identifies the results of the Issuer Script Execution.

Identifies the version number of updated application of the terminal.

Indicates the card data input, CVM, and security capabilities of the terminal.

Indicates the country of the terminal, represented according to ISO 3166.

Indicates the environment of the terminal, its communications capability, and its operational control.

Result of the different verification operations performed by the authorization system.

Authorization amount of the transaction as provided by the terminal to the card.

Describes the environment of the TRX. Derived from MCC.

Indicates the currency code of the transaction according to ISO 4217.

The local date when the transaction was authorized.

Counter maintained by the terminal that is incremented by one for each transaction.

Indicates the type of financial transaction, representing the first two digits of ISO 8583:1987 processing code.

Value provided by the terminal to provide variability and uniqueness to the generation of the application.

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.

Country code where the merchant is located (NUMERIC ISO 3166).

Required where merchant country code is US/CA.
If country code = 840 or 124, than record ‘TAR’ is required.

Important: the state or province code should be consistent for all transactions in the batch. Refer to the specification of the processor for more information.

Indicates the method used to capture the cardholder’s information for an MOTO/eCommerce or internet transaction.

If transaction source is equal to 02:
‘1’ - Mail-/Telephone Order
‘5’ - fully e-Commerce (*1)
‘6’ - attempt e-Commerce (*2)
‘7’ - Channel encrypted (*3)

If transaction source is not equal to ‘02’, spaces must be entered.

Name of the guest.

Secondary identifier of the network that can be used to cross-reference records between UniPay and integrated systems.

Number of guests in a party.

Specific identifier assigned by the processor.

The retrieval reference number returned from the Canadian debit gateway during an authorization attempt. Also, used in a Canadian debit void transaction.

If data is not present, spaces must be entered.

Required for Discover processing in the US/CAN and UnionPay in all countries. Assigned by the merchant to assist in identifying a specific card transaction.

STAN remains unchanged for the entire life cycle of the card transaction.
STAN in the settlement record must match what was submitted in the authorization request.
If data is not present, spaces must be entered.

Condition code of the track data.

Authorization amount of the transaction as provided by the terminal to the card for cryptogram generation. The maximum transaction amounts supported are currently $9,999,999.99 for Visa and MasterCard, and $99,999.99 for all others card associations.

ISO currency code used in the Foreign Exchange Rate message. Taken from the terminal initialisation table or EMV chip card.

The actual date of the transaction.

Transaction identifier that is returned on the original authorization response (returned in the authorization response message).

For Visa transactions, this field may include an identifier provided in the authorization message to facilitate linking of authorization and settlement records.

If data is not present, spaces must be entered.

Used to identify the transaction reference on the account that the balance is being transferred to for the loyalty transfer transaction. Merchant transaction reference field/ ROC-Text-1 (Diners customer reference 1).

The source of processing transaction.

The actual time of the transaction.

Indicates the type of a transaction, representing the first two digits of ISO 8583:1987 processing code.

Validation code returned on the original authorization response.

For Visa transactions, this information is be provided to the merchant as part of the authorization message. May include a code to determine the accuracy of the authorization date contained in the clearing record.

If data is not present, spaces must be entered.