Elavon4 Global Capture Retail Transaction UML

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

Contains the credit card account number which identifies the customer. The account number is left justified with trailing spaces. Visa’s authorization network record returns the cardholder account number in field 2. The cardholder account number must contain 13, 16 or 19 digits with the last digit being a mod-10 check digit.

ACI (Authorization Characteristics Indicator) is applicable to Visa transactions only. ACI is a code assigned by the Visa authorization system to reflect the authorization characteristics. This field was formerly known as the Payment Service Indicator.

Chip transaction field – Tag 5F24 – captures the expiration date which is imbedded within the chip.

Chip transaction field – Tag 82 – provides a series of indicators that reflect the specific functions supported by the chip card account.

Chip transaction field – Tag 9F26 – contains chip information passed from the chip to the terminal to validate the chip. This information must be captured and passed in the settlement.

Chip transaction field – Tag 9F36 – contains the count (the counter increments by 1 each time a transaction is initiated) of the transactions performed within the application.

The approval code is a series of alpha/numeric characters assigned by the credit card company to validate approval of a transaction. This field is also known as the authorization code. If no value is entered, zeroes or spaces are accepted; however, in order to qualify for Association incentive rates, the authorization code from the authorization response record must be moved to this field.

Chip transaction field – Tag 5F2A – contains the currency code the transaction was authorized in.

Chip transaction field – contains the date transaction was authorized on.

Applicable to Visa transactions only –authorization response code is a code that is returned by Visa in the authorization response message (usually 00) indicating approval of a transaction. This field may be spaces if a value is not transferred from the Visa authorization response record field 39.

Contains the source of the authorization.

If Multi-Currency or DCC transaction, the authorized amount field should contain the amount which was authorized and must equal the cardholder amount.

If NOT Multi-Currency or DCC transaction, the authorized amount should contain the amount which was authorized and must equal transaction amount keeping in mind the below scenario for U.S. processing.

The authorized amount field must contain the total amount authorized for all transactions approved simultaneously with a single approval code. This field is required to qualify for Association incentive rates. This field may be space-filled if the authorized amount is not available.

If the merchant participates in surcharging, the authorized amount will also include the surcharge amount if one is assessed.

Example for the airline industry: If four tickets for $400 each are authorized simultaneously, the authorized amount for all four transactions will be $1,600.

When a credit card company’s Address Verification Service (AVS) is utilized, this field will contain the code used by the credit card company to respond to the address verification request. This field may be spaces if a value is not transferred from the authorization response record.

MasterCard transactions only – the Banknet date is the date the transaction was authorized through Banknet. The format of this field is MMDD. This field is required to qualify for MasterCard incentive rates.

MasterCard transactions only – assigned by MasterCard to each authorization message. The Banknet Reference Number contains the financial network code, a unique identifying number and the identification for the MIP that generated it. This field is required to qualify for MasterCard incentive rates.

Chip transaction field – contains the number assigned to a specific card when two or more cards are associated with a single account number.

Contains and identifier which indicates the type of card used.

The cardholder ID method indicates how the cardholder was identified. This field is required to qualify for Visa/MasterCard incentive rates.

Contains the amount of cash back given to the cardholder at the time of the transaction. This amount cannot be higher than the transaction amount.

Contains the amount of cash back given to the cardholder at the time of the EMV transaction. This amount cannot be higher than the transaction amount.

The cardholder activated terminal level indicator indicates the transaction took place at a self-service terminal used for transactions in an unattended POS situation. Values in this field will vary depending on association and environment.

NOTE: If the CAT code field is not applicable to the transaction type the field must contain a space

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

Chip transaction field, Visa only – contains a value indicating what the condition the transaction occurred in. In certain situations the transaction failed chip validation and falls back to magnetic stripe processing.

Used for transaction level processing (MPS2 & 3 international platforms) and contains the country code where the transaction originated from. The value in this field is NOT used for batch level processing (MPS1 US and Canadian platform).

Chip transaction field – Tag 9F27 – indicates the type of cryptogram and the actions to be performed by the authorization system.

Chip transaction field – Tag 9C – indicates the type of financial transaction.

A three character code which indicates the currency represented in the transaction. This field may be zeros however, is required to match the authorized response record to qualify for Visa Customer Payment
Services (CPS) incentive rates. The Visa authorization system places this information in field 49.

Chip transaction field – Tag 9F34 – contains the result of the cardholder verification procedure.

CVV2 verification result field.

Contains information from the point of sale and is primarily used for MasterCard transactions.
For All other card brand transactions this field should be space filled.

MasterCard transactions only – DE22 Point of Service Data Code is a series of codes that identify terminal capability, terminal environment and point of interaction security data. It identifies special conditions that are present at the time a transaction occurred at the point of interaction. The information in DE22 must be passed unchanged from auth to clearing. DE22 contains 12 sub fields as described below.

Contains the network identifier for PIN based Debit cards.

Contains the switch settlement date for PIN based Debit cards in MMDD format.

Chip transaction field – contains the card application identification code for the card application from ISO 7816-5, selected by the terminal.

Chip transaction field – contains information indicating the type of the device used at the terminal for contactless transactions and is primarily used for MasterCard transactions. For all other card brand transactions this field should be space filled.

Electronic Commerce Indicator (ECI) = A VisaNet code that identifies a transaction that is conducted over the Internet or other network using a cardholder access device.
Mail Order Telephone Order (MOTO) = The purchase of goods or services where the cardholder is not present at the point of sale; the purchase is a result of a mail order, telephone order, fax order and so forth.

Reference to the entity atht represents Elavon4 Global retail file batch information.

Contains the month and year (MMYY) after which the credit card account number is no longer valid. If the expiration date is not available, this field may be zero filled.

Chip transaction field – Tag 9F6E – the form factor indicator defines the type of consumer device used to conduct the transaction. The field is conditional, however if information is passed it must be carried throughout the transaction (auth and settle).

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

Serial number of device interface.

Chip transaction field – Tag 9F10 – contains information the issuer wants to pass to the chip. The field is conditional, however if information is passed it must be carried throughout the transaction (auth and settle).

Issuer Script Results Part 1.

Issuer Script Results Part 2.

The Associations have assigned specific Merchant Category Codes (MCC) for merchants according to the operating regulations. If this field is not filled by the merchant, Elavon will insert the appropriate Merchant Category Code from its accounting system.

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.

Contains the merchants 'doing business as' (DBA) name.

Discover transactions only – contains a unique ID assigned by Discover Network at the time of the authorization response.

Installment transaction field – contains the amount a customer put down as a deposit on a transaction.

Contains the name of the travel agent or ticketing location where the transaction took place.

Required to qualify for Visa/MasterCard/Discover incentive rates. It occupies positions 1-2 of field 22 on the Visa authorization system. Refer to the specification of the processor for detailed information.

Indicates the capability of the terminal.

Applicable to Visa transactions only - assigned to U.S. and Canada regions identifying the type of card being used (the product). This value is passed in the authorization response message in field 62.23 Card Level Results if authorized through an MDEX. If transaction is authorized through another means, check with the authorization vendor to understand where the product id will be passed. The value received in this field must be passed in the settlement record, unchanged. This field is required to qualify for Visa incentive rates.

The purchase ID format indicates the format of additional identifying information for purchases, such as order number or invoice number, etc.

The purchase identifier is used to send information identifying the purchase to the issuer and cardholder. It indicates the type of identifying information (order number, invoice number, hotel folio number, car rental agreement number, text description, etc.).

Populated by the merchant for their use to assist with finding original documents, and for chargebacks. Elavon will include the reference code data on copy retrieval requests or chargeback forms.

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

Retrieval reference number.

Contains the amount of sales tax on the transaction. This field is required for certain interchange incentive rates.

Contains a sales tax indicator relating to the transaction. This field is required for certain interchange incentive rates.

Visa only – contains a value which identifies if a transaction meets Visa’s spend requirement defined by the Visa region. This field should be populated as a straight pass thru from authorization to clearing/settlement. The Spend Qualified Indicator is located in field 62.25 of the authorization response record.

Contains the two digit abbreviation for the state (if US) or province (if Canada) for the transaction.

Discover transactions only – This value is assigned by the Merchant to assist in identifying a specific card transaction. The STAN remains unchanged for the life of the card transaction. The STAN in the settlement record should match what was submitted in the Authorization Request.

Chip transaction field – contains the EMV Version of the Terminal.

Chip transaction field – Tag 9F33 – indicates the card input data, the Cardholder Verification Method and the security capabilities that are supported by the terminal.

Chip transaction field – Tag 9F1A – contains the country code of the country where the terminal is located.

Contains the terminal serial number or means of identifying the terminal for merchant locations with multiple terminals.

Chip transaction field – Tag 9A – contains the terminal transmission date from the Chip reader, format YYMMDD where YY indicates the year, MM indicates the month, and DD indicates the day.

Chip transaction field – Tag 9F35 – contains the terminal type which indicates the environment of the terminal, its communications capability, and its operational control.

Chip transaction field – Tag 95 – contains a series of indicators from the terminal perspective. The terminal records the results of offline and online processing by setting a series of indicators in this field.

Installment transaction field – contains the total installment amount.

Discover transactions only – The track data condition code field identifies the condition of the Track Data submitted in the authorization request. This field is required for association incentive interchange rates.

If the merchant is utilizing Dynamic Currency Conversion (DCC), the transaction amount field contains the amount of the transaction in the transaction currency before DCC is applied.

For all other types of transactions (i.e., all transactions except DCC), the transaction amount field contains the amount of the transaction in the local currency. This is the transaction amount that will be processed by Elavon to the Card associations.

The transaction amount is a required field. 2 decimals are implied for US and Canadian transactions.

The transaction amount must include the surcharge amount if one is assessed.

Chip transaction field – Tag 9F53 – indicates the type of transaction being performed.

Contains the numeric value for the currency code for the transaction.

The date of sale or refund in the format YYMMDD where YY denotes the year, MM denotes the month, and DD denotes the day.

Visa and Amex transactions – this field must include an identifier provided in the authorization message to facilitate linking of authorization and settlement records. This field is required for Visa incentive interchange rates. All other card brands – this field should be space filled.

Contains the merchant transaction reference information. This information is also referred to as the Record of Charge (ROC). The information in this field will be used to investigate any transaction level inquiries. This field is a user defined optional field. ROC information is at a transaction level and is returned to the merchant in the EPA file.

Chip transaction field – Tag 9F41 – contains the sequence number assigned to the transaction. The transaction sequence counter is a counter maintained by the terminal that is incremented by one for each transaction.

Contains the local transaction time in the format HHMMSS where H indicates the hour, M indicates the minute, and S indicates the seconds. The local transaction time is in the time zone the merchant is located in.

Used to differentiate between debit (sale) and credit (refund) transactions as follows:

• 05 = Sale
• 06 = Refund

Installment transaction field – contains a value indicating the type of installment, issuer or acquirer.

MasterCard transactions only – the UCAF Collection Indicator is present on Secure Code e-commerce transactions only indicating the type of participation.

Chip transaction field – Tag 9F37 – this field contains the number used in the generation of the cryptogram for chip transactions. It provides variability and uniqueness to the cryptogram.

Visa transactions only – validation code is a unique value that Visa includes as part of the authorization response for CPS transactions to ensure that key authorization fields are preserved in the clearing record.