6. Transaction Field Description
Clearing file have details of multiple transactions in a file.
Example: 1240^200^101100^9592605678986058^567345^975568938144^12345678901234 567890123^6011^20240401074516^T001B034B458P503^BANGKOK1 BAAC BANGKOK 001TH^500.00^524^500.00^524^^^^^00000009289^00000004567^00000009289 ^00000004567^20240401^^^0^C^0.00^524^0.00^524^0.00^524^C^BankA^B ankB ^1^5^^^^^A^^(Additional data for future use)
Description for each field of the file trailer is as follows,
6.1 MTI (Message Type Identifier)
MTI specifies the type of transaction/record such as header/trailer, financial, non-financial, dispute etc. MTI is placed at the beginning of the transaction i.e. each transaction/record in the file should start with the MTI.
| Position: | 1 |
| Max Length: | 4 |
| Data Type: | Numeric |
| MTI | Transaction Type |
|---|---|
| 1240 | |
| First Presentment | |
| Retrieval Request | |
| Retrieval Request Response | |
| Re-Presentment Full | |
| Re-Presentment Partia | |
| Re-Presentment Acceptance Full | |
| Re-Presentment Acceptance Partial | |
| Chargeback Full | |
| Chargeback Partial | |
| Chargeback Acceptance Full | |
| Chargeback Acceptance Partial | |
| Pre-Arbitration | |
| Pre-Arbitration Acceptance | |
| Arbitration case filing | |
| Arbitration case filing verdict | |
| Arbitration case filing acceptance | |
| Non-financial Transactions |
Table 9: Transaction Field MTI Matrix
6.2 Function Code
Function code specifies the type of functionality used for a transaction/record. MTI can have multiple function codes.
| Position: | 2 |
| Max Length: | 3 |
| Data Type: | Numeric |
Table 10: Transaction Field Function Code Matrix
6.3 Processing Code
Processing code (Transaction code) specifies the effect of transaction on customer account and type of accounts affected. Processing code is the combination of transaction type, from account type and to account type.
| Position: | 3 |
| Max Length: | 6 |
| Type: | Numeric |
Processing Code - <2-digit transaction type><2 digit from account type><2 digit to account type> Example: 301100 (Balance enquiry from saving account)
Table 11: Processing Code Details
6.4 PAN/Token
PAN (Primary Account Number) specifies the card number of the customer and Token specifies the token data of the respective card or account. Maximum length of PAN/Token is 19.
| Position: | 4 |
| Max Length: | 19 |
| Data Type: | Alphanumeric |
6.5 Approval Code
Approval code is a code authorizing institute assigns to a transaction, indicating approval. The approval code generated by the transaction authorizer. This code can be generated by an interchange or host or switch.
| Position: | 5 |
| Length: | 8 |
| Data Type: | Alphanumeric |
6.6 RRN (Retrieval Reference Number)
RRN (Sequence number) is a unique number to identify the transaction. Each transaction in a file have different RRN. RRN start with 1 and continue till 999999999999 (12 times 9). After 999999999999 RRN resets to 1 and again continue till 999999999999.
| Position: | 6 |
| Length: | 12 |
| Data Type: | Numeric |
6.7 ARN (Acquirer Reference Number)
ARN specifies the data that acquirer provide in message that is used by issuer in subsequent messages or in complete life cycle of transaction.
| Position: | 7 |
| Length: | 23 |
| Data Type: | Numeric |
6.8 MCC (Merchant Category Code)
MCC is used to segment transactions into specific categories. For the ATM transactions MCC will be 6011 but for the POS transaction different MCC is used for each category of transaction.
| Position: | 5 |
| Length: | 8 |
| Data Type: | Alphanumeric |
6.9 Transaction Date & Time
Transaction date & time field specifies the date and time when the transaction happened. Example: 02-March-2024 10:26:47 will be represented as 20240302102647 Date & Time Format: YYYYMMDDHHMMSS
| Position: | 9 |
| Length: | 14 |
| Data Type: | Numeric |
6.10 Terminal ID
Terminal ID field specifies the Id of the terminal on which card is used. Each terminal/ATM have unique terminal Id.
| Position: | 10 |
| Length: | 16 |
| Data Type: | Alphanumeric |
6.11 Terminal Name & Location
Terminal name & location field specifies the name and location of the terminal where transaction initiated. Terminal name & location is the combination of terminal owner name, terminal location, terminal city, terminal state and terminal country.
| Position: | 11 |
| Length: | 100 |
| Data Type: | Alphanumeric |
6.12 Transaction Amount
Transaction amount specifies the amount in currency in which transaction happened.
| Position: | 12 |
| Length: | 12 (length is inclusive of dot and decimal digits) |
| Data Type: | Numeric with 2 decimal places (Example: 15000.00) |
6.13 Transaction Currency Code
Transaction currency code specifies the currency code for the transaction amount where transaction initiated.
| Position: | 13 |
| Length: | 3 |
| Data Type: | Numeric |
6.14 Settlement Amount
Settlement Amount is the amount reflected for settlement.
| Position: | 14 |
| Length: | 12 (length is inclusive of dot and decimal digits) |
| Data Type: | Numeric Numeric with 2 decimal places (Example: 15000.00) |
6.15 Settlement Currency Code
Settlement currency code specifies the currency code of settlement amount.
| Position: | 15 |
| Length: | 3 |
| Data Type: | Numeric |
6.16 Cardholder Billing Amount
Transaction Amount is converted into issuer’s designated billing amount. Cardholder billing amount will be same as transaction amount for the domestic transaction but for the international transaction, cardholder billing amount will be the amount in the currency of issuer country
| Position: | 16 |
| Length: | 12(length is inclusive of dot and decimal digits) |
| Data Type: | Numeric with 2 decimal places (Example: 15000.00) |
6.17 Cardholder Billing Currency Code
Cardholder billing currency code specifies the currency code for the cardholder billing amount. Cardholder billing currency code represents the currency code of the cardholder’s issuer bank country.
| Position: | 17 |
| Length: | 3 |
| Data Type: | Numeric |
6.18 Settlement Conversion Rate
Settlement conversion rate is a rate applied while converting the transaction amount into settlement amount.
| Position: | 18 |
| Length: | 8 |
| Data Type: | Numeric |
6.19 Cardholder Billing Conversion Rate
Cardholder billing conversion rate is a rate applied while converting the transaction amount into card holder billing amount.
| Position: | 19 |
| Length: | 8 |
| Data Type: | Numeric |
6.20 Forwarded By
Forwarded by specifies the unique member bank Id of the transaction forwarding institution. Each member bank has unique member Id configured while adding the member bank.
| Position: | 20 |
| Length: | 11 |
| Data Type: | Numeric |
6.21 Received By
Received by specifies the unique member bank Id of the transaction receiver institution. Each member bank has unique member Id configured while adding the member bank
| Position: | 21 |
| Length: | 11 |
| Data Type: | Numeric |
6.22 Acquirer ID
Acquirer ID specifies the unique member bank Id of the acquirer bank. Each member bank has unique member Id configured while adding the member bank.
| Position: | 22 |
| Length: | 11 |
| Data Type: | Numeric |
6.23 Issuer ID
Issuer ID specifies the unique member bank Id of the issuer bank. Each member bank has unique member Id configured while adding the member bank.
| Position: | 23 |
| Length: | 11 |
| Data Type: | Numeric |
6.24 Settlement Date
Date on which transaction settled by the interchange.
| Date Format: | YYYYMMDD |
| Position: | 24 |
| Length: | 8 |
| Data Type: | Numeric |
6.25 Message Reason Code
Message reason code (Response code) specifies the reason of responding the message.
| Position: | 25 |
| Length: | 2 |
| Data Type: | Numeric |
6.26 Member Message Text
Member message text specifies the additional information about the transaction.
| Position: | 26 |
| Length: | 100 |
| Data Type: | Alphanumeric |
6.27 Document Indicator
Document indicator specifies whether document is sent to support the transaction or not. In case of dispute transaction value may be 1 but for other transactions this field value will be 0.
| Position: | 27 |
| Length: | 1 |
| Data Type: | Numeric |
| 0 | No document sent |
| 1 | Document sent |
6.28 Fee Type Indicator
Fee type indicator specifies whether fee is credit or debit to the receiving member.
| Position: | 28 |
| Length: | 2 |
| Data Type: | String |
| C | Credit |
| D | Debit |
6.29 Fee Transaction Amount
Fee transaction amount specifies the fee in transaction currency.
| Position: | 29 |
| Max Length: | 12 (length is inclusive of dot and decimal digits) |
| Data Type: | Numeric with 2 decimal places (Example: 15.00) |
6.30 Fee Transaction Currency Code
Currency code for fee transaction amount.
| Position: | 30 |
| Length: | 3 |
| Data Type: | Numeric |
6.31 Fee Settlement Amount
Fee transaction amount is converted into the fee settlement amount.
| Position: | 31 |
| Length: | 12 (length is inclusive of dot and decimal digits) |
| Data Type: | Numeric with 2 decimal places (Example: 150.00) |
6.32 Fee Settlement Currency Code
Currency code for fee settlement amount.
| Position: | 32 |
| Length: | 3 |
| Data Type: | Numeric |
6.33 Additional Amount
Additional amount of tips/surcharge or currency fluctuation
| Position: | 33 |
| Length: | 12 (length is inclusive of dot and decimal digits) |
| Data Type: | Numeric with 2 decimal places (Example: 150.00) |
6.34 Additional Amount Sign
Additional amount sign specifies whether the additional amount will be credited/debited to/from participating member.
| Position: | 34 |
| Length: | 1 |
| Data Type: | String |
| C | Credit |
| D | Debit |
6.35 Issuer Member Name
Issuer member name is the short name of the issuer member assigned by NCHL.
| Position: | 35 |
| Length: | 9 |
| Data Type: | String |
6.36 Acquirer Member Name
Acquirer member name is the short name of the acquirer member assigned by NCHL.
| Position: | 36 |
| Length: | 9 |
| Data Type: | String |
6.37 Card Present (CP) Indicator
CPS Indicator indicates whether transaction is Card Present Transactions or Card Not Present Transactions.
| Position: | 37 |
| Length: | 1 |
| Data Type: | Numeric |
| Indicator | Description |
| 0 | CNP |
| 1 | CP |
| 8 | Unknown |
6.38 Terminal Capability Code
Terminal capability indicates the mode of transaction.
| Position: | 38 |
| Length: | 1 |
| Data Type: | Numeric |
| Code | Description |
|---|---|
| 0 | Unknown entry point |
| 1 | Manual entry |
| 2 | Magnetic stripe read |
| 5 | ICC Read |
| 6 | Key entered at POS |
| 8 | Contactless |
| 9 | Hybrid |
6.39 ECI Indicator
ECI Indicator indicates how ecommerce transaction is authorized.
| Position: | 39 |
| Length: | 1 |
| Data Type: | Numeric |
6.40 Transaction Indicator
Transaction indicator is used for MIT transactions. The values are as per DCI (DE 62 Tag Df05)
| Position: | 40 | |
| Length: | 1 | |
| Data Type: | String |
| Indicator | Description |
|---|---|
| Blank | Default |
| A | Re-authorize for Full Amount |
| D | Delayed Card Sale |
| E | Resubmission of Card Sale |
| G | Transit Aggregated Transaction |
| I | Incremental Authorization |
| N | No-Show Charge |
| P | Partial/Split Shipment |
| R | Recurring Payment |
| S | Installment Payment |
| U | Unscheduled Payment |
6.41 Original Transaction Amount
Original transaction amount specifies the amount in currency in which original transaction happened.
| Position: | 41 |
| Length: | 12 (length is inclusive of dot and decimal digits) |
| Data Type: | Numeric with 2 decimal places (Example: 15000.00) |
6.42 Transaction Identifier
Transaction identifier is a unique value for each transaction, which is used to maintain an audit trail throughout the life cycle of the transaction and all related transactions, such as presentments, adjustments, confirmations, and disputes. This identifier will be a combination of below fields from authorization transaction: Transaction Identifier: Acquirer ID (DE32) + Settlement Date (DE15) + Approval Code (DE38) + Reference Number (DE37)
| Position: | 42 |
| Length: | Varies |
| Data Type: | Alphanumeric |
6.43 Process
Process identifies whether the transaction is issuing or acquiring transactions.
| Position: | 43 |
| Length: | 1 |
| Data Type: | Alphanumeric |
6.44 Case Id
Case Id is id assigned for dispute transaction.
| Position: | 44 |
| Length: | 20 |
| Data Type: | Alphanumeric |
6.45 Additional Data
Additional information related to the transaction will be available in this field. It is reserved for future use. If additional data is not there, then this field value will remain empty.
| Position: | 45 |
| Length: | Varies |
| Data Type: | Alphanumeric |
The value of the additional field would be,
(3-digit Data ID)(Length of Data)(Data Value) Example: 0016345678002244
Where,
001 – ID of Data 1
6 – Length of Data 1
345678 – Value of Data 1
002 - ID of Data 2
2 - Length of Data 2
44 - Value of Data 2