First Data Compass Auth Retail Transaction UML

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

Contains the credit card account number which identifies the customer. The account number is left justified with trailing spaces.

This action tells First Data what service to perform on the transaction.

We use:
DR - Refund Auth Reversal (PINLess Debit)
PR - Purchase Auth Reversal (PINLess Debit)
AR - Authorization Reversal (Amex, MasterCard, Visa, Discover, JCB, GoogleCheckout, PayPal, ValueLink)
RA - Refund Auth (PINLess Debit)
PA - Purchase Auth (PINLess Debit)
AU - Authorize (Credit Card, Alt Pay, ValueLink)

Accountholder’s address information

Amount of the authorization. 2 decimal implied. Minimum amount for all card types is $0.01 U.S. dollars* (or established international currency equivalent), but no greater than the established Transaction Division limit. The default is $99,999.99

Identification number of the used application.

Authorization code of the approved, original, authorized transaction. This field cannot be blank or the transaction will reject with Response Reason Code 262 (Authorization Code/Response Date Invalid).

Response to address verification request.

Reference number the biller (merchant) uses on his system to identify this customer

Used to validate the presence of a card security value.

We use:
1 – Value is present (DI, MC, MD, or VI)
“ ” – Blank, indicator not sent (AX, MC, MD)

CVV code of the credit card.

CAVV code of the card.

This field will be populated for any Verified by Visa transaction.
It is used during authorization processing to verify that authentication, or attempted authentication, was performed. The Issuer receives the authorization request and validates the CAVV and responds with a CAVV response code, as well as an approval or a decline of the authorization. If the CAVV does not match, the Issuer should decline the transaction.

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

Accountholder’s city.

Unique value, that identifies the transaction.

This value is calculated by the gateway, according to the processor's specification rules. This value is taken into account by the processor on the communications layer.

Accountholder’s country code.

Card Security Value Response Code returned by the card Issuer in response to a card security verification request.

Current Balance

Item Description (optional). Left justified/space filled.

Notes: First Data will not pass the full 38 bytes of this field.

Identifier of the merchant. Assigned by the processor.

Assigned and provided to merchant by First Data. First Data assigns a unique Division Number to process each international currency. A single Division Number can support different transaction types and methods of payment in the same currency.

Indicates transaction token status.
Possible values:
PAN – TransArmor token request (or on response if tokenization failure and PAN masked;
TOK – TransArmor token supplied.

Expiration date of the associated credit card.

The tokenized value of Account Number.

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

Indicates the number of positions submitted for the following field

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.

City of the merchant's postal address.

Country code of the merchant's postal address.

ZIP code of the merchant's postal address.

Region code of the merchant's postal address.

Street of the merchant's postal address.

Identifier of the merchant. Assigned by the processor.

Method of Payment (MOP) defines the MOP associated with this transaction.

Method of Payment (MOP) defines the MOP associated with this transaction.

Accountholder’s name (asterisk should precede last name).

A value composed of any alpha, blank, digit, or punctuation combination that will be returned in the transaction response. This field will tie the merchant’s request to the First Data response.

Determines approval functionality for pre-paid/gift card authorizations.

Valid values for American Express:
Y – Transaction is not declined if authorization amount is greater than the current balance
N – Transaction is declined if authorization amount is greater than the current balance

Valid values for Discover:
Y – The sale amount can be partially approved but the cash back amount cannot be partially approved.
N – Merchant does not support partial authorization. Partial authorization not allowed for both sale amount and cash back amount.

Valid values for Visa/MasterCard/MasterCard Diners:
Y – Attempt a partial authorization if allowed for the account.
N – Do not attempt a partial authorization.

Accountholder’s postal code.

Field Recurring payment advice code (MasterCard/MasterCard Diners Only) has such valid values:
01 – New account information available. Obtain new account information.
02 – Try again later. Recycle transaction in 72 hours.
03 – Do not try again. Obtain another type of payment from customer.
21 – Do not try again. Issuer has blocked recurring payment transaction. Default space filled

Approved amount. Partial authorization is done and redemption amount is returned if authorized amount > available balance.

Date of approved, original, authorized transaction. YYMMDD format.
Response date must be current or prior date or the transaction will reject with Response Reason Code 262 (Authorization Code/Response Date Invalid).

Description of the response code

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

Accountholder’s state.

Amount of surcharge

Identifier of the merchant. Assigned by the processor.

Track data of the swipe card associated with the transaction.

Terminal identification – code identifying the balancing features available to the POS from the Host.

Identifier of the terminal. Assigned by the processor.

Merchant Specific Token Value issued by First Data.
This Format record will be returned on all TransArmor submissions.

Total transaction amount, including surcharge (if any)

Third Party Processor ID is mandatory on all Authorization requests submitted by Third Parties who have been issued one by First Data.

If you were assigned a Third Party Processor ID, you are required to send this additional format record.
If you were not assigned a Third Party Processor ID, this record should not be sent.

Trace number returned from debit vendor

Track that was read.

Valid values: 1 – Track 1 2 – Track 2

Describes the circumstances under which the transaction takes place. Default space filled.

We use:
1 – MOTO Indicator – Single Transaction Mail/telephone order: designates a transaction where the cardholder is not present at a merchant location and consummates the sale via the phone or through the mail. The transaction is not for recurring services or product and does not include sales that are processed via an installment plan.
2 – MOTO Indicator – Recurring Transaction: Designates a transaction that represents an arrangement between a cardholder and the merchant where transactions are going to occur on a periodic basis.
3 – MOTO Indicator – Installment Payment: Designates a group of transactions that originated from a single purchase where the merchant agrees to bill the cardholder in installments.
7 – ECI Indicator – Channel Encrypted Transaction: Designates a transaction between a cardholder and a merchant consummated via the Internet where the transaction includes the use of transaction encryption such as SSL, but authentication was not performed. The cardholder payment data was protected with a form of Internet security, such as SSL, but authentication was not performed.
R – Retail Indicator – designates a transaction where the cardholder was present at a merchant location. If an “R” is sent for a transaction with a MOTO Merchant Category Code (MCC) the transaction will downgrade.

Datawire address where the transactions are sent to.

Identifier of the merchant. Assigned by the processor.