FirstData Nashville Auth Retail Transaction UML

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

Authorization Characteristics Indicator.
This field indicates the result of the Visa's evaluation of the authorization characteristics of a custom payment service transaction.

Identification number of the used application.

Returned with an amount less than the requested amount.

Alphanumeric value assigned by the bank to a merchant sale or cash advance that has received specific approval. The code is used as proof that the transaction has been properly approved.

Address Verification Response.
One character code indicating the response of the Address Verification process.

Space-fill in the 0100 original authorization request message. The value received in the 0110 original authorization response, must be submitted in the 0100 incremental request & 0400 reversal message and capture only transaction request message. The Issuer will respond with the 4-byte BankNET Date (MMDD).

Space-fill in the 0100 original authorization request message. The value received in the 0110 original authorization response, must be submitted in the 0100 incremental request & 0400 reversal message and capture only transaction request message. The Issuer will respond with the 9-byte BankNET Reference.

Acquirer Reference Data.

Contains values to be used by the "Acquirer" (First Data) to determine how to process the transaction. Currently only the first byte in the field is being used. The remaining positions are reserved for future use and should not be sent.

Note: This should only be used for host capture merchants. If this field is present for other merchants, the transaction could be rejected.

Network management information code that indicates the function of a particular 0800 Test Message.

A system-generated number is provided by the merchant and it uniquely identifies a transaction. It is ―echoed‖ back to the merchant in the host response messages.

Note: System Trace Number cannot be repeated for another Terminal ID of the same merchant for the same day.

This is the time stamp of the transaction, and as a Regulation E requirement it should be printed on the Debit Receipt given to a customer. It does not change on subsequent transactions (i.e., on debit reversals).

For POS terminals sending credit card transactions, this code identifies the month and day a transaction is sent. It must be POS terminal time and match the printed receipt.

This is the date stamp of the transaction and, as a REG-E requirement; it should be printed on the Debit/EBT Receipt given to a customer. It does not change on subsequent transactions (i.e., debit reversal).

Card Expiration Date.

Conditional — Mandatory for manual entry of Account number (Credit, Debit and EBT); Mandatory for Debit Reversals, and Void; optional for card-swiped transactions (YYMM).

This field expresses the expiration date (YYMM) for the card. It is included in both Track 1 and Track 2 data. The terminal must not store the track information, so the PAN is sent on all advice messages (i.e., adjust, off-line, etc.).

• Transactions associated with an expired card must be settled within four days, or the batch will be rejected.
• For Discover (JCB (US Domestic only), and Diners) recurring and Installment transactions the transaction must include a valid expiration date for the card being used in the recurring agreement with the merchant.
• For Debit and EBT Transactions, the requirement is only as to presence. If present it may contain expired dates or '0000' without issues.

A code that identifies the type of business or services conducted by the service establishment.

Primary Account Number.

Conditional — Mandatory for:

• Credit card authorizations, authorization and capture, and capture only for all transactions, both manual/swiped entry modes used during original authorization.
• EBT Voucher Clear Transactions and Debit PIN-less Transactions.
• Debit Reversal and Void.

Not included for check transactions message.

In the 0200 Financial Transaction messages for EBT Card, this field is mandatory if the Track 2 Data cannot be read.

Identifies the card member‘s account number. Unlike most numeric fields, the Primary Account Number is left-justified. In this case, the rightmost byte is padded with a ½ byte binary zero (e.g., a three-position field, X ‘03 12 30‘).

This field specifies how the Primary Account Number was entered into the terminal. The code is comprised of the POS Entry Mode Value and the PIN Capability Value

Card Sequence Number.

The Card Sequence Number is a number used to differentiate cards that have the same primary account number (PAN). Field 023 contains the Card Sequence Number in the range '000' to '099', right justified and left-padded with zeros. It is only used for transactions containing ICC System Data. For transactions containing ICC Data, the Card Sequence Number is mandated when the card product includes the Card Sequence Number in the criteria for uniquely defining a card. In this case, Field 023 must contain the Application PAN Sequence number (ICC tag 5F34), if present on the ICC. If ICC Tag 5F34 is not available (is not supplied by the card), Field 023 must be omitted.

This field identifies the acquiring host. This code will be returned on the host response.

This field describes the conditions at the POS location for a particular transaction.

A required code is used in conjunction with the message type to define the type of transaction that is by the terminal to the host.

Track 2 Data.

Contains the information encoded from a valid Track 2 magnetic stripe read. It includes information such as the Primary Account Number and Expiration Date. Entire Track Data must be forwarded intact (excludes Start Sentinel, End Sentinel and Longitudinal Redundancy Check).

1. On Debit Card transactions, this field is mandatory (with the exception of Debit Card PIN-Less transactions). Debit Card PIN-Less transactions are manually entered transactions.
2. On EBT transactions (Cash Benefit and Food Stamps), this field should be sent if available (If not available, manual entry is allowed).
3. On EBT Voucher Clear transactions, this field is not available.
4. On Debit and EBT Card transactions, Bit 45 (Track 1) should be off.
5. On a 0400 EBT reversal message, this field must match the original 0200 EBT request.
6. On a Credit Card 0400 reversal message, Track Data must not be included as Card Associations forbid the storage of track data.
7. On a 0400 (Debit) reversal message, this field must not be present.

Authorization only — For Credit and debit transactions (excluding Canadian Debit) the retrieval reference number can be any value based on the merchant‘s choosing (e.g. sequential tracking of transactions, fixed value etc.). The value submitted in the request message is then echoed back in response.

Authorization with capture — For Credit and debit transactions (excluding Canadian Debit), this is a unique 12-byte reference number assigned to a transaction by the merchant and returned in the response message.

Capture Only – For Credit card transactions the retrieval reference number must be the same value that was submitted in the original authorization request.

Canadian Debit — The POS terminal at the merchant‘s location generates the retrieval reference number and includes it in the transaction request. The host echoes the value back in the response. The terminal must ensure that the number is unique.

Reversals — In a 0400 (Debit/Credit) reversal request message, the retrieval reference number does not have to match the original 0100 (Credit) and 0200 (Debit) request. This is applicable to all transaction type (Credit, Debit inclusive of Canadian Debit).

The Authorization ID Response is the approval code assigned by the association, issuing bank, or Debit/EBT network.

The host response to a message to indicate the status of the transaction. The value returned in the authorization response is submitted in the capture only transaction request.

This field specifies the transaction amount, in the acquirer‘s currency.

This field contains a code that identifies a merchant terminal.

This field contains a code assigned to a merchant location.

Alternative Merchant Name/Location.

This field contains a number of sub-fields identifying the merchant‘s name, location and service entitlement number.

Note: Must be in upper-case letters.

The purpose of this field is to override information that is stored for the merchant on First Data‘s Merchant Master. Merchant name, City and State must be completely entered; otherwise the legal name in First Data‘s Merchant Master will be used. It is recommended for American Express and Debit transactions that the Street Address also be provided.

Additional Response Data. Contains the response to an Address Verification Only (AVS) request.

Conditional — If Bit 48 is used in the request message (0100, 0200), this field is returned in the response message (0110, 0210). For Host Capture merchants, if the transaction is a Capture only transaction (Bit 31 value of 2) and address verification was processed on the original authorization, the Address Verification Response Code must be presented in the 0100 message.

Additional Response Data.

Conditional — If Bit 48 is used in the request message (0100, 0200), this field is returned in the response message (0110, 0210). For Host Capture merchants, if the transaction is a Capture only transaction (Bit 31 value of 2) and address verification was processed on the original authorization, the Address Verification Response Code must be presented in the 0100 message.

Contains the response to an Address Verification Only (AVS) request.

First Data uses field 48 to communicate elements not included in the ISO 8583 specification.

Transaction Currency Code.

Can be used to specify the currency type associated with a transaction (e.g., 840=U.S. Dollar).

Note : Conditional — Mandatory for "multi-currency" merchants, but optional for merchants who use U.S. currency only.

Encrypted PIN Data.

Conditional — Mandatory for Debit Card transactions (with exception of Debit Card PIN-Less transactions).
Mandatory for EBT Cash Benefit transactions and mandatory for all EBT Food Stamp transactions (except for EBT Voucher Clear transactions).

Personal Identification Number (PIN) data as received from the PIN pad. The terminal is not itself a secure device, so it doesn‘t process the PIN data. The terminal simply passes the encrypted PIN data (cryptogram) as received from the PIN pad. On a 0400 message send eight bytes of Hex '0‘s for domestic DUKPT processing. The same format applies to Master Key processing.

For transactions where the PIN is verified offline (e.g. Interac chip) or not required (debit contactless transactions under the no PIN required‟ floor limit), a value of all F‟s (FFFFFFFFFFFFFFFF‟) should be populated in this field.

All new applications supporting Debit and EBT are required to use Derived Unique Key Per Transactions (DUKPT) key management between the point-of-sale and the first link where the PIN block is decrypted and re-encrypted at a Host Security Module. This means that in most situations Leased Line merchants will be required to use DUKPT key management, since the PIN block will be passed from the pointof-sale to the corporate host to the First Data host, where the First Data Host Security Module decrypts it. For DUKPT, Field 63 (Table 33) is required in addition to Field 52. Refer to page 4-82 for details concerning this table.

For any corporation that has its own Host Security Module, Debit/EBT transactions are required to use DUKPT key management between the point-of-sale and the corporate host to which the Host Security Module is attached. These transactions can then be transmitted to the First Data host during Master/Session Key management.

Data associated with Merchant Advice Code table received from the processor.

This field contains amounts associated with the transaction. For Debit card (with exception of Debit Card PIN-Less transactions) and EBT Cash benefit transactions, this field represents the ―Cash Back‖ amount. On a 0400 (Debit/EBT) reversal message, this field must match the original 0200 (Debit/EBT) request.

ICC Data.

ICC Data is a series of ―Tag/Length/Value combination for ICC card processing. The length of the field is the length of all data that follows the length (total length of field 55 minus 3). All information that follows the 3 digit BCD length of Field 55 should be considered binary data.

ICC Data is a series of ―Tag/Length/Value‖ combination for ICC card processing. The length of the field is the length of all data that follows the length (total length of field 55 minus 3). All information that follows the 3 digit BCD length of Field 55 should be considered binary data.

Refer to the specification of the provider for more information.

The merchant's postal/ZIP code must be left-justify and filled if less than 9 bytes.

This field is comprised of the POS Type (first four bits) and the POS Capability (last four bits) data elements. The POS Type describes the general category of terminal used for the transaction. POS Capability describes the data entry methods available at the POS location.

First Data Private Use Data Element.

First Data uses Field 63 to communicate elements not included in the ISO 8583 specification.

New merchants/VARS are required to use Bitmap Position 63. Existing merchants are advised to switch from Bitmap Position 62 to 63 as well, since Bit 63 provides access to additional tables supporting required/optional services.

This code identifies the month, day, hour, minute, and second a transaction is sent (MMDDhhmmss). This must be represented in GMT or Universal time.

Response code generated by Interac network system.

The Card Level Response Code field is required to be included in the Settlement records for Visa sale transactions that were electronically authorized. The Visa Compliance Table is sent in on the request message as a trigger to receive the Visa Compliance table in the response message.

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

Reference to the client.

For Visa the Customer Code/Customer Reference Identifier — Used by the customer to identify the purchase (e.g., the invoice number).

For Visa this field must be 12 digits.
For MasterCard and American Express the code that facilitates merchant/corporation communication and record keeping.
For MasterCard this field must be 17 digits.
For MasterCard Electronic Payment Transactions this value should represent the Invoice Number.

Note: Refer to Conditional Requirement Matrix for further detail.

Space-fill in authorization request message.
CVC Incorrect Indicator. An indicator, provided by the Issuer in the authorization response, to identify the presence of an invalid card verification code (CVC). If there is an error, the Issuer will respond with the 1-byte CVC Error Code (Y).

The result code of CVV2 verification.

Identification code of the datawire.

Applicable to Authorization only, and Authorization and Capture

Optional for Visa and MasterCard. Mandatory for American Express.

The postal or ZIP code of the "ship to" location. This is equal to the Ship from Postal/ZIP Code when the customer takes possession of the items at the merchant location.

Result of the mailing address verification.

Network ID.

Must match authorization response value.

A required code is used in conjunction with the message type to define the type of transaction that is by the terminal to the host.

System trace audit number (STAN).

Card Track Data Submitted at the Time of Auth.

Text displayed on the terminal corresponds to the response code

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

Indicates whether the private data field response is present in the request.

MAC value assigned to the transaction by a processor.

Data associated with MasterCard processing received from the processor.

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.

A code associated with the reason a recurring payment transaction has been declined.

Mandatory for MasterCard. Not applicable for Visa or American Express. The merchant‘s federal tax identification number.

Relevant key used for messages authentication.

Relevant key used for encryption of the message.

A code that defines the message type.

The value submitted for reversal and capture only request must mirror the value that was submitted in the 0100 initial authorization request.

Label that shows the network where the transaction was routed for authorization (e.g. ‘NYCE’, ‘PULSE’,’ STAR’, ‘Visa’, ‘MasterCard’ etc.)

Relevant key used for PIN encryption.

Space-fill in authorization request message.
Only if the American Express Indicator on the authorization request message (0100) is an ―X‖, Amex CAPN POS Data field will be returned in the response (0110), otherwise zero-filled.

Space-fill in authorization request message. If the entry mode has changed, the Issuer will respond with the 1-byte POS Entry Mode Change (Y).

Identification number of the provider.

For Visa the information in the field used by the merchant to identify the purchase (e.g., SKU number).
For MasterCard the code that the cardholder supplied to the merchant.
For American Express the customer reference number.

Indicates the status of the transaction. For details, refer to Bitmap 39 — Response Code on page 4-19.

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

Digital number that represents the specific code of the product/service.

Indicates whether security key update mechanism is activated.

Identificator of the CA key.

TransArmor Security Packet (SP) tags.

01 -Security Level.

TransArmor Security Packet (SP) tags.

02 - Encryption Type.

TransArmor Security Packet (SP) tags.

03 - Encryption Target.

TransArmor Security Packet (SP) tags.

04 - Key ID.

If the transaction includes encrypted data, this field contains encrypted card number, track data, etc.

TransArmor Security Packet (SP) tags.

06 - Token Type.

TransArmor Security Packet (SP) tags.

07 - Token.

TransArmor Security Packet (SP) tags.

10 - Provider ID.

TransArmor Security Packet (SP) tags.

11 - ExpDate.

Nothing is to be sent from the merchant. These fields are passed in the response.

Enumeration of possible sub requests available in the system.

Table DS – Discover (JCB (US Domestic only), and Diners) Compliance – Fixed Portion.

Refer to the specification of the provider for more information.

Additional Compliance Data.

For 0100 and 0200 authorization request processing, the fixed header portion of the ICC Table is sent in on the request message from the POS Device as a trigger that the device can receive the "EV" table in the 0110 or 0210 response message if applicable.

Refer to the specification of the provider for more information.

Table MC - MasterCard Qualification Data.

Refer to the specification of the provider for more information.

Last 4 Digits of actual Account number.

Last 4 digits of actual account number will be returned back in auth response when it’s available from association, merchant can use it for receipt-printing purpose instead of using payment token number.

AMEX token cryptogram data.

Required tag for AMEX token in-app transaction. (AMEX Digital Wallet) Hex-Binary representation of 20 bytes binary data.

AMEX token cryptogram data.

Required tag for AMEX token in-app transaction. (AMEX Digital Wallet) Hex-Binary representation of 20 bytes binary data.

Token Assurance Level.

Token Assurance Level will be returned back to merchants in auth response when it’s available from association.

This tag should be included in capture message, if available from auth response.

Table VI - Visa Compliance Field Identifier Table.

Refer to the specification of the provider for more information.

CPS/2000 Additional credit card Data.

Refer to the specification of the provider for more information.

MOTO/Bill Payment/Electronic-Commerce additional POS information.

Additional Account/Amount Information.

Type of account used.

• 00 - Not specified
• 30 - Credit Card Account — used for cash disbursement.

Additional Account/Amount Information.

Type of account used.

• 00 - Not specified
• 30 - Credit Card Account — used for cash disbursement.

Additional Account/Amount Information.

Type of account used.

• 00 - Not specified
• 30 - Credit Card Account — used for cash disbursement.

Additional Account/Amount Information.

Type of account used.

• 00 - Not specified
• 30 - Credit Card Account — used for cash disbursement.

Additional Account/Amount Information.

Type of account used.

• 00 - Not specified
• 30 - Credit Card Account — used for cash disbursement.

Additional Account/Amount Information.

Type of account used.

• 00 - Not specified
• 30 - Credit Card Account — used for cash disbursement.

Additional Account/Amount Information

Type of specified amount.

• 4S - Healthcare (Visa/MC only) - Qualified medical expenses (i.e. over-thecounter qualified medical items);
• 4T - Transit (Visa only) - Transit fare media such as commuter and parking passes, and mass transit vouchers and tickets;
• 40 - Cash Disbursement (Discover (JCB (US Domestic only), and Diners) Only) - Amount of Cash Back being requested;
• 4U - RX (Visa/MC only) - Sub-Total of Prescription RX;
• 4V - Vision (Visa only) - Sub-Total of Vision/Optical;
• 4W - Clinical (Visa only) - Sub-Total of Clinical;
• 4X - Dental (Visa only) - Sub-Total of Dental;

Additional Account/Amount Information

Type of specified amount.

• 4S - Healthcare (Visa/MC only) - Qualified medical expenses (i.e. over-thecounter qualified medical items);
• 4T - Transit (Visa only) - Transit fare media such as commuter and parking passes, and mass transit vouchers and tickets;
• 40 - Cash Disbursement (Discover (JCB (US Domestic only), and Diners) Only) - Amount of Cash Back being requested;
• 4U - RX (Visa/MC only) - Sub-Total of Prescription RX;
• 4V - Vision (Visa only) - Sub-Total of Vision/Optical;
• 4W - Clinical (Visa only) - Sub-Total of Clinical;
• 4X - Dental (Visa only) - Sub-Total of Dental.

Additional Account/Amount Information

Type of specified amount.

• 4S - Healthcare (Visa/MC only) - Qualified medical expenses (i.e. over-thecounter qualified medical items);
• 4T - Transit (Visa only) - Transit fare media such as commuter and parking passes, and mass transit vouchers and tickets;
• 40 - Cash Disbursement (Discover (JCB (US Domestic only), and Diners) Only) - Amount of Cash Back being requested;
• 4U - RX (Visa/MC only) - Sub-Total of Prescription RX;
• 4V - Vision (Visa only) - Sub-Total of Vision/Optical;
• 4W - Clinical (Visa only) - Sub-Total of Clinical;
• 4X - Dental (Visa only) - Sub-Total of Dental.

Additional Account/Amount Information

Type of specified amount.

• 4S - Healthcare (Visa/MC only) - Qualified medical expenses (i.e. over-thecounter qualified medical items);
• 4T - Transit (Visa only) - Transit fare media such as commuter and parking passes, and mass transit vouchers and tickets;
• 40 - Cash Disbursement (Discover (JCB (US Domestic only), and Diners) Only) - Amount of Cash Back being requested;
• 4U - RX (Visa/MC only) - Sub-Total of Prescription RX;
• 4V - Vision (Visa only) - Sub-Total of Vision/Optical;
• 4W - Clinical (Visa only) - Sub-Total of Clinical;
• 4X - Dental (Visa only) - Sub-Total of Dental.

Additional Account/Amount Information

Type of specified amount.

• 4S - Healthcare (Visa/MC only) - Qualified medical expenses (i.e. over-thecounter qualified medical items);
• 4T - Transit (Visa only) - Transit fare media such as commuter and parking passes, and mass transit vouchers and tickets;
• 40 - Cash Disbursement (Discover (JCB (US Domestic only), and Diners) Only) - Amount of Cash Back being requested;
• 4U - RX (Visa/MC only) - Sub-Total of Prescription RX;
• 4V - Vision (Visa only) - Sub-Total of Vision/Optical;
• 4W - Clinical (Visa only) - Sub-Total of Clinical;
• 4X - Dental (Visa only) - Sub-Total of Dental.

Additional Account/Amount Information

Type of specified amount.

• 4S - Healthcare (Visa/MC only) - Qualified medical expenses (i.e. over-thecounter qualified medical items);
• 4T - Transit (Visa only) - Transit fare media such as commuter and parking passes, and mass transit vouchers and tickets;
• 40 - Cash Disbursement (Discover (JCB (US Domestic only), and Diners) Only) - Amount of Cash Back being requested;
• 4U - RX (Visa/MC only) - Sub-Total of Prescription RX;
• 4V - Vision (Visa only) - Sub-Total of Vision/Optical;
• 4W - Clinical (Visa only) - Sub-Total of Clinical;
• 4X - Dental (Visa only) - Sub-Total of Dental.

Additional Account/Amount Information.

12 digits, with implied decimal relative to the currency code. In Auto-Substantiation transactions, this value reflects the qualified amount of the total purchase. For Discover (JCB (US Domestic only), and Diners) credit card cash disbursement transactions, this value reflects the cash portion of the total purchase amount.

Additional Account/Amount Information.

12 digits, with implied decimal relative to the currency code. In Auto-Substantiation transactions, this value reflects the qualified amount of the total purchase. For Discover (JCB (US Domestic only), and Diners) credit card cash disbursement transactions, this value reflects the cash portion of the total purchase amount.

Additional Account/Amount Information.

12 digits, with implied decimal relative to the currency code. In Auto-Substantiation transactions, this value reflects the qualified amount of the total purchase. For Discover (JCB (US Domestic only), and Diners) credit card cash disbursement transactions, this value reflects the cash portion of the total purchase amount.

Additional Account/Amount Information.

12 digits, with implied decimal relative to the currency code. In Auto-Substantiation transactions, this value reflects the qualified amount of the total purchase. For Discover (JCB (US Domestic only), and Diners) credit card cash disbursement transactions, this value reflects the cash portion of the total purchase amount.

Additional Account/Amount Information.

12 digits, with implied decimal relative to the currency code. In Auto-Substantiation transactions, this value reflects the qualified amount of the total purchase. For Discover (JCB (US Domestic only), and Diners) credit card cash disbursement transactions, this value reflects the cash portion of the total purchase amount.

Additional Account/Amount Information.

12 digits, with implied decimal relative to the currency code. In Auto-Substantiation transactions, this value reflects the qualified amount of the total purchase. For Discover (JCB (US Domestic only), and Diners) credit card cash disbursement transactions, this value reflects the cash portion of the total purchase amount.

Additional Account/Amount Information.

The 3-digit code defines the currency used in the amount field.

Additional Account/Amount Information.

The 3-digit code defines the currency used in the amount field.

Additional Account/Amount Information.

The 3-digit code defines the currency used in the amount field.

Additional Account/Amount Information.

The 3-digit code defines the currency used in the amount field.

Additional Account/Amount Information.

The 3-digit code defines the currency used in the amount field.

Additional Account/Amount Information.

The 3-digit code defines the currency used in the amount field.

Additional Account/Amount Information.

• C - Positive Amount
• D - Negative Amount

Additional Account/Amount Information.

• C - Positive Amount
• D - Negative Amount

Additional Account/Amount Information.

• C - Positive Amount
• D - Negative Amount

Additional Account/Amount Information.

• C - Positive Amount
• D - Negative Amount

Additional Account/Amount Information.

• C - Positive Amount
• D - Negative Amount

Additional Account/Amount Information.

• C - Positive Amount
• D - Negative Amount

For Visa the amount of state or provincial tax included in the transaction amount. The tax amount must be within 0.1 % and 22% of the transaction amount. Two (2) decimal places are implied and size can be 12 bytes.

For MasterCard the total amount of sales tax or VAT on the total purchase must be between 0.1% and 30 % of the total transaction amount; zeroes indicate that the card acceptor is capable of transmitting the tax amount and the tax amount is zero. Right justified and zero filled. Two (2) decimal places are implied and size can be 9 bytes maximum.

For American Express the amount of tax calculated or entered for the transaction. Two (2) decimal places are implied and size can be 12 bytes.

Note: Refer to Conditional Requirement Matrix for further detail.

Mandatory for Visa and MasterCard.

Visa

- 0 - No tax information provided.
- 1 - Local tax amount is provided.
- 2 - Item is tax exempt or non taxable (The Local Tax Amount [above] must be zero).

MasterCard

An indicator used to reflect sales tax capture and reporting:
- Y - Sales tax included in total purchase amount
- N - Merchant has ability to provide tax amount, but goods/services were not taxable
- Space - Sales tax not provided

Token code used for the transaction.

For payment token transactions, merchant should send in token requestor id when it’s available. It’s a required field for MasterCard card-on-file token transactions.

Token Requestor ID will also be returned/ echoed back to merchant in payment token response message when it’s available from association.

This tag should be included in capture message, if available from auth response.

Terminal will send X‘20‘ (spaces) in initial authorization message.
Transaction Identifier back in the authorization response.

Space-fill in authorization request message. If there is an error, the Issuer will respond with the 1-byte Transaction Edit Error Code.

URL adresses. For example, E-commerce URL address.

Space-filled for initial authorization message. The Issuer response will be sent for incremental authorizations and reversals.

VPAS (Visa Payer Authentication Service) response value.