Field Name |
L |
Position |
F |
S |
Remarks |
|||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Record Type |
3 |
1-3 |
A |
M |
Always TDR |
|||||||||||||||
Data Record Sequence Number |
9 |
4-12 |
N |
M |
Increment by 1 per data record |
|||||||||||||||
Card Number |
19 |
13-31 |
A / N |
M |
|
|||||||||||||||
Expiry Date |
4 |
32-35 |
N |
M |
MMYY (Field 4 of Track 2 or Tag 5F24 without DD) ZAPP: populate as 0000 |
|||||||||||||||
Transaction Amount |
13 |
36-48 |
N |
M |
Two implied decimal positions. Right justified and zero-padded. 27.00 EUR is represented as 0000000002700 100 JPY is represented as 0000000010000 100.000 KWD is represented as 0000000010000 |
|||||||||||||||
Transaction Type |
2 |
49-50 |
N |
M |
Valid values:
Diners supported from November 2020. |
|||||||||||||||
Transaction Source |
2 |
51-52 |
N |
M |
Transaction Source Value Valid values:
|
|||||||||||||||
Authorisation Code |
10 |
53-62 |
A |
M |
If no authorisation code is obtained then the field must be padded with spaces |
|||||||||||||||
Authorisation Source |
2 |
63-64 |
N |
M |
Indicates the source of the authorisation. Offline Authorisation / Non-Authorised Source Codes Valid values:
Acquirer / Issuer Authorisation Source Codes Mandatory where transactions are approved outside of the Elavon network. Valid values:
Authorisation via APM Valid value:
Space-fill if not applicable / not available. Please note values 00, 01, 02 are deprecated from version 2.72. |
|||||||||||||||
Transaction Currency |
3 |
65-67 |
N |
M |
Transaction currency code (NUMERIC ISO 4217) (in accordance with the THR Currency settings) |
|||||||||||||||
Merchant Country Code |
3 |
68-70 |
N |
M |
Country code where the Merchant is located (NUMERIC ISO 3166) |
|||||||||||||||
Transaction Date |
8 |
71-78 |
N |
M |
YYYYMMDD Note: must be the same as the authorisation date. |
|||||||||||||||
Transaction Time |
6 |
79-84 |
N |
M |
HHMMSS or file creation time |
|||||||||||||||
Transaction Reference |
30 |
85-114 |
A |
O |
Merchant transaction reference field (feeds to ROC text) / ROC-Text-1 (Diners Customer Reference 1) ZAPP Transactions: Settlement Retrieval ID (sale transactions) RefundTRID (refund transactions) |
|||||||||||||||
State/Province Code (Merchant) |
2 |
115-116 |
A |
C |
Mandatory where Merchant Country code is US/CA. If Country-Code = 840 or 124 then ‘TAR’ is mandatory. Important: The State or Province code should be consistent for all transactions in the batch. |
|||||||||||||||
Application Cryptogram |
16 |
117-132 |
A |
C |
Cryptogram returned from the ICC in response to the GENERATE AC command (EMV TAG 9F26) |
|||||||||||||||
Cryptogram Information Data |
2 |
133-134 |
A |
C |
Indicates the type of cryptogram and the actions to be performed by the authorization system (EMV TAG 9F27) |
|||||||||||||||
Issuer Application Data (IAD) |
64 |
135-198 |
A |
C |
Contains proprietary application data for transmission to the issuer in all transaction messages. (EMV TAG 9F10) |
|||||||||||||||
Unpredictable Number |
8 |
199-206 |
A |
C |
Value provided by the terminal to provide variability and uniqueness to the generation of the application (EMV TAG 9F37) |
|||||||||||||||
Application Transaction counter (ATC) |
4 |
207-210 |
A |
C |
Counter maintained by the application in the ICC, indicates the number of transactions processed by the card application (EMV TAG 9F36) |
|||||||||||||||
Terminal Verification Results |
10 |
211-220 |
A |
C |
Result of the different verification operations performed by the authorization system (EMV TAG 95) |
|||||||||||||||
Transaction Date |
6 |
221-226 |
A |
C |
The local date that the transaction was authorized (EMV TAG 9A) |
|||||||||||||||
Transaction Type |
2 |
227-228 |
A |
C |
Indicates the type of financial transaction, representing the first two digits of ISO 8583:1987 Processing code (EMV TAG 9C) |
|||||||||||||||
Transaction Amount |
12 |
229-240 |
A |
C |
Authorization amount of the transaction as provided by the terminal to the card (EMV TAG 9F02) |
|||||||||||||||
Transaction Currency Code |
4 |
241-244 |
A |
C |
Indicates the currency code of the transaction according to ISO 4217 (EMV TAG 5F2A) |
|||||||||||||||
Application Interchange Profile |
4 |
245-248 |
A |
C |
Indicates microcircuit application-specific functions (information supplied by the card) (EMV TAG 82) |
|||||||||||||||
Terminal Country Code |
4 |
249-252 |
A |
C |
Indicates the country of the terminal, represented according to ISO 3166 (EMV TAG 9F1A) |
|||||||||||||||
Amount, Other |
12 |
253-264 |
A |
C |
Secondary Amount of the transaction (e.g. Cash Amount) as provided by the terminal to the card (EMV TAG 9F03) |
|||||||||||||||
Terminal Capabilities |
6 |
265-270 |
A |
C |
Indicates the card data input, CVM, and security capabilities of the terminal. Alphabetic characters must be presented in upper case (EMV TAG 9F33) |
|||||||||||||||
CVM results |
6 |
271-276 |
A |
C |
Result of Cardholder Verification Procedure (EMV TAG 9F34) |
|||||||||||||||
Terminal Type |
2 |
277-278 |
A |
C |
Indicates the environment of the terminal, its communications capability, and its operational control (EMV TAG 9F35) |
|||||||||||||||
Interface Device (IFD) Serial No |
16 |
279-294 |
A |
C |
Unique and permanent serial number assigned to the IFD by the manufacturer (EMV TAG 9F1E) |
|||||||||||||||
Transaction category Code |
2 |
295-269 |
A |
C |
Describes environment of the TX. Derived from MCC (EMV TAG 9F53) |
|||||||||||||||
Dedicated File (DF) Name |
32 |
297-328 |
A |
C |
Identifies the name of the DF as described in ISO/IEC 7816-4. Mandatory for Diners transactions. (EMV TAG 84) |
|||||||||||||||
Terminal application version no. |
4 |
329-332 |
A |
C |
EMV Version of the Terminal SW (EMV TAG 9F09) |
|||||||||||||||
Transaction Sequence Counter |
8 |
333-340 |
A |
C |
Counter maintained by the terminal that is incremented by one for each transaction (EMV TAG 9F41) |
|||||||||||||||
Card Sequence Number |
3 |
341-343 |
A |
C |
A number distinguishing between separate cards with the same PAN Otherwise space-fill (EMV TAG 5F34) |
|||||||||||||||
Issuer Script Results part I |
24 |
344-367 |
A |
C |
Results of the Issuer Script Execution Part 1 (Tag 71) |
|||||||||||||||
Issuer Script Results part II |
18 |
368-385 |
A |
C |
Results of the Issuer Script Execution Part 2 (Tag 72)
|
|||||||||||||||
System Trace Audit Number |
6 |
386-391 |
A |
C |
Mandatory for Discover Processing in the US/CAN and Union Pay in all countries. 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. If not present = Space-fill |
|||||||||||||||
Retrieval Reference Number |
12 |
392-403 |
A |
O |
If not present = Space-fill |
|||||||||||||||
Form Factor Indicator |
8 |
404-411 |
A |
C |
VISA payWave / Diners Contactless: the Form Factor Indicator is transmitted from the card to the terminal in the response of GET PROCESSING OPTIONS command in order to be forwarded to the issuer. Mandatory for Visa and Diners if present on card. Mastercard Contactless: Tag 9F6E is defined to hold Third-Party Data. (EMV TAG 9F6E) |
|||||||||||||||
Reserved For Future Use |
14 |
412-425 |
A |
O |
Space-fill |
|||||||||||||||
MOTO/ Ecommerce Authentication Indicator |
1 |
426-426 |
A |
C |
Valid values:
|
|||||||||||||||
Cardholder Verification Value (CVV2) |
1 |
427 |
A |
C |
Required where Transaction Source Field = 02 (Keyed) if available. Valid values:
American Express Values:
|
|||||||||||||||
AVS Result |
1 |
428 |
A |
O |
Address Verification Service Result Code. 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 space filled if a value is not transferred from the authorization response record. Returned in Authorisation Response Message as a result of an AVS Request |
|||||||||||||||
Dynamic CVV2 Result Code |
1 |
429 |
A |
O |
Reserved for future use |
|||||||||||||||
Check-In Date |
6 |
430-435 |
N |
O |
YYMMDD Cruises Line: Check-in Date Car Rental: Check-in Date / returns Tour-Operator / Travel-Agent: Check-in Date Hotel: pls. use the HAR-Record Otherwise Space-fill |
|||||||||||||||
Check-Out Date |
6 |
436-441 |
N |
O |
YYMMDD Cruises Line: Check-out Date / returns Car Rental: Check-out Date Tour-Operator / Travel-Agent: Check-out Date Hotel: pls. use the HAR-Record Otherwise Space-fill |
|||||||||||||||
Mobile POS (MPOS) Indicator
|
1 |
442 |
A |
C |
Indicating that the Point of Sale Device is e.g. a Mobile or a Tablet Computer. Valid values:
|
|||||||||||||||
Dual Brand Override Indicator |
2 |
443-444 |
A |
C |
Field denotes card brand selected by the customer at the Point of Interaction. Only applies to dual branded cards. Only currently supported for Union Pay. Only populate if a dual-brand override is required. Otherwise space-fill. Valid values:
|
|||||||||||||||
Spend Qualified Indicator |
1 |
445 |
A |
C |
Optional data field is used in conjunction with certain card products that have minimum annual spending limits, and is populated by Visa. Indicates whether an account is spend-qualified, based on the point-of-sale spend history of the account and the defined product-level spend requirement for country of issuance. It is forwarded to participating endpoints in authorisation and full financial messages.
Valid values:
|
|||||||||||||||
Unattended Acceptance Terminal Indicator |
1 |
446 |
N |
C |
Indicates type of unattended terminal. Also known as Card Activated Terminal (CAT) Indicator. Valid values:
Space-fill if not applicable. |
|||||||||||||||
POS Terminal Capability |
1 |
447 |
N |
M |
Indicates terminal card entry capabilities. Valid values:
|
|||||||||||||||
Debt Repayment Indicator |
1 |
448 |
A |
C |
Indicates Debt Repayment Transactions. Valid values:
|
|||||||||||||||
Elavon Current Token Type |
2 |
449-450 |
A |
C |
Indicates the Elavon Token Type used in an Elavon Tokenised transaction. Space-filled if not applicable. |
Fields from position 117 to 385 and 404 to 425 in the TDR relate to EMV transactions. As such, these should only be populated where appropriate. They are to be filled if the Transaction Source Field (position 51-52) is equal to one of the following values: 06, 07, 16, 17, 24, 25, 26, 27.
If an EMV field is not present, either space-fill if the field is alphanumeric or zero-fill if the field is numeric.