5. Message Format
5.1 Message Definition
A card-based transaction message ordinarily travels from a transaction initiating device, such as a point-of-sale terminal (POS) or an automated teller machine (ATM), through a series of networks, to issuer for authorization against the card holder's account. The transaction message consists the information of card, cardholder, terminal, merchant and other as per needs. Based on this information, the card issuing system will either authorize or decline the transaction and generate a response message which must be delivered back to the terminal within a predefined time period. Based on the response message, terminal shall complete the transaction and provide respective result to the cardholder.
The card-based transaction messages include purchase, withdrawal, deposit, refund, reversal, balance inquiry, fund transfer, mini statement, utility payments etc. Apart from these, ISO 8583 also defines system-to-system messages such as network messages, key exchange messages, etc.
5.2 Message Type Identification
This section covers the message type identification used in National Card Switch online message specification.
S.N. | Transaction | Message Type | Key Data Elements |
---|---|---|---|
1 | POS Purchase | MTI 0100 / 0110 | Data Element Field 3 must be 00XXXX Data Element Field 35 must be present |
2 | POS Purchase Reversal | MTI 0420 / 0430 | Data Element Field 3 must be 00XXXX Data Element Field 90 must be present |
3 | VOID / Cancellation | MTI 0420 / 0430 | Data Element Field 3 must be 00XXXX Data Element Field 39 must be 17 Data Element Field 90 must be present |
4 | Refund | MTI 0120 / 0130 | Data Element Field 3 must be 20XXXX Data Element Field 90 must be present |
5 | Preauthorization | MTI 0100 / 0110 | Data Element Field 3 must be 03XXXX |
6 | Preauthorization Reversal | MTI 0420 / 0430 | Data Element Field 3 must be 03XXXX Data Element Field 90 must be present |
7 | Preauthorization Cancellation | MTI 0420 / 0430 | Data Element Field 3 must be 03XXXX Data Element Field 39 must be 17 Data Element Field 90 must be present |
8 | Preauthorization Completion | MTI 0120 / 0130 | Data Element Field 3 must be 03XXXX |
9 | Purchase with Cashback | MTI 0100 / 0110 | Data Element Field 3 must be 09XXXX Data Element Field 54 must contain cashback amount |
10 | Purchase with TIP (Gratuity) | MTI 0100 / 0110 | Data Element Field 3 must be 00XXXX Data Element 04 must contain transaction amount plus tip amount Data Element Field 54 must contain tip amount |
11 | Balance Inquiry | MTI 0100 / 0110 MTI 0200 / 0210 | Data Element Field 3 must be 30XXXX The Balance Amount is returned in Data Element Field 54 |
12 | Cash Withdrawal / Fast Cash - ATM | MTI 0200 / 0210 | Data Element Field 3 must be 01XXXX |
13 | Mini Statement | MTI 0100 / 0110 MTI 0200 / 0210 | Data Element Field 3 must be 38XXXX The Statement Data is returned in Data Element Field 120 |
14 | PIN Change | MTI 0200 / 0210 | Data Element Field 3 must be 98XXXX The PIN change data must present in Data Element 120 |
15 | Reversal – ATM Cash withdrawal / Fast Cash | MTI 0420 / 0430 | Data Element Field 3 must be 01XXXX Data Element Field 90 must be present |
16 | Cheque Book Request | MTI 0200 / 0210 | Data Element Field 3 must be 36XXXX |
17 | Statement Request | MTI 0200 / 0210 | Data Element Field 3 must be 37XXXX |
18 | Fund Transfer | MTI 0200 / 0210 | Data Element Field 3 must be 40XXXX |
19 | Utility Payment – for ATM | MTI 0200 / 0210 – from ATM MTI 0100 / 0110 – from POS & Ecommerce | |
20 | eCommerce Purchase | MTI 0100 / 0110 | Data Element Field 3 must be 00XXXX Data Element Field 22 must be 07X |
21 | Account Verification | MTI 0100 / 0110 | Data Element Field 3 must be 18XXXX Data Element Field 63 must be present |
22 | Original Credit Transaction (OCT) | MTI 0100 / 0110 | Data Element Field 3 must be 26XXXX |
23 | Installment Payment | MTI 0200 / 0210 – from ATM MTI 0100 / 0110 – from POS & Ecommerce | |
24 | Recurring Payment | MTI 0200 / 0210 – from ATM MTI 0100 / 0110 – from POS & Ecommerce | |
25 | Tax Refund | MTI 0200 / 0210 – from ATM MTI 0100 / 0110 – from POS & Ecommerce | |
26 | EMI Payment | MTI 0200 / 0210 – from ATM MTI 0100 / 0110 – from POS & Ecommerce | |
27 | Network Echo | MTI 0800 / 0810 | Data Element Field 70 must be 301 |
28 | Network Signon / Logon | MTI 0800 / 0810 | Data Element Field 70 must be 001 |
29 | Network Signoff / Logoff | MTI 0800 / 0810 | Data Element Field 70 must be 002 Data Element Field 70 must be 012 – for logoff due to Debit Cap Limit Exceed |
30 | Network Cut Over | MTI 0800 / 0810 | Data Element Field 70 must be 201 |
31 | Network Key Exchange | MTI 0800 / 0810 | Data Element Field 70 must be 161 – for Member initiated Data Element Field 70 must be 162 – for NCHL initiated |
32 | STIP Advice | MTI 0120 / 0130 | |
33 | File Update | MTI 0302 / 0312 |
Table 8: Message Identification
5.3 Transaction Message Flow
The following Message flows represent the path of a Message between an Acquirer, NCHL and an Issuer. The flows are organized by Message type and by specific situations for each Message type. A diagram and a description that gives details regarding the diagram depict each flow. The numbers in the diagram correlate to a specific step in the description.
5.3.1 Authorization Transaction Message Flows [0100 / 0110]
This message serves to authorize a transaction even before the final purchase amount is determined. Its primary function is to ascertain the availability of funds, obtain approval, and subsequently block the necessary funds in the account. It's important to note that these messages do not have a direct settlement impact. To complete the clearing and settlement process for an approved transaction, the acquirer must submit the transaction to the clearing system. Authorization Messages deliver information regarding the purchase of goods or services between Merchants/Acquirers and Issuers. Minimally, the 0100 Authorization Request carries information detailing the Card Number, Card Acceptor, and when and how the Card Transaction occurred. The 0110 Authorization Response returns the same information, including the decision on the Authorization Request.
Figure 11: 0100/0110 Authorization message flow
Sequence | Description |
---|---|
1 | The Acquirer sends the 0100 Authorization Request to NCHL. |
2 | NCHL receives the 0100 Authorization Request and routes it to the Issuer for Authorization. |
3 | The Issuer approves or declines the 0100 Authorization Request, creates the 0110 Authorization Response, and sends the Authorization Response to NCHL. |
4 | NCHL routes the 0110 Authorization Response to the Acquirer. |
5.3.2 Financial Transaction Message Flows [0200 / 0210]
This message is designed to verify the availability of funds, secure approval, and initiate the debit from the account. Notably, financial messages of this nature have a direct settlement impact. Following this transaction, no exchange of clearing files takes place. Financial Transaction Messages deliver information regarding Cash Disbursements from ATMs as well as Card Transactions for transfer of funds. Minimally, the 0200 Financial Transaction Request carries information detailing how, when, and where the Cash Disbursement occurred, details about the Cardholder and Card Number, security information, and Settlement date. The 0210 Financial Transaction Response returns the same information, including the decision on the Financial Transaction Request.
Figure 12: 0200/0210 Financial message flow
Sequence | Description |
---|---|
1 | The Acquirer/ATM Network sends the 0200 Financial Transaction Request to NCHL. |
2 | NCHL receives the 0200 Financial Transaction Request and routes it to the Issuer for Authorization. |
3 | The Issuer approves or declines the 0200 Financial Transaction Request, creates the 0210 Financial Transaction Response, and sends the Financial Transaction Response to NCHL. |
4 | NCHL routes the 0210 Financial Transaction Response to the Acquirer/ATM Network. |
5.3.3 Authorization Advice Message Flows [0120 / 0130]
Authorization Advice Messages are used when the Issuer is unavailable and stand-in processing was used to make the decision on an Authorization Request Transactions. The Authorization Advice Messages are subject to store and forward processing for Network stand-in processing to ensure the Issuer receives notification of the Card Transaction. The 0120 Authorization Advice Message contains the same information as the original Authorization Request, as well as the NCHL stand-in decision regarding the Authorization Request, where applicable. The 0130 Authorization Advice Message Response indicates the Authorization Advice Message was received.
Figure 13: 0120/0130 Authorization advice message flow
Sequence | Description |
---|---|
1 | The Acquirer sends the 0100 Authorization Transaction Request to NCHL. |
2 | NCHL receives the 0100 Authorization Transaction Request and, in the event of issuer unavailability, responds with a 0110 Authorization response to the acquirer, exercising the stand-in facility and providing the necessary authority on behalf of the issuer. |
3 | When the issuer comes online, NCHL generates an authorization advice message request 0120, stores and forwards it to the issuer. |
4 | The issuer sends a 0130 authorization advice response, confirming the proper receipt of the authorization advice request. |
5.3.4 File Update Message Flows [0302 / 0312]
File update message is an issuer generated message. File update message is used to update the cardholder records in NCHL database for negative list. This message will enable performing a STIP authentication on behalf of the issuer.
Sequence | Description |
---|---|
1 | The Issuer member sends 0302 File Update Message request to NCHL. |
2 | NCHL responds with the 0312 File Update Message Response to the Issuer. |
5.3.4 Reversal Advice Message Flows [0420 / 0430]
This message functions to reverse the action of a prior authorization or financial transactions. It serves as a notification to NPS-NCS and/or the issuer, specifically addressing an error condition related to a previous financial transaction or balance update transaction if:
• An approved transaction is cancelled at the POS or ATM device.
• Acquirer does not receive a response to a financial request.
• Acquirer cannot send an approved response to the POS or ATM device.
In the event that these messages cannot be promptly delivered to their designated destination for any reason, the acquirer or NCHL stores them in SAF (Store and Forward) and subsequently forwards them to the intended destination. NCHL treats all reversal messages as reversal advice messages. To initiate a reversal, the acquirer must send a 0420 message to NCHL, which will then forward it to the issuer. The issuer is required to respond with a 0430 message.
NCHL generates reversals exclusively for time-out scenarios concerning issuer responses. Additionally, NCHL will generate a reversal if the response from the issuer fails format validation or if the issuer fails to respond within the allowed time limit. It is crucial to note that a reversal always requires acknowledgment. The response code in the reversal response 0430 message is disregarded at NCHL. Once a response is received for the 0420 message from the issuer, NCHL considers the reversal as completed. It is then removed from SAF and takes effect in settlement.
The acquirer has the capability to generate reversals within the next 72 hours, equivalent to three cut-over cycles. Reversals generated beyond this timeframe will not be validated or processed by NCHL.
5.3.4.1 Acquirer Generated Reversal Message Flow [0420 / 0430]
Figure 15: 0420/0430 Reversal message flow
Sequence | Description |
---|---|
1 | The Merchant/Acquirer/ATM Network generates and forwards the 0420 Reversal Advice Message to NCHL due to reasons as:
|
2 | NCHL responds with the 0430 Reversal Advice Message Response to the Merchant/Acquirer/ATM Network. |
3 | NCHL stores and forwards the 0420 Reversal Advice Message to the Issuer. |
4 | The Issuer responds with the 0430 Reversal Advice Message Response to NCHL. |
Note:Reversal advice message may be stored and forwarded by NCHL at a later time, resulting in sending the Message immediately or at some later time.
5.3.4.1.1 Reversal Message Flow [0420 / 0430] due to Acquirer Unable to Process
Figure 16: Acquirer generated Reversal message flow: Acquirer Unable to Process
Sequence | Description |
---|---|
1 | The Acquirer sends the 0100/0200 Transaction Request to NCHL. |
2 | NCHL receives the 0100/0200 Transaction Request and routes it to the Issuer for Authorization. |
3 | The Issuer accepts or declines the 0100/0200 Transaction Request, creates the 0110/0210 Response, and sends the response to NCHL. |
4 | NCHL responds to the 0100/0200 Transaction Request with the 0110/0210 Response. |
5 | The Acquirer unable to process the transaction or could not able to send the response to terminal. Then Acquirer creates the 0420 Reversal Advice Message, if the 0100/0200 Transaction Request was approved, and stores and forwards the Reversal Advice Message to NCHL. |
6 | NCHL responds with a 0430 Reversal Advice Message Response to the Acquirer. |
7 | NCHL stores and forwards the 0420 Reversal Advice Message to the Issuer. |
8 | The Issuer responds with the 0430 Reversal Advice Message Response to NCHL. |
Note:Reversal advice message may be stored and forwarded by NCHL at a later time, resulting in sending the Message immediately or at some later time.
5.3.4.1.2 Reversal Message Flow [0420 / 0430] due to NCHL Late Good Response to Acquirer
Figure 17: Acquirer generated Reversal message flow: NCHL Late Good Response to Acquirer
Sequence | Description |
---|---|
1 | The Acquirer sends the 0100/0200 Transaction Request to NCHL. |
2 | NCHL receives the 0100/0200 Transaction Request and routes it to the Issuer for Authorization. |
3 | The Issuer accepts or declines the 0100/0200 Transaction Request, creates the 0110/0210 Transaction Response, and sends the response to NCHL. |
4 | NCHL does not respond to the 0100/0200 Transaction Request with the 0110/0210 Transaction Response in a pre-determined time period. The Acquirer declines the Transaction, but then receives a delayed 0110/0210 Transaction Response from NCHL. |
5 | The Acquirer generates the 0420 Reversal Advice Message, if the 0100/0200 Transaction Request was having timed-out or late good response, and forwards the Reversal Advice Message to NCHL. |
6 | NCHL responds with a 0430 Reversal Advice Message Response to the Acquirer. |
7 | NCHL stores and forwards the 0420 Reversal Advice Message to the Issuer. |
8 | The Issuer responds with the 0430 Reversal Advice Message Response to NCHL. |
Note:Reversal advice message may be stored and forwarded by NCHL at a later time, resulting in sending the Message immediately or at some later time.
5.3.4.1.3 Reversal Message Flow [0420 / 0430] due to Terminal Failure
Figure 18: Acquirer generated Reversal message flow: Terminal Failure
Sequence | Description |
---|---|
1 | The Acquirer sends the 0100/0200 Transaction Request to NCHL. |
2 | NCHL receives the 0100/0200 Transaction Request and routes it to the Issuer for Authorization. |
3 | The Issuer accepts or declines the 0100/0200 Transaction Request, creates the 0110/0210 Transaction Response, and sends the response to NCHL. |
4 | NCHL responds to the 0100/0200 Transaction Request with the good 0110/0210 Transaction Response. |
5 | The Acquirer declines the Transaction due to a hardware failure of the terminal. The Acquirer generates the 0420 Reversal Advice Message and forwards the Reversal Advice Message to NCHL. |
6 | NCHL responds with a 0430 Reversal Advice Message Response to the Acquirer. |
7 | NCHL stores and forwards the 0420 Reversal Advice Message to the Issuer. |
8 | The Issuer responds with the 0430 Reversal Advice Message Response to NCHL. |
Note:Reversal advice message may be stored and forwarded by NCHL at a later time, resulting in sending the Message immediately or at some later time.
5.3.4.2 NCHL Generated Reversal Message Flow [0420 / 0430]
Figure 19: NCHL Generated Reversal Message Flow
Sequence | Description |
---|---|
1 | The Acquirer sends the 0100/0200 Transaction Request to NCHL. |
2 | NCHL receives the 0100/0200 Transaction Request and routes it to the Issuer for Authorization. |
3 | The Issuer responds to the 0100/0200 Transaction with the 0110/0210 Transaction Response to NCHL. |
4 | NCHL found timeout or message validation fails in the 0110/0210 response, responds 0110/0210 message to acquirer with appropriate error code. |
5 | NCHL generates and sends the 0420 Reversal Advice Message to the Issuer in case of late good response or failing validation of the response message. |
6 | The Issuer responds with the 0430 Reversal Advice Message Response to NCHL. |
Note:Reversal advice message may be stored and forwarded by NCHL at a later time, resulting in sending the Message immediately or at some later time.
5.3.4.2.1 NCHL Generated Reversal Message Flow [0420 / 0430] due to Message Validation
Sequence | Description |
---|---|
1 | The Acquirer sends the 0100/0200 Transaction Request to NCHL. |
2 | NCHL receives the 0100/0200 Transaction Request and routes it to the Issuer for Authorization. |
3 | The Issuer responds to the 0100/0200 Transaction with the 0110/0210 Transaction Response. |
4 | NCHL validates the response message 0110/0210 and identifies an invalid message, then NCHL responds acquirer with error response code. |
5 | NCHL generates and sends the 0420 Reversal Advice Message to the Issuer. |
6 | The Issuer responds with the 0430 Reversal Advice Message Response to NCHL. |
Note:Reversal advice message may be stored and forwarded by NCHL at a later time, resulting in sending the Message immediately or at some later time.
5.3.4.2.2 NCHL Generated Reversal Message Flow [0420 / 0430] due to Issuer Late good Response to NCHL
Figure 21: NCHL generated Reversal message flow: Issuer Late Good Response to NCHL
Sequence | Description |
---|---|
1 | The Acquirer sends the 0100/0200 Transaction Request to NCHL. |
2 | NCHL receives the 0100/0200 Transaction Request and routes it to the Issuer for Authorization. |
3 | The Issuer does not respond to the 0100/0200 Transaction with the 0110/0210 Transaction Response in a pre-determined time period. NCHL creates the declined 0110/0210 Transaction Response, and sends the response to the Acquirer. |
4 | NCHL receives a delayed 0110/0210 Transaction Response from the Issuer. |
5 | NCHL generates and sends the 0420 Reversal Advice Message to the Issuer, if the Issuer was not responded or responded 0110/0210 with late good response. |
6 | The Issuer responds with the 0430 Reversal Advice Message Response to NCHL. |
Note:Reversal advice message may be stored and forwarded by NCHL at a later time, resulting in sending the Message immediately or at some later time.
5.3.4.2.3 NCHL Generated Reversal Message Flow [0420 / 0430] due to NCHL processing error
Figure 22: NCHL generated Reversal message flow: NCHL processing error
Sequence | Description |
---|---|
1 | The Acquirer sends the 0100/0200 Transaction Request to NCHL. |
2 | NCHL receives the 0100/0200 Transaction Request and routes it to the Issuer for Authorization. |
3 | The Issuer responds to the 0100/0200 Transaction with the 0110/0210 Transaction Response. |
4 | NCHL is unable to process the response 0110/0210 properly, then NCHL responds acquirer with error response code. |
5 | NCHL generates and sends the 0420 Reversal Advice Message to the Issuer. |
6 | The Issuer responds with the 0430 Reversal Advice Message Response to NCHL. |
Note:Reversal advice message may be stored and forwarded by NCHL at a later time, resulting in sending the Message immediately or at some later time.
5.3.4.4 Merchant Refunds and VOID Through Reversal
In the scenario where an acquirer initiates an authorization request (0100) and receives an approved authorization response (0110) with valid DE-38 and DE-39, but the customer cancels the transaction by voiding it at the POS terminal, the acquirer subsequently sends a reversal with DE-39 = '17' to NCHL.
Figure 23: Merchant Refund and VOID Through Reversal Message Flow
Sequence | Description |
---|---|
1 | The Acquirer/ATM Network sends the 0100 Authorization Transaction Request to NCHL. |
2 | NCHL receives the 0100 Authorization Transaction Request and routes it to the Issuer for Authorization. |
3 | The Issuer responds to the 0100 Authorization Transaction with the 0110 Authorization Transaction Response to NCHL. |
4 | NCHL responds the 0110 authorization response message to acquirer. |
5 | In response to a merchant's request for a customer refund or void, the merchant acquirer reverses the original transaction. The merchant acquirer formats a 0420 Reversal Advice message, as necessary, with specified field values to indicate the reason for the reversal. DE-39 = ‘17’ |
6 | NCHL stores and forwards the 0420 Reversal Advice Message to the Issuer. |
7 | The Issuer responds with the 0430 Reversal Advice Message Response to NCHL. |
8 | NCHL responds with the 0430 Reversal Advice Message Response to the Acquirer. |
Note:Reversal advice message may be stored and forwarded by NCHL at a later time, resulting in sending the Message immediately or at some later time.
5.3.5 Network Management Message Flows [0800 / 0810]
This message is used to communicate participating members with the NCHL. These messages can be initiated either by members or by NCHL. These messages are used to communicate that the member is available for processing transactions.
5.3.5.1 0800/0810 Network Management Message Flow: Echo Message
Echo-test messages are network management messages used to establish whether a member is available for message processing. They can be sent from or to a Member as 0800 messages and require 0810 messages in response. Echo-test messages are distinguished by a value of 301 in data element 70 (Network Management Information Code). Echo-test messages are sent based on a pre-configured time interval. When NCHL sends an Echo-test message, a timer is set to wait for a response. If the timer expires before NCHL receives the response, NCHL will attempt the Echo-test message three more times and if they all timeout then it will change the status of the corresponding Member to unavailable or DOWN. NCHL will not send any messages except for Echo-test messages until the member confirms the echo message with response code “00”. Then Logon message is required to change the status of the corresponding Member to available or UP.
Figure 24: 0800/0810 Network Management - Echo message flow
Sequence | Description |
---|---|
1 | NCHL generates a 0800 Network Management Request, Echo-test and sends it to the Member with Network Management Code set to - "301". This tells the Member that NCHL is available over that link. |
2 | The Member responds with a 0810 Network Management Request Response message with Response Code set to - “00”. There is no need to log the Echo-test message at the Member side. |
Note:Similarly, member can originate and send the Network Management – Echo message to NCHL as per their pre-defined interval. Echo messages must be sent before logon messages are exchanged.
5.3.5.2 0800/0810 Network Management Message Flow: Logon Message
Logon or Signon messages are network management messages used to initiate communications access between the NPS-NCS and Member’s switch. They are sent as 0800 messages and require 0810 messages in response. Logon messages are distinguished by a value of 001 (sign-on) in data element 70 (Network Management Information Code). The Logon message is essential in scenarios where a Member is: initially enrolled, or if a prior Logoff has occurred and need logon, or if physical connection between NCHL and member was down and is up. After the successful Logon message, NPS-NCS defines the status of the Member’s link as being UP and is ready to start processing transactions.
Figure 25: 0800/0810 Network Management - Logon message flow
Sequence | Description |
---|---|
1 | The member generates a 0800 Network Management Request, Logon and sends it to the NCHL with Network Management Code set to - "001". |
2 | NCHL responds with a 0810 Network Management Request Response message with Response Code set to - “00”. Then brings the status of the Member’s link as being UP. |
Note:Similarly, NCHL can originate and send the Network Management – Logon message to member. NCHL or member shall initiate the logon message under following conditions.
• If physical link is broken due from member’s side, its member’s responsibility to initiate logon message.
• If physical link is broken due from NCHL side, its NCHL’s responsibility to initiate logon message.
5.3.5.3 0800/0810 Network Management Message Flow: Logoff Message
Logoff messages are used to shut down a communication line between the NPS-NCS and member’s switch. All traffic on the line shall be completed before the line is shut down. They are sent as 0800 messages and require 0810 messages in response. Logoff messages are distinguished by a value of 002 (sign-off) in data element 70 (Network Management Information Code). Occasionally, it may be necessary for NCHL to cut off communications with a Member. The logoff message feature is a method of indicating to the Member that NCHL will not be processing any transactions.
Figure 26: 0800/0810 Network Management - Logoff message flow
Sequence | Description |
---|---|
1 | NCHL generates a 0800 Network Management Request, Logoff and sends it to the Member with Network Management Code set to - "002". |
2 | The Member responds with a 0810 Network Management Request Response message with Response Code set to - “00”. |
Note:Similarly, member can originate and send the Network Management – Logoff message to NCHL when it is necessary to cut off the communications with NCHL. This indicates to NCHL that the Member will not be processing any more transactions.
5.3.5.4 0800/0810 Network Management Message Flow: Cutover Message
It provides a mechanism for NCHL to inform all Banks that the transactions that they receive from this point on will be applied to a new business day or settlement date. It must be noted that NCHL’s settlement date will apply for all transaction settlement between NCHL and Members regardless of the Member bank’s capture date. NCHL will issue cutover message (0800 message with net code=201 in DE-70) at defined hour indicating a business date change for both SMS & DMS transactions, NCHL cut off time indicates the new settlement date is considered for transactions after cutover for SMS transactions.
Figure 27: 0800/0810 Network Management - Cutoff message flow
Sequence | Description |
---|---|
1 | NCHL generates a 0800 Network Management Request, Cutover and sends it to the Member with Network Management Code set to - "201". The commencement of the NPS-NCS new business day is indicated by the Settlement Date (DE - 15), signifying that all subsequent transactions between NCHL and Members should exclusively pertain to the refreshed NCHL business day. |
2 | The Member responds with a 0810 Network Management Request Response message with Response Code set to - “00” indicating receipt and acknowledgment of the change of business day. |
5.3.5.5 0800/0810 Network Management Message Flow: NCHL Initiated Key Exchange Message
Key exchange is a service that enables member banks to change working keys that are used to protect cardholder PINs via online messages. To utilize this service, members shall obtain a Zone Master Key (ZMK). A ZMK is a key exchange key. Members use a ZMK for encrypting the working key when they convey it in an online message. A ZMK is used to protect a Zonal Pin Key (ZPK). ZPK is different for both an issuer and an acquirer. Whether functioning as an issuer or an acquirer, each member will utilize a singular ZPK. There are two types of PIN encryption keys: Acquirer ZPKs and Issuer ZPKs. NCHL and an acquirer would share one ZPK and NCHL and issuer would share another ZPK. Acquirers use their ZPK to encrypt the PIN while sending a message to NCHL. NCHL uses the issuer ZPK to encrypt the PIN when it sends the message to the issuer.
The key exchange service makes it practically convenient to change PIN encryption keys frequently, thereby increasing the security of the payment system and reducing the chances of key compromise. The key exchange message could be initiated from NCHL side as well as from Member’s side.
Sequence | Description |
---|---|
1 | When NCHL identifies the need for a key change in response to threshold limit breaches or expired timers for a specific member, it initiates the process by composing a Network Management Request message (0800). The message is then sent to the member, containing predefined field values:
|
2 | Upon receipt of the 0800 Network Management Request Message, the Member identifies it as a key change request. Following a thorough validation, the Member's switch initiates a request to the Member Host Security Module. NCHL receives the 0810 Network Management Request Response from the Member and determines that a Response Code value “00” was received indicating successful completion of the key exchange. |
Note:For key exchange request initiated by NCHL, the success of a message is contingent upon a Member providing a response within the timeframe specified by NCHL. If the timer expires before NCHL receives the response or if the original message encounters failure, NCHL automatically discards the 0800 message. Only NCHL may initiate the key exchange message based on:
After a specific time interval.
In case NCHL detects a cryptographic error.
5.3.5.6 0800/0810 Network Management Message Flow: Member Initiated Key Exchange Message
In cases where a Member encounters HSM problems or key synchronization issues, there is an option to request a dynamic key exchange for recovery. This can be accomplished by initiating a dynamic key exchange request to NCHL as per details provided below.
Figure 29: 0800/0810 Network Management – Member Initiated Key Exchange message flow
Sequence | Description |
---|---|
1 | The Member initiates a new key request message (0800) for recovery purpose or for any ad-hoc reason, containing predefined field values:
|
2 | NCHL responds with a 0810 Network Management Request Response message with Response Code set to - “00” with DE-70 = “161”. |
3 | NCHL then generates a new key and initiates a key exchange request message (0800) containing predefined field values:
|
4 | Upon receipt of the 0800 Network Management Request Message, the Member identifies it as a key change request. Following a thorough validation, the Member's switch initiates a request to the Member Host Security Module. NCHL receives the 0810 Network Management Request Response from the Member and determines that a Response Code value “00” was received indicating successful completion of the key exchange. |
Note:Member bank can initiate key exchange request either on ad hoc basis or after facing some key related issues. Once the new key request from the member bank is accepted, NCHL will initiate key exchange message.
5.4 Message Format Notations
Following are the symbols used in different message formats.
Abbreviation | Meaning |
---|---|
M | Mandatory |
M+ | Mandatory, Echoed from the request |
C | Conditional |
C+ | Conditional, Echoed from request |
C* | Conditional, value changed by NCHL |
O | Optional |
O+ | Optional, Echoed from request |
-- | Not required |
A | Alphabetical |
B | Binary data |
N | Numeric value |
S | Special character |
X | Character C / D to indicate credit / debit |
Z | Track data |
AN | Alphanumeric |
ANS | Alphanumeric with special characters |
LL | Followed by the variable length value of data element, from 01 to 99 |
LLL | Followed by the variable length value of data element, from 001 to 999 |
VAR | Data element with variable length |
Table 9: Notation used in message format
5.5 Message Format
5.5.1 POS Purchase
The table below describes POS purchase message.
DE Field | Description | 0100 (Acquirer ➜ NCHL) | 0110 (NCHL ➜ Acquirer) | 0100 (NCHL ➜ Issuer) | 0110 (Issuer ➜ NCHL) |
---|---|---|---|---|---|
1 | Secondary bit map | C | C | C | C |
2 | Primary Account Number | M | M+ | M | M+ |
3 | Processing Code | M | M+ | M | M+ |
4 | Amount, Transaction | M | M+ | M | M+ |
5 | Amount, Settlement | C | C+ | C | C+ |
6 | Amount, card holder billing | C | C+ | C | C+ |
7 | Date/time transmission | M | M+ | M | M+ |
9 | Conversion rate, Settlement | C | C+ | C | C+ |
10 | Conversion rate, card holder billing | C | C+ | C | C+ |
11 | System trace audit number | M | M+ | M | M+ |
12 | Time, local transaction | M | M+ | M | M+ |
13 | Date, local transaction | M | M+ | M | M+ |
14 | Date, expiry | C | -- | C | -- |
15 | Date, Settlement | C | C+ | C | C+ |
16 | Date, conversion | C | C+ | C | C+ |
18 | Merchant category code | M | M+ | M | M+ |
19 | Acquiring institution country code | M | M+ | M | M |
22 | POS entry mode | M | -- | M | -- |
23 | Card sequence number | C | C+ | C | C+ |
25 | POS condition code | M | -- | M | -- |
28 | Amount, Fee | C | C+ | C | C+ |
29 | Amount, Fee | C | C | C | C |
32 | Acquiring institution code | M | M+ | M | M+ |
33 | Forwarding institution code | C | C+ | C | C+ |
35 | Track 2 data | C | -- | C | -- |
37 | Retrieval reference number | M | M+ | M | M+ |
38 | Authorization code | -- | M | -- | M |
39 | Response code | -- | M | -- | M |
41 | Card acceptor terminal ID | M | M+ | M | M+ |
42 | Card acceptor ID | M | -- | M | -- |
43 | Card acceptor name / location | M | -- | M | -- |
44 | Additional Response Data | -- | C | -- | C |
45 | Track 1 data | C | -- | C | -- |
48 | Additional Data 1 | M | -- | M | -- |
50 | Currency code, settlement | C | C+ | C | C+ |
51 | Currency code, card holder billing | C | C+ | C | C+ |
52 | PIN data | C | -- | C | -- |
54 | Additional Amounts | -- | O | -- | O |
55 | Chip data | C | C | C | C |
56 | Customer Related Data | C | C+ | C | C+ |
61 | POS Data | M | -- | M | -- |
102 | Account Identification 1 | O | O | O | O |
Table 10: POS Purchase Message
5.5.2 POS Purchase Reversal
The table below describes POS purchase Reversal message.
DE Field | Description | 0420 (Acquirer ➜ NCHL) | 0430 (NCHL ➜ Acquirer) | 0420 (NCHL ➜ Issuer) | 0430 (Issuer ➜ NCHL) |
---|---|---|---|---|---|
1 | Secondary bit map | C | C | C | C |
2 | Primary Account Number | M | M+ | M | M+ |
3 | Processing Code | M | M+ | M | M+ |
4 | Amount, Transaction | M | M+ | M | M+ |
5 | Amount, Settlement | C | C+ | C | C+ |
6 | Amount, card holder billing | C | C+ | C | C+ |
7 | Date/time transmission | M | M+ | M | M+ |
9 | Conversion rate, Settlement | C | C+ | C | C+ |
10 | Conversion rate, card holder billing | C | C+ | C | C+ |
11 | System trace audit number | M | M+ | M | M+ |
12 | Time, local transaction | M | M+ | M | M+ |
13 | Date, local transaction | M | M+ | M | M+ |
15 | Date, Settlement | C | C+ | C | C+ |
16 | Date, conversion | C | C+ | C | C+ |
18 | Merchant category code | M | M+ | M | M+ |
19 | Acquiring institution country code | M | M+ | M | M+ |
22 | POS entry mode | M | -- | M | -- |
23 | Card sequence number | C | C+ | C | C+ |
25 | POS condition code | M | -- | M | -- |
28 | Amount, Fee | C | C+ | C | C+ |
29 | Amount, Fee | C | C | C | C |
32 | Acquiring institution code | M | M+ | M | M+ |
33 | Forwarding institution code | C | C+ | C | C+ |
37 | Retrieval reference number | M | M+ | M | M+ |
38 | Authorization code | -- | M | -- | M |
39 | Response code | M | M | M | M |
41 | Card acceptor terminal ID | M | M+ | M | M+ |
42 | Card acceptor ID | M | -- | M | -- |
43 | Card acceptor name / location | M | -- | M | -- |
44 | Additional Response Data | -- | C | -- | -- |
48 | Additional Data 1 | M | -- | M | -- |
49 | Currency code, transaction | M | M+ | M | M+ |
50 | Currency code, settlement | C | C+ | C | C+ |
51 | Currency code, card holder billing | C | C+ | C | C+ |
54 | Additional Amounts | -- | O | -- | O |
55 | Chip data | C | C | C | C |
56 | Customer Related Data | C | C+ | C | C+ |
61 | POS Data | M | -- | M | -- |
90 | Original Data Element | M | M+ | M | M+ |
102 | Account Identification 1 | O | O | O | O |
Table 11: POS Purchase Reversal Message
5.5.3 VOID / Cancellation
The table below describes VOID / Cancellation message.
DE Field | Description | 0420 (Acquirer ➜ NCHL) | 0430 (NCHL ➜ Acquirer) | 0420 (NCHL ➜ Issuer) | 0430 (Issuer ➜ NCHL) |
---|---|---|---|---|---|
1 | Secondary bit map | C | C | C | C |
2 | Primary Account Number | M | M+ | M | M+ |
3 | Processing Code | M | M+ | M | M+ |
4 | Amount, Transaction | M | M+ | M | M+ |
5 | Amount, Settlement | C | C+ | C | C+ |
6 | Amount, card holder billing | C | C+ | C | C+ |
7 | Date/time transmission | M | M+ | M | M+ |
9 | Conversion rate, Settlement | C | C+ | C | C+ |
10 | Conversion rate, card holder billing | C | C+ | C | C+ |
11 | System trace audit number | M | M+ | M | M+ |
12 | Time, local transaction | M | M+ | M | M+ |
13 | Date, local transaction | M | M+ | M | M+ |
15 | Date, Settlement | C | C+ | C | C+ |
16 | Date, conversion | C | C+ | C | C+ |
18 | Merchant category code | M | M+ | M | M+ |
19 | Acquiring institution country code | M | M+ | M | M+ |
22 | POS entry mode | M | -- | M | -- |
23 | Card sequence number | C | C+ | C | C+ |
25 | POS condition code | M | -- | M | -- |
28 | Amount, Fee | C | C+ | C | C+ |
29 | Amount, Fee | C | C | C | C |
32 | Acquiring institution code | M | M+ | M | M+ |
33 | Forwarding institution code | C | C+ | C | C+ |
37 | Retrieval reference number | M | M+ | M | M+ |
38 | Authorization code | -- | M | -- | M |
39 | Response code | M | M | M | M |
41 | Card acceptor terminal ID | M | M+ | M | M+ |
42 | Card acceptor ID | M | -- | M | -- |
43 | Card acceptor name / location | M | -- | M | -- |
44 | Additional Response Data | -- | C | -- | C |
48 | Additional Data 1 | M | -- | M | -- |
49 | Currency code, transaction | M | M+ | M | M+ |
50 | Currency code, settlement | C | C+ | C | C+ |
51 | Currency code, card holder billing | C | C+ | C | C+ |
54 | Additional Amounts | -- | O | -- | O |
55 | Chip data | C | C | C | C |
56 | Customer Related Data | C | C+ | C | C+ |
61 | POS Data | M | -- | M | -- |
90 | Original Data Element | M | M+ | M | M+ |
102 | Account Identification 1 | O | O | O | O |
Table 12: VOID Message
5.5.4 Refund
The table below describes Refund message.
DE Field | Description | 0120 (Acquirer ➜ NCHL) | 0130 (NCHL ➜ Acquirer) | 0120 (NCHL ➜ Issuer) | 0130 (Issuer ➜ NCHL) |
---|---|---|---|---|---|
1 | Secondary bit map | C | C | C | C |
2 | Primary Account Number | M | M+ | M | M+ |
3 | Processing Code | M | M+ | M | M+ |
4 | Amount, Transaction | M | M+ | M | M+ |
5 | Amount, Settlement | C | C+ | C | C+ |
6 | Amount, card holder billing | C | C+ | C | C+ |
7 | Date/time transmission | M | M+ | M | M+ |
9 | Conversion rate, Settlement | C | C+ | C | C+ |
10 | Conversion rate, card holder billing | C | C+ | C | C+ |
11 | System trace audit number | M | M+ | M | M+ |
12 | Time, local transaction | M | M+ | M | M+ |
13 | Date, local transaction | M | M+ | M | M+ |
15 | Date, Settlement | C | C+ | C | C+ |
16 | Date, conversion | C | C+ | C | C+ |
18 | Merchant category code | M | M+ | M | M+ |
19 | Acquiring institution country code | M | M+ | M | M+ |
22 | POS entry mode | M | -- | M | -- |
23 | Card sequence number | C | C+ | C | C+ |
25 | POS condition code | M | -- | M | -- |
28 | Amount, Fee | C | C+ | C | C+ |
29 | Amount, Fee | C | C | C | C |
32 | Acquiring institution code | M | M+ | M | M+ |
33 | Forwarding institution code | C | C+ | C | C+ |
37 | Retrieval reference number | M | M+ | M | M+ |
38 | Authorization code | -- | M | -- | M |
39 | Response code | -- | M | -- | M |
41 | Card acceptor terminal ID | M | M+ | M | M+ |
42 | Card acceptor ID | M | -- | M | -- |
43 | Card acceptor name / location | M | -- | M | -- |
44 | Additional Response Data | -- | C | -- | C |
48 | Additional Data 1 | M | -- | M | -- |
49 | Currency code, transaction | M | M+ | M | M+ |
50 | Currency code, settlement | C | C+ | C | C+ |
51 | Currency code, card holder billing | C | C+ | C | C+ |
54 | Additional Amounts | -- | O | -- | O |
55 | Chip data | C | C | C | C |
56 | Customer Related Data | C | C+ | C | C+ |
61 | POS Data | M | -- | M | -- |
90 | Original Data Element | M | -- | M | -- |
102 | Account Identification 1 | O | O | O | O |
Table 13: Refund Message
5.5.5 Preauthorization
The table below describes Preauthorization message.
DE Field | Description | 0100 (Acquirer ➡ NCHL) | 0110 (NCHL ➡ Acquirer) | 0100 (NCHL ➡ Issuer) | 0110 (Issuer ➡ NCHL) |
---|---|---|---|---|---|
1 | Secondary bit map | C | C | C | C |
2 | Primary Account Number | M | M+ | M | M+ |
3 | Processing Code | M | M+ | M | M+ |
4 | Amount, Transaction | M | M+ | M | M+ |
5 | Amount, Settlement | C | C+ | C | C+ |
6 | Amount, card holder billing | C | C+ | C | C+ |
7 | Date/time transmission | M | M+ | M | M+ |
9 | Conversion rate, Settlement | C | C+ | C | C+ |
10 | Conversion rate, card holder billing | C | C+ | C | C+ |
11 | System trace audit number | M | M+ | M | M+ |
12 | Time, local transaction | M | M+ | M | M+ |
13 | Date, local transaction | M | M+ | M | M+ |
14 | Date, expiry | C | -- | C | -- |
15 | Date, Settlement | C | C+ | C | C+ |
16 | Date, conversion | C | C+ | C | C+ |
18 | Merchant category code | M | M+ | M | M+ |
19 | Acquiring institution country code | M | M+ | M | M+ |
22 | POS entry mode | M | -- | M | -- |
23 | Card sequence number | C | C+ | C | C+ |
25 | POS condition code | M | -- | M | -- |
28 | Amount, Fee | C | C+ | C | C+ |
29 | Amount, Fee | C | C | C | C |
32 | Acquiring institution code | M | M+ | M | M+ |
33 | Forwarding institution code | C | C+ | C | C+ |
35 | Track 2 data | C | -- | C | -- |
37 | Retrieval reference number | M | M+ | M | M+ |
38 | Authorization code | -- | M | -- | M |
39 | Response code | -- | M | -- | M |
41 | Card acceptor terminal ID | M | M+ | M | M+ |
42 | Card acceptor ID | M | -- | M | -- |
43 | Card acceptor name / location | M | -- | M | -- |
44 | Additional Response Data | -- | C | -- | -- |
45 | Track 1 data | C | -- | C | -- |
48 | Additional Data 1 | M | -- | M | -- |
49 | Currency code, transaction | M | M+ | M | M+ |
50 | Currency code, settlement | C | C+ | C | C+ |
51 | Currency code, card holder billing | C | C+ | C | C+ |
52 | PIN data | C | -- | C | -- |
54 | Additional Amounts | -- | O | -- | O |
55 | Chip data | C | C | C | C |
56 | Customer Related Data | C | C+ | C | C+ |
61 | POS Data | M | -- | M | -- |
102 | Account Identification 1 | O | O | O | O |
Table 14: Preauthorization Message
5.5.6 Preauthorization Reversal
The table below describes Preauthorization Reversal message.
DE Field | Description | 0420 (Acquirer ➡ NCHL) | 0430 (NCHL ➡ Acquirer) | 0420 (NCHL ➡ Issuer) | 0430 (Issuer ➡ NCHL) |
---|---|---|---|---|---|
1 | Secondary bit map | C | C | C | C |
2 | Primary Account Number | M | M+ | M | M+ |
3 | Processing Code | M | M+ | M | M+ |
4 | Amount, Transaction | M | M+ | M | M+ |
5 | Amount, Settlement | C | C+ | C | C+ |
6 | Amount, card holder billing | C | C+ | C | C+ |
7 | Date/time transmission | M | M+ | M | M+ |
9 | Conversion rate, Settlement | C | C+ | C | C+ |
10 | Conversion rate, card holder billing | C | C+ | C | C+ |
11 | System trace audit number | M | M+ | M | M+ |
12 | Time, local transaction | M | M+ | M | M+ |
13 | Date, local transaction | M | M+ | M | M+ |
15 | Date, Settlement | C | C+ | C | C+ |
16 | Date, conversion | C | C+ | C | C+ |
18 | Merchant category code | M | M+ | M | M+ |
19 | Acquiring institution country code | M | M+ | M | M+ |
22 | POS entry mode | M | -- | M | -- |
23 | Card sequence number | C | C+ | C | C+ |
25 | POS condition code | M | -- | M | -- |
28 | Amount, Fee | C | C+ | C | C+ |
29 | Amount, Fee | C | C | C | C |
32 | Acquiring institution code | M | M+ | M | M+ |
33 | Forwarding institution code | C | C+ | C | C+ |
37 | Retrieval reference number | M | M+ | M | M+ |
38 | Authorization code | -- | M | -- | M |
39 | Response code | M | M | M | M |
41 | Card acceptor terminal ID | M | M+ | M | M+ |
42 | Card acceptor ID | M | -- | M | -- |
43 | Card acceptor name / location | M | -- | M | -- |
44 | Additional Response Data | -- | C | -- | -- |
48 | Additional Data 1 | M | -- | M | -- |
49 | Currency code, transaction | M | M+ | M | M+ |
50 | Currency code, settlement | C | C+ | C | C+ |
51 | Currency code, card holder billing | C | C+ | C | C+ |
54 | Additional Amounts | -- | O | -- | O |
55 | Chip data | C | C | C | C |
56 | Customer Related Data | C | C+ | C | C+ |
61 | POS Data | M | -- | M | -- |
90 | Original Data Element | M | M+ | M | M+ |
102 | Account Identification 1 | O | O | O | O |
Table 15: Preauthorization Reversal Message
5.5.7 Preauthorization Cancellation
The table below describes Preauthorization Cancellation message.
DE Field | Description | 0420 (Acquirer ➡ NCHL) | 0430 (NCHL ➡ Acquirer) | 0420 (NCHL ➡ Issuer) | 0430 (Issuer ➡ NCHL) |
---|---|---|---|---|---|
1 | Secondary bit map | C | C | C | C |
2 | Primary Account Number | M | M+ | M | M+ |
3 | Processing Code | M | M+ | M | M+ |
4 | Amount, Transaction | M | M+ | M | M+ |
5 | Amount, Settlement | C | C+ | C | C+ |
6 | Amount, card holder billing | C | C+ | C | C+ |
7 | Date/time transmission | M | M+ | M | M+ |
9 | Conversion rate, Settlement | C | C+ | C | C+ |
10 | Conversion rate, card holder billing | C | C+ | C | C+ |
11 | System trace audit number | M | M+ | M | M+ |
12 | Time, local transaction | M | M+ | M | M+ |
13 | Date, local transaction | M | M+ | M | M+ |
15 | Date, Settlement | C | C+ | C | C+ |
16 | Date, conversion | C | C+ | C | C+ |
18 | Merchant category code | M | M+ | M | M+ |
19 | Acquiring institution country code | M | M+ | M | M+ |
22 | POS entry mode | -- | M | -- | M |
23 | Card sequence number | C | C+ | C | C+ |
25 | POS condition code | -- | M | -- | M |
28 | Amount, Fee | C | C+ | C | C+ |
29 | Amount, Fee | C | C | C | C |
32 | Acquiring institution code | M | M+ | M | M+ |
33 | Forwarding institution code | C | C+ | C | C+ |
37 | Retrieval reference number | M | M+ | M | M+ |
38 | Authorization code | -- | M | -- | M |
42 | Card acceptor ID | M | -- | M | -- |
43 | Card acceptor name / location | M | -- | M | -- |
44 | Additional Response Data | -- | C | -- | C |
48 | Additional Data 1 | M | -- | M | -- |
49 | Currency code, transaction | M | M+ | M | M+ |
50 | Currency code, settlement | C | C+ | C | C+ |
51 | Currency code, card holder billing | C | C+ | C | C+ |
54 | Additional Amounts | -- | O | -- | O |
55 | Chip data | C | C | C | C |
56 | Customer Related Data | C | C+ | C | C+ |
61 | POS Data | M | -- | M | -- |
90 | Original Data Element | M | M+ | M | M+ |
102 | Account Identification 1 | O | O | O | O |
Table 16: Preauthorization Cancellation Message
5.5.8 Preauthorization Completion
The table below describes Preauthorization Completion message.
DE Field | Description | 0100 (Acquirer ➡ NCHL) | 0110 (NCHL ➡ Acquirer) | 0100 (NCHL ➡ Issuer) | 0110 (Issuer ➡ NCHL) |
---|---|---|---|---|---|
1 | Secondary bit map | C | C | C | C |
2 | Primary Account Number | M | M+ | M | M+ |
3 | Processing Code | M | M+ | M | M+ |
4 | Amount, Transaction | M | M+ | M | M+ |
5 | Amount, Settlement | C | C+ | C | C+ |
6 | Amount, card holder billing | C | C+ | C | C+ |
7 | Date/time transmission | M | M+ | M | M+ |
9 | Conversion rate, Settlement | C | C+ | C | C+ |
10 | Conversion rate, card holder billing | C | C+ | C | C+ |
11 | System trace audit number | M | M+ | M | M+ |
12 | Time, local transaction | M | M+ | M | M+ |
13 | Date, local transaction | M | M+ | M | M+ |
14 | Date, expiry | C | -- | C | -- |
15 | Date, Settlement | C | C+ | C | C+ |
16 | Date, conversion | C | C+ | C | C+ |
18 | Merchant category code | M | M+ | M | M+ |
19 | Acquiring institution country code | M | M+ | M | M+ |
22 | POS entry mode | M | -- | M | -- |
23 | Card sequence number | C | C+ | C | C+ |
25 | POS condition code | M | -- | M | -- |
28 | Amount, Fee | C | C+ | C | C+ |
29 | Amount, Fee | C | C | C | C |
32 | Acquiring institution code | M | M+ | M | M+ |
33 | Forwarding institution code | C | C+ | C | C+ |
35 | Track 2 data | C | -- | C | -- |
37 | Retrieval reference number | M | M+ | M | M+ |
38 | Authorization code | -- | M | -- | M |
39 | Response code | -- | M | -- | M |
41 | Card acceptor terminal ID | M | M+ | M | M+ |
42 | Card acceptor ID | M | -- | M | -- |
44 | Additional Response Data | -- | C | -- | C |
45 | Track 1 data | C | -- | C | -- |
48 | Additional Data 1 | M | -- | M | -- |
49 | Currency code, transaction | M | M+ | M | M+ |
50 | Currency code, settlement | C | C+ | C | C+ |
51 | Currency code, card holder billing | C | C+ | C | C+ |
52 | PIN data | C | -- | C | -- |
54 | Additional Amounts | -- | O | -- | O |
55 | Chip data | C | C | C | C |
56 | Customer Related Data | C | C+ | C | C+ |
61 | POS Data | M | -- | M | -- |
102 | Account Identification 1 | O | O | O | O |
Table 17: Preauthorization Completion Message
5.5.9 Purchase with Cashback
The table below describes Purchase with Cashback message.
DE Field | Description | 0100 (Acquirer ➝ NCHL) | 0110 (NCHL ➝ Acquirer) | 0100 (NCHL ➝ Issuer) | 0110 (Issuer ➝ NCHL) |
---|---|---|---|---|---|
1 | Secondary bit map | C | C | C | C |
2 | Primary Account Number | M | M+ | M | M+ |
3 | Processing Code | M | M+ | M | M+ |
4 | Amount, Transaction | M | M+ | M | M+ |
5 | Amount, Settlement | C | C+ | C | C+ |
6 | Amount, card holder billing | C | C+ | C | C+ |
7 | Date/time transmission | M | M+ | M | M+ |
9 | Conversion rate, Settlement | C | C+ | C | C+ |
10 | Conversion rate, card holder billing | C | C+ | C | C+ |
11 | System trace audit number | M | M+ | M | M+ |
12 | Time, local transaction | M | M+ | M | M+ |
13 | Date, local transaction | M | M+ | M | M+ |
14 | Date, expiry | C | -- | C | -- |
15 | Date, Settlement | C | C+ | C | C+ |
16 | Date, conversion | C | C+ | C | C+ |
18 | Merchant category code | M | M+ | M | M+ |
19 | Acquiring institution country code | M | M+ | M | M+ |
22 | POS entry mode | -- | M | -- | M |
23 | Card sequence number | C | C+ | C | C+ |
25 | POS condition code | -- | M | -- | M |
28 | Amount, Fee | C | C+ | C | C+ |
29 | Amount, Fee | C | C | C | C |
32 | Acquiring institution code | M | M+ | M | M+ |
33 | Forwarding institution code | C | C+ | C | C+ |
35 | Track 2 data | -- | C | -- | C |
37 | Retrieval reference number | M | M+ | M | M+ |
38 | Authorization code | -- | M | -- | M |
39 | Response code | -- | M | -- | M |
41 | Card acceptor terminal ID | M | M+ | M | M+ |
42 | Card acceptor ID | M | -- | M | -- |
43 | Card acceptor name / location | M | -- | M | -- |
44 | Additional Response Data | -- | C | -- | C |
45 | Track 1 data | C | -- | C | -- |
48 | Additional Data 1 | M | -- | M | -- |
49 | Currency code, transaction | M | M+ | M | M+ |
50 | Currency code, settlement | C | C+ | C | C+ |
51 | Currency code, card holder billing | C | C+ | C | C+ |
52 | PIN data | C | -- | C | -- |
54 | Additional Amounts (Cashback) | M | M+ | M | M+ |
55 | Chip data | C | C | C | C |
56 | Customer Related Data | C | C+ | C | C+ |
61 | POS Data | M | -- | M | -- |
102 | Account Identification 1 | O | O | O | O |
Table 18: Purchase with Cashback Message
5.5.10 Purchase with TIP (Gratuity)
The table below describes Purchase with TIP message.
DE Field | Description | 0100 | 0110 | 0100 | 0110 |
---|---|---|---|---|---|
1 | Secondary bit map | C | C | C | C |
2 | Primary Account Number | M | M+ | M | M+ |
3 | Processing Code | M | M+ | M | M+ |
4 | Amount, Transaction | M | M+ | M | M+ |
5 | Amount, Settlement | C | C+ | C | C+ |
6 | Amount, card holder billing | C | C+ | C | C+ |
7 | Date/time transmission | M | M+ | M | M+ |
9 | Conversion rate, Settlement | C | C+ | C | C+ |
10 | Conversion rate, card holder billing | C | C+ | C | C+ |
11 | System trace audit number | M | M+ | M | M+ |
12 | Time, local transaction | M | M+ | M | M+ |
13 | Date, local transaction | M | M+ | M | M+ |
14 | Date, expiry | C | -- | C | -- |
15 | Date, Settlement | C | C+ | C | C+ |
16 | Date, conversion | C | C+ | C | C+ |
18 | Merchant category code | M | M+ | M | M+ |
19 | Acquiring institution country code | M | M+ | M | M+ |
22 | POS entry mode | M | -- | M | -- |
23 | Card sequence number | C | C+ | C | C+ |
25 | POS condition code | M | -- | M | -- |
28 | Amount, Fee | C | C+ | C | C+ |
29 | Amount, Fee | C | C | C | C |
32 | Acquiring institution code | M | M+ | M | M+ |
33 | Forwarding institution code | C | C+ | C | C+ |
35 | Track 2 data | C | -- | C | -- |
37 | Retrieval reference number | M | M+ | M | M+ |
38 | Authorization code | -- | M | -- | M |
39 | Response code | -- | M | -- | M |
41 | Card acceptor terminal ID | M | M+ | M | M+ |
42 | Card acceptor ID | M | -- | M | -- |
43 | Card acceptor name / location | M | -- | M | -- |
44 | Additional Response Data | -- | C | -- | C |
45 | Track 1 data | C | -- | C | -- |
48 | Additional Data 1 | M | -- | M | -- |
49 | Currency code, transaction | M | M+ | M | M+ |
50 | Currency code, settlement | C | C+ | C | C+ |
51 | Currency code, card holder billing | C | C+ | C | C+ |
52 | PIN data | C | -- | C | -- |
54 | Additional Amounts (Tips) | M | M+ | M | M+ |
55 | Chip data | C | C | C | C |
56 | Customer Related Data | C | C+ | C | C+ |
61 | POS Data | M | -- | M | -- |
102 | Account Identification 1 | O | O | O | O |
Table 19: Purchase with TIP (Gratuity) Message
5.5.11 Balance Inquiry
The table below describes Balance Inquiry message.
DE Field | Description | 0100/0200 | 0110/0210 | 0100/0200 | 0110/0210 |
---|---|---|---|---|---|
1 | Secondary bit map | C | C | C | C |
2 | Primary Account Number | M | M+ | M | M+ |
3 | Processing Code | M | M+ | M | M+ |
4 | Amount, Transaction | M | M+ | M | M+ |
5 | Amount, Settlement | C | C+ | C | C+ |
6 | Amount, card holder billing | C | C+ | C | C+ |
7 | Date/time transmission | M | M+ | M | M+ |
9 | Conversion rate, Settlement | C | C+ | C | C+ |
10 | Conversion rate, card holder billing | C | C+ | C | C+ |
11 | System trace audit number | M | M+ | M | M+ |
12 | Time, local transaction | M | M+ | M | M+ |
13 | Date, local transaction | M | M+ | M | M+ |
14 | Date, expiry | C | -- | C | -- |
15 | Date, Settlement | C | C+ | C | C+ |
16 | Date, conversion | C | C+ | C | C+ |
18 | Merchant category code | M | M+ | M | M+ |
19 | Acquiring institution country code | M | M+ | M | M+ |
22 | POS entry mode | M | -- | M | -- |
23 | Card sequence number | C | C+ | C | C+ |
25 | POS condition code | M | -- | M | -- |
28 | Amount, Fee | C | C+ | C | C+ |
29 | Amount, Fee | C | C | C | C |
32 | Acquiring institution code | M | M+ | M | M+ |
33 | Forwarding institution code | C | C+ | C | C+ |
35 | Track 2 data | C | -- | C | -- |
37 | Retrieval reference number | M | M+ | M | M+ |
38 | Authorization code | -- | M | -- | M |
39 | Response code | -- | M | -- | M |
41 | Card acceptor terminal ID | M | M+ | M | M+ |
42 | Card acceptor ID | M | -- | M | -- |
43 | Card acceptor name / location | M | -- | M | -- |
44 | Additional Response Data | -- | C | -- | C |
45 | Track 1 data | C | -- | C | -- |
48 | Additional Data 1 | M | -- | M | -- |
49 | Currency code, transaction | M | M+ | M | M+ |
50 | Currency code, settlement | C | C+ | C | C+ |
51 | Currency code, card holder billing | C | C+ | C | C+ |
52 | PIN data | C | -- | C | -- |
54 | Additional Amounts | -- | M | -- | M |
55 | Chip data | C | C | C | C |
56 | Customer Related Data | C | C+ | C | C+ |
61 | POS Data | M | -- | M | -- |
102 | Account Identification 1 | O | O | O | O |
Table 20: Balance Inquiry Message
5.5.12 Cash Withdrawal/ Fast Cash - ATM
The table below describes Cash Withdrawal / Fast Cash - ATM message.
DE Field | Description | 0200 | 0210 |
---|---|---|---|
1 | Secondary bit map | C | C |
2 | Primary Account Number | M | M+ |
3 | Processing Code | M | M+ |
4 | Amount, Transaction | M | M+ |
5 | Amount, Settlement | C | C+ |
6 | Amount, card holder billing | C | C+ |
7 | Date/time transmission | M | M+ |
9 | Conversion rate, Settlement | C | C+ |
10 | Conversion rate, card holder billing | C | C+ |
11 | System trace audit number | M | M+ |
12 | Time, local transaction | M | M+ |
13 | Date, local transaction | M | M+ |
14 | Date, expiry | C | -- |
15 | Date, Settlement | C | C+ |
16 | Date, conversion | C | C+ |
18 | Merchant category code | M | M+ |
19 | Acquiring institution country code | M | M+ |
22 | POS entry mode | -- | M |
23 | Card sequence number | C | C+ |
25 | POS condition code | -- | M |
28 | Amount, Fee | C | C+ |
29 | Amount, Fee | C | C |
32 | Acquiring institution code | M | M+ |
33 | Forwarding institution code | C | C+ |
35 | Track 2 data | C | -- |
37 | Retrieval reference number | M | M+ |
38 | Authorization code | -- | M |
39 | Response code | -- | M |
41 | Card acceptor terminal ID | M | M+ |
42 | Card acceptor ID | M | -- |
43 | Card acceptor name / location | M | -- |
44 | Additional Response Data | -- | C |
45 | Track 1 data | C | -- |
48 | Additional Data 1 | M | -- |
49 | Currency code, transaction | M | M+ |
50 | Currency code, settlement | C | C+ |
51 | Currency code, card holder billing | C | C+ |
52 | PIN data | C | -- |
54 | Additional Amounts | -- | O |
55 | Chip data | C | C |
56 | Customer Related Data | C | C+ |
61 | POS Data | M | -- |
102 | Account Identification 1 | O | O |
Table 21: Cash Withdrawal/ Fast Cash - ATM Message
5.5.13 Mini Statement
The table below describes Mini Statement message.
DE Field | Description | 0100/0200 | 0110/0210 |
---|---|---|---|
1 | Secondary bit map | C | C |
2 | Primary Account Number | M | M+ |
3 | Processing Code | M | M+ |
4 | Amount, Transaction | M | M+ |
5 | Amount, Settlement | C | C+ |
6 | Amount, card holder billing | C | C+ |
7 | Date/time transmission | M | M+ |
9 | Conversion rate, Settlement | C | C+ |
10 | Conversion rate, card holder billing | C | C+ |
11 | System trace audit number | M | M+ |
12 | Time, local transaction | M | M+ |
13 | Date, local transaction | M | M+ |
14 | Date, expiry | C | -- |
15 | Date, Settlement | C | C+ |
16 | Date, conversion | C | C+ |
18 | Merchant category code | M | M+ |
19 | Acquiring institution country code | M | M+ |
22 | POS entry mode | M | -- |
23 | Card sequence number | C | C+ |
25 | POS condition code | M | -- |
28 | Amount, Fee | C | C+ |
29 | Amount, Fee | C | C |
32 | Acquiring institution code | M | M+ |
33 | Forwarding institution code | C | C+ |
35 | Track 2 data | C | -- |
37 | Retrieval reference number | M | M+ |
38 | Authorization code | -- | M |
39 | Response code | -- | M |
41 | Card acceptor terminal ID | M | M+ |
42 | Card acceptor ID | M | -- |
43 | Card acceptor name / location | M | -- |
44 | Additional Response Data | -- | C |
45 | Track 1 data | C | -- |
48 | Additional Data 1 | M | -- |
49 | Currency code, transaction | M | M+ |
50 | Currency code, settlement | C | C+ |
51 | Currency code, card holder billing | C | C+ |
52 | PIN data | C | -- |
54 | Additional Amounts | -- | O |
55 | Chip data | C | C |
56 | Customer Related Data | C | C+ |
61 | POS Data | M | -- |
102 | Account Identification 1 | O | O |
120 | Additional Data 2 | -- | M |
Table 22: Mini Statement Message
5.5.14 PIN Change
The table below describes PIN Change message.
DE Field | Description | 0100/0200 | 0110/0210 |
---|---|---|---|
1 | Secondary bit map | C | C |
2 | Primary Account Number | M | M+ |
3 | Processing Code | M | M+ |
4 | Amount, Transaction | M | M+ |
5 | Amount, Settlement | C | C+ |
6 | Amount, card holder billing | C | C+ |
7 | Date/time transmission | M | M+ |
11 | System trace audit number | M | M+ |
12 | Time, local transaction | M | M+ |
13 | Date, local transaction | M | M+ |
14 | Date, expiry | C | -- |
15 | Date, Settlement | C | C+ |
16 | Date, conversion | C | C+ |
18 | Merchant category code | M | M+ |
19 | Acquiring institution country code | M | M+ |
22 | POS entry mode | -- | M |
23 | Card sequence number | C+ | C |
25 | POS condition code | -- | M |
28 | Amount, Fee | C+ | C |
29 | Amount, Fee | C | C |
32 | Acquiring institution code | M+ | M |
33 | Forwarding institution code | C+ | C |
35 | Track 2 data | -- | C |
37 | Retrieval reference number | M+ | M |
38 | Authorization code | -- | M |
39 | Response code | -- | M |
41 | Card acceptor terminal ID | M+ | M |
42 | Card acceptor ID | -- | M |
43 | Card acceptor name / location | -- | M |
44 | Additional Response Data | -- | C |
45 | Track 1 data | C | -- |
48 | Additional Data 1 | -- | M |
49 | Currency code, transaction | M+ | M |
50 | Currency code, settlement | C+ | C |
52 | PIN data | -- | C |
55 | Chip data | C | C |
56 | Customer Related Data | C+ | C |
61 | POS Data | -- | M |
102 | Account Identification 1 | O | O |
120 | Additional Data 2 | -- | M |
Table 23: PIN Change Message
5.5.15 Reversal – ATM Cash withdrawal/ Fast Cash
The table below describes Reversal – ATM Cash withdrawal/ Fast Cash message.
DE Field | Description | 0420 | 0430 | 0420 | 0430 |
---|---|---|---|---|---|
1 | Secondary bit map | C | C | C | C |
2 | Primary Account Number | M | M+ | M | M+ |
3 | Processing Code | M | M+ | M | M+ |
4 | Amount, Transaction | M | M+ | M | M+ |
5 | Amount, Settlement | C | C+ | C | C+ |
6 | Amount, card holder billing | C | C+ | C | C+ |
7 | Date/time transmission | M | M+ | M | M+ |
9 | Conversion rate, Settlement | C | C+ | C | C+ |
10 | Conversion rate, card holder billing | C | C+ | C | C+ |
11 | System trace audit number | M | M+ | M | M+ |
12 | Time, local transaction | M | M+ | M | M+ |
13 | Date, local transaction | M | M+ | M | M+ |
15 | Date, Settlement | C | C+ | C | C+ |
16 | Date, conversion | C | C+ | C | C+ |
18 | Merchant category code | M | M+ | M | M+ |
19 | Acquiring institution country code | M | M+ | M | M+ |
22 | POS entry mode | -- | M | -- | M |
23 | Card sequence number | C | C+ | C | C+ |
25 | POS condition code | M | -- | M | -- |
28 | Amount, Fee | C | C+ | C | C+ |
29 | Amount, Fee | C | C | C | C |
32 | Acquiring institution code | M | M+ | M | M+ |
33 | Forwarding institution code | C | C+ | C | C+ |
37 | Retrieval reference number | M | M+ | M | M+ |
38 | Authorization code | -- | M | -- | M |
39 | Response code | M | M | M | M |
41 | Card acceptor terminal ID | M | M+ | M | M+ |
42 | Card acceptor ID | -- | M | -- | M |
43 | Card acceptor name / location | -- | M | -- | M |
44 | Additional Response Data | -- | C | -- | C |
48 | Additional Data 1 | M | -- | M | -- |
49 | Currency code, transaction | M | M+ | M | M+ |
50 | Currency code, settlement | C | C+ | C | C+ |
51 | Currency code, card holder billing | C | C+ | C | C+ |
54 | Additional Amounts | -- | O | -- | O |
55 | Chip data | C | C | C | C |
56 | Customer Related Data | C | C+ | C | C+ |
61 | POS Data | M | -- | M | -- |
90 | Original Data Element | M | M+ | M | M+ |
102 | Account Identification 1 | O | O | O | O |
Table 24: Reversal – ATM Cash withdrawal/ Fast Cash Message
5.5.16 Cheque Book Request
The table below describes Cheque Book Request message.
DE Field | Description | 0200 (Acquirer ➔ NCHL) | 0210 (NCHL ➔ Acquirer) | 0200 (NCHL ➔ Issuer) | 0210 (Issuer ➔ NCHL) |
---|---|---|---|---|---|
1 | Secondary bit map | C | C | C | C |
2 | Primary Account Number | M | M+ | M | M+ |
3 | Processing Code | M | M+ | M | M+ |
4 | Amount, Transaction | M | M+ | M | M+ |
5 | Amount, Settlement | C | C+ | C | C+ |
6 | Amount, card holder billing | C | C+ | C | C+ |
7 | Date/time transmission | M | M+ | M | M+ |
9 | Conversion rate, Settlement | C | C+ | C | C+ |
10 | Conversion rate, card holder billing | C | C+ | C | C+ |
11 | System trace audit number | M | M+ | M | M+ |
12 | Time, local transaction | M | M+ | M | M+ |
13 | Date, local transaction | M | M+ | M | M+ |
14 | Date, expiry | C | -- | C | -- |
15 | Date, Settlement | C | C+ | C | C+ |
16 | Date, conversion | C | C+ | C | C+ |
18 | Merchant category code | M | M+ | M | M+ |
19 | Acquiring institution country code | M | M+ | M | M+ |
22 | POS entry mode | M | -- | M | -- |
23 | Card sequence number | C | C+ | C | C+ |
25 | POS condition code | M | -- | M | -- |
28 | Amount, Fee | C | C+ | C | C+ |
29 | Amount, Fee | C | C | C | C |
32 | Acquiring institution code | M | M+ | M | M+ |
33 | Forwarding institution code | C | C+ | C | C+ |
35 | Track 2 data | C | -- | C | -- |
37 | Retrieval reference number | M | M+ | M | M+ |
38 | Authorization code | -- | M | -- | M |
39 | Response code | -- | M | -- | M |
41 | Card acceptor terminal ID | M | M+ | M | M+ |
42 | Card acceptor ID | M | -- | M | -- |
43 | Card acceptor name / location | M | -- | M | -- |
44 | Additional Response Data | -- | C | -- | -- |
45 | Track 1 data | C | -- | C | -- |
48 | Additional Data 1 | M | -- | M | -- |
49 | Currency code, transaction | M | M+ | M | M+ |
50 | Currency code, settlement | C | C+ | C | C+ |
51 | Currency code, card holder billing | C | C+ | C | C+ |
52 | PIN data | C | -- | C | -- |
55 | Chip data | C | C | C | C |
56 | Customer Related Data | C | C+ | C | C+ |
61 | POS Data | M | -- | M | -- |
102 | Account Identification 1 | O | O | O | O |
120 | Additional Data 2 | C | C+ | C | C+ |
Table 25: Cheque Book Request Message
5.5.17 Statement Request
The table below describes Statement Request message.
DE Field | Description | 0200 (Acquirer ➔ NCHL) | 0210 (NCHL ➔ Acquirer) | 0200 (NCHL ➔ Issuer) | 0210 (Issuer ➔ NCHL) |
---|---|---|---|---|---|
1 | Secondary bit map | C | C | C | C |
2 | Primary Account Number | M | M+ | M | M+ |
3 | Processing Code | M | M+ | M | M+ |
4 | Amount, Transaction | M | M+ | M | M+ |
5 | Amount, Settlement | C | C+ | C | C+ |
6 | Amount, card holder billing | C | C+ | C | C+ |
7 | Date/time transmission | M | M+ | M | M+ |
9 | Conversion rate, Settlement | C | C+ | C | C+ |
10 | Conversion rate, card holder billing | C | C+ | C | C+ |
11 | System trace audit number | M | M+ | M | M+ |
12 | Time, local transaction | M | M+ | M | M+ |
13 | Date, local transaction | M | M+ | M | M+ |
14 | Date, expiry | C | -- | C | -- |
15 | Date, Settlement | C | C+ | C | C+ |
16 | Date, conversion | C | C+ | C | C+ |
18 | Merchant category code | M | M+ | M | M+ |
19 | Acquiring institution country code | M | M+ | M | M+ |
22 | POS entry mode | M | -- | M | -- |
23 | Card sequence number | C | C+ | C | C+ |
25 | POS condition code | M | -- | M | -- |
28 | Amount, Fee | C | C+ | C | C+ |
29 | Amount, Fee | C | C | C | C |
32 | Acquiring institution code | M | M+ | M | M+ |
33 | Forwarding institution code | C | C+ | C | C+ |
35 | Track 2 data | C | -- | C | -- |
37 | Retrieval reference number | M | M+ | M | M+ |
38 | Authorization code | -- | M | -- | M |
39 | Response code | -- | M | -- | M |
41 | Card acceptor terminal ID | M | M+ | M | M+ |
42 | Card acceptor ID | M | -- | M | -- |
43 | Card acceptor name / location | M | -- | M | -- |
44 | Additional Response Data | -- | C | -- | -- |
45 | Track 1 data | C | -- | C | -- |
48 | Additional Data 1 | M | -- | M | -- |
49 | Currency code, transaction | M | M+ | M | M+ |
50 | Currency code, settlement | C | C+ | C | C+ |
51 | Currency code, card holder billing | C | C+ | C | C+ |
52 | PIN data | C | -- | C | -- |
55 | Chip data | C | C | C | C |
56 | Customer Related Data | C | C+ | C | C+ |
61 | POS Data | M | -- | M | -- |
102 | Account Identification 1 | O | O | O | O |
120 | Additional Data 2 | C | C+ | C | C+ |
Table 26: Statement Request Message
5.5.18 Fund Transfer
5.5.18.1 Fund Transfer Debit Leg
The table below describes Fund Transfer Debit Leg message.
DE Field | Description | 0200 (Acquirer ➔ NCHL) | 0210 (NCHL ➔ Acquirer) | 0200 (NCHL ➔ Issuer) | 0210 (Issuer ➔ NCHL) |
---|---|---|---|---|---|
1 | Secondary bit map | C | C | C | C |
2 | Primary Account Number | M | M+ | M | M+ |
3 | Processing Code | M | M+ | M | M+ |
4 | Amount, Transaction | M | M+ | M | M+ |
5 | Amount, Settlement | C | C+ | C | C+ |
6 | Amount, card holder billing | C | C+ | C | C+ |
7 | Date/time transmission | M | M+ | M | M+ |
9 | Conversion rate, Settlement | C | C+ | C | C+ |
10 | Conversion rate, card holder billing | C | C+ | C | C+ |
11 | System trace audit number | M | M+ | M | M+ |
12 | Time, local transaction | M | M+ | M | M+ |
13 | Date, local transaction | M | M+ | M | M+ |
14 | Date, expiry | C | -- | C | -- |
15 | Date, Settlement | C | C+ | C | C+ |
16 | Date, conversion | C | C+ | C | C+ |
18 | Merchant category code | M | M+ | M | M+ |
19 | Acquiring institution country code | M | M+ | M | M+ |
22 | POS entry mode | M | -- | M | -- |
23 | Card sequence number | C | C+ | C | C+ |
25 | POS condition code | M | -- | M | -- |
28 | Amount, Fee | C | C+ | C | C+ |
28 | Amount, Fee | C | C+ | C | C+ |
29 | Amount, Fee | C | C | C | C |
32 | Acquiring institution code | M | M+ | M | M+ |
33 | Forwarding institution code | C | C+ | C | C+ |
35 | Track 2 data | C | -- | C | -- |
37 | Retrieval reference number | M | M+ | M | M+ |
38 | Authorization code | -- | M | -- | M |
39 | Response code | -- | M | -- | M |
41 | Card acceptor terminal ID | M | M+ | M | M+ |
42 | Card acceptor ID | M | -- | M | -- |
43 | Card acceptor name / location | M | -- | M | -- |
44 | Additional Response Data | -- | C | -- | -- |
45 | Track 1 data | C | -- | C | -- |
48 | Additional Data 1 | M | -- | M | -- |
49 | Currency code, transaction | M | M+ | M | M+ |
50 | Currency code, settlement | C | C+ | C | C+ |
51 | Currency code, card holder billing | C | C+ | C | C+ |
52 | PIN data | C | -- | C | -- |
55 | Chip data | C | C | C | C |
56 | Customer Related Data | C | C+ | C | C+ |
61 | POS Data | M | -- | M | -- |
102 | Account Identification 1 | O | O | O | O |
103 | Account Identification 2 | O | O | O | O |
120 | Additional Data 2 | C | C+ | C | C+ |
5.5.18.2 Fund Transfer Credit Leg
The table below describes Fund Transfer Credit Leg message.
DE Field | Description | 0200 (Acquirer ➔ NCHL) | 0210 (NCHL ➔ Acquirer) | 0200 (NCHL ➔ Issuer) | 0210 (Issuer ➔ NCHL) |
---|---|---|---|---|---|
1 | Secondary bit map | C | C | C | C |
2 | Primary Account Number | M | M+ | M | M+ |
3 | Processing Code | M | M+ | M | M+ |
4 | Amount, Transaction | M | M+ | M | M+ |
5 | Amount, Settlement | C | C+ | C | C+ |
6 | Amount, card holder billing | C | C+ | C | C+ |
7 | Date/time transmission | M | M+ | M | M+ |
9 | Conversion rate, Settlement | C | C+ | C | C+ |
10 | Conversion rate, card holder billing | C | C+ | C | C+ |
11 | System trace audit number | M | M+ | M | M+ |
12 | Time, local transaction | M | M+ | M | M+ |
13 | Date, local transaction | M | M+ | M | M+ |
14 | Date, expiry | C | -- | C | -- |
15 | Date, Settlement | C | C+ | C | C+ |
16 | Date, conversion | C | C+ | C | C+ |
18 | Merchant category code | M | M+ | M | M+ |
19 | Acquiring institution country code | M | M+ | M | M+ |
22 | POS entry mode | M | -- | M | -- |
23 | Card sequence number | C | C+ | C | C+ |
25 | POS condition code | M | -- | M | -- |
28 | Amount, Fee | C | C+ | C | C+ |
29 | Amount, Fee | C | C | C | C |
32 | Acquiring institution code | M | M+ | M | M+ |
33 | Forwarding institution code | C | C+ | C | C+ |
35 | Track 2 data | C | -- | C | -- |
37 | Retrieval reference number | M | M+ | M | M+ |
38 | Authorization code | -- | M | -- | M |
39 | Response code | -- | M | -- | M |
41 | Card acceptor terminal ID | M | M+ | M | M+ |
42 | Card acceptor ID | M | -- | M | -- |
43 | Card acceptor name / location | M | -- | M | -- |
44 | Additional Response Data | -- | C | -- | -- |
45 | Track 1 data | C | -- | C | -- |
48 | Additional Data 1 | M | -- | M | -- |
49 | Currency code, transaction | M | M+ | M | M+ |
50 | Currency code, settlement | C | C+ | C | C+ |
51 | Currency code, card holder billing | C | C+ | C | C+ |
52 | PIN data | C | -- | C | -- |
55 | Chip data | C | C | C | C |
56 | Customer Related Data | C | C+ | C | C+ |
61 | POS Data | M | -- | M | -- |
102 | Account Identification 1 | O | O | O | O |
103 | Account Identification 2 | O | O | O | O |
120 | Additional Data 2 | C | C+ | C | C+ |
Table 28: Fund Transfer Credit Leg Message
5.5.19 e-commerce Purchase
The table below describes e-commerce Purchase message.
DE Field | Description | 0100 (Acquirer ➔ NCHL) | 0110 (NCHL ➔ Acquirer) | 0100 (NCHL ➔ Issuer) | 0110 (Issuer ➔ NCHL) |
---|---|---|---|---|---|
1 | Secondary bit map | C | C | C | C |
2 | Primary Account Number | M | M+ | M | M+ |
3 | Processing Code | M | M+ | M | M+ |
4 | Amount, Transaction | M | M+ | M | M+ |
5 | Amount, Settlement | C | C+ | C | C+ |
6 | Amount, card holder billing | C | C+ | C | C+ |
7 | Date/time transmission | M | M+ | M | M+ |
9 | Conversion rate, Settlement | C | C+ | C | C+ |
10 | Conversion rate, card holder billing | C | C+ | C | C+ |
11 | System trace audit number | M | M+ | M | M+ |
12 | Time, local transaction | M | M+ | M | M+ |
13 | Date, local transaction | M | M+ | M | M+ |
14 | Date, expiry | C | -- | C | -- |
15 | Date, Settlement | C | C+ | C | C+ |
16 | Date, conversion | C | C+ | C | C+ |
18 | Merchant category code | M | M+ | M | M+ |
19 | Acquiring institution country code | M | M+ | M | M+ |
22 | POS entry mode | M | -- | M | -- |
23 | Card sequence number | C | C+ | C | C+ |
25 | POS condition code | M | -- | M | -- |
28 | Amount, Fee | C | C+ | C | C+ |
29 | Amount, Fee | C | C | C | C |
32 | Acquiring institution code | M | M+ | M | M+ |
33 | Forwarding institution code | C | C+ | C | C+ |
35 | Track 2 data | C | -- | C | -- |
37 | Retrieval reference number | M | M+ | M | M+ |
38 | Authorization code | -- | M | -- | M |
39 | Response code | -- | M | -- | M |
41 | Card acceptor terminal ID | M | M+ | M | M+ |
42 | Card acceptor ID | M | -- | M | -- |
43 | Card acceptor name / location | M | -- | M | -- |
44 | Additional Response Data | -- | C | -- | -- |
45 | Track 1 data | C | -- | C | -- |
48 | Additional Data 1 | M | -- | M | -- |
49 | Currency code, transaction | M | M+ | M | M+ |
50 | Currency code, settlement | C | C+ | C | C+ |
51 | Currency code, card holder billing | C | C+ | C | C+ |
52 | PIN data | C | -- | C | -- |
54 | Additional Amounts | -- | O | -- | O |
55 | Chip data | C | C | C | C |
56 | Customer Related Data | C | C+ | C | C+ |
61 | POS Data | M | -- | M | -- |
102 | Account Identification 1 | O | O | O | O |
Table 29: e-commerce Purchase Message
5.5.20 Account Verification
The table below describes Account Verification message.
DE Field | Description | 0100 (Acquirer ➔ NCHL) | 0110 (NCHL ➔ Acquirer) | 0200 (Acquirer ➔ Issuer) | 0210 (Issuer ➔ Acquirer) |
---|---|---|---|---|---|
1 | Secondary bit map | C | C | C | C |
2 | Primary Account Number | M | M+ | M | M+ |
3 | Processing Code | M | M+ | M | M+ |
4 | Amount, Transaction | M | M+ | M | M+ |
5 | Amount, Settlement | C | C+ | C | C+ |
6 | Amount, card holder billing | C | C+ | C | C+ |
7 | Date/time transmission | M | M+ | M | M+ |
9 | Conversion rate, Settlement | C | C+ | C | C+ |
10 | Conversion rate, card holder billing | C | C+ | C | C+ |
11 | System trace audit number | M | M+ | M | M+ |
12 | Time, local transaction | M | M+ | M | M+ |
13 | Date, local transaction | M | M+ | M | M+ |
14 | Date, expiry | C | -- | C | -- |
15 | Date, Settlement | C | C+ | C | C+ |
16 | Date, conversion | C | C+ | C | C+ |
18 | Merchant category code | M | M+ | M | M+ |
19 | Acquiring institution country code | M | M+ | M | M+ |
22 | POS entry mode | M | -- | M | -- |
25 | POS condition code | M | -- | M | -- |
28 | Amount, Fee | C | C+ | C | C+ |
29 | Amount, Fee | C | C | C | C |
32 | Acquiring institution code | M | M+ | M | M+ |
33 | Forwarding institution code | C | C+ | C | C+ |
37 | Retrieval reference number | M | M+ | M | M+ |
38 | Authorization code | -- | M | -- | M |
39 | Response code | -- | M | -- | M |
41 | Card acceptor terminal ID | M | M+ | M | M+ |
42 | Card acceptor ID | M | -- | M | -- |
43 | Card acceptor name / location | M | -- | M | -- |
44 | Additional Response Data | -- | C | -- | -- |
48 | Additional Data 1 | M | -- | M | -- |
49 | Currency code, transaction | M | M+ | M | M+ |
50 | Currency code, settlement | C | C+ | C | C+ |
51 | Currency code, card holder billing | C | C+ | C | C+ |
56 | Customer Related Data | C | C+ | C | C+ |
61 | POS Data | M | -- | M | -- |
63 | Account Verification Service (AVS) | C | -- | C | -- |
102 | Account Identification 1 | O | O | O | O |
Table 30: Account Verification Transaction Message
5.5.21 Original Credit Transaction (OCT)
The table below describes Original Credit Transaction (OCT) message.
DE Field | Description | 0100 (Acquirer ➔ NCHL) | 0110 (NCHL ➔ Acquirer) | 0200 (NCHL ➔ Issuer) | 0210 (Issuer ➔ NCHL) |
---|---|---|---|---|---|
1 | Secondary bit map | C | C | C | C |
2 | Primary Account Number | M | M+ | M | M+ |
3 | Processing Code | M | M+ | M | M+ |
4 | Amount, Transaction | M | M+ | M | M+ |
5 | Amount, Settlement | C | C+ | C | C+ |
6 | Amount, card holder billing | C | C+ | C | C+ |
7 | Date/time transmission | M | M+ | M | M+ |
9 | Conversion rate, Settlement | C | C+ | C | C+ |
10 | Conversion rate, card holder billing | C | C+ | C | C+ |
11 | System trace audit number | M | M+ | M | M+ |
12 | Time, local transaction | M | M+ | M | M+ |
13 | Date, local transaction | M | M+ | M | M+ |
14 | Date, expiry | C | -- | C | -- |
15 | Date, Settlement | C | C+ | C | C+ |
16 | Date, conversion | C | C+ | C | C+ |
18 | Merchant category code | M | M+ | M | M+ |
19 | Acquiring institution country code | M | M+ | M | M+ |
22 | POS entry mode | M | -- | M | -- |
25 | POS condition code | M | -- | M | -- |
28 | Amount, Fee | C | C+ | C | C+ |
29 | Amount, Fee | C | C | C | C |
32 | Acquiring institution code | M | M+ | M | M+ |
33 | Forwarding institution code | C | C+ | C | C+ |
37 | Retrieval reference number | M | M+ | M | M+ |
38 | Authorization code | -- | M | -- | M |
39 | Response code | -- | M | -- | M |
41 | Card acceptor terminal ID | M | M+ | M | M+ |
42 | Card acceptor ID | M | -- | M | -- |
43 | Card acceptor name / location | M | -- | M | -- |
44 | Additional Response Data | -- | C | -- | -- |
48 | Additional Data 1 | M | -- | M | -- |
49 | Currency code, transaction | M | M+ | M | M+ |
50 | Currency code, settlement | C | C+ | C | C+ |
51 | Currency code, card holder billing | C | C+ | C | C+ |
56 | Customer Related Data | C | C+ | C | C+ |
61 | POS Data | M | -- | M | -- |
104 | OCT Data | C | C+ | C | C+ |
Table 31: Original Credit Transaction Message
5.5.22 e-commerce Bill Payment
The table below describes e-commerce Bill Payment message.
DE Field | Description | 0100/0200 | 0110/0210 | 0100/0200 | 0110/0210 |
---|---|---|---|---|---|
1 | Secondary bit map | C | C | C | C |
2 | Primary Account Number | M | M+ | M | M+ |
3 | Processing Code | M | M+ | M | M+ |
4 | Amount, Transaction | M | M+ | M | M+ |
5 | Amount, Settlement | C | C+ | C | C+ |
6 | Amount, card holder billing | C | C+ | C | C+ |
7 | Date/time transmission | M | M+ | M | M+ |
9 | Conversion rate, Settlement | C | C+ | C | C+ |
10 | Conversion rate, card holder billing | C | C+ | C | C+ |
11 | System trace audit number | M | M+ | M | M+ |
12 | Time, local transaction | M | M+ | M | M+ |
13 | Date, local transaction | M | M+ | M | M+ |
14 | Date, expiry | C | -- | C | -- |
15 | Date, Settlement | C | C+ | C | C+ |
16 | Date, conversion | C | C+ | C | C+ |
18 | Merchant category code | M | M+ | M | M+ |
19 | Acquiring institution country code | M | M+ | M | M+ |
22 | POS entry mode | M | -- | M | -- |
23 | Card sequence number | C | C+ | C | C+ |
25 | POS condition code | M | -- | M | -- |
28 | Amount, Fee | C | C+ | C | C+ |
29 | Amount, Fee | C | C | C | C |
32 | Acquiring institution code | M | M+ | M | M+ |
33 | Forwarding institution code | C | C+ | C | C+ |
35 | Track 2 data | C | -- | C | -- |
37 | Retrieval reference number | M | M+ | M | M+ |
38 | Authorization code | -- | M | -- | M |
39 | Response code | -- | M | -- | M |
41 | Card acceptor terminal ID | M | M+ | M | M+ |
42 | Card acceptor ID | M | -- | M | -- |
43 | Card acceptor name / location | M | -- | M | -- |
44 | Additional Response Data | -- | C | -- | -- |
45 | Track 1 data | C | -- | C | -- |
48 | Additional Data 1 | M | -- | M | -- |
49 | Currency code, transaction | M | M+ | M | M+ |
50 | Currency code, settlement | C | C+ | C | C+ |
51 | Currency code, card holder billing | C | C+ | C | C+ |
52 | PIN data | C | -- | C | -- |
55 | Chip data | C | C | C | C |
56 | Customer Related Data | C | C+ | C | C+ |
61 | POS Data | M | -- | M | -- |
102 | Account Identification 1 | O | O | O | O |
120 | Additional Data 2 | C | C+ | C | C+ |
Table 32: e-commerce Bill Payment Message
5.5.23 e-commerce Payment (Government Revenue Payment)
The table below describes e-commerce Payment (Government Revenue Payment) message.
DE Field | Description | 0100/0200 | 0110/0210 | 0100/0200 | 0110/0210 |
---|---|---|---|---|---|
1 | Secondary bit map | C | C | C | C |
2 | Primary Account Number | M | M+ | M | M+ |
3 | Processing Code | M | M+ | M | M+ |
4 | Amount, Transaction | M | M+ | M | M+ |
5 | Amount, Settlement | C | C+ | C | C+ |
6 | Amount, card holder billing | C | C+ | C | C+ |
7 | Date/time transmission | M | M+ | M | M+ |
9 | Conversion rate, Settlement | C | C+ | C | C+ |
10 | Conversion rate, card holder billing | C | C+ | C | C+ |
11 | System trace audit number | M | M+ | M | M+ |
12 | Time, local transaction | M | M+ | M | M+ |
13 | Date, local transaction | M | M+ | M | M+ |
14 | Date, expiry | C | -- | C | -- |
15 | Date, Settlement | C | C+ | C | C+ |
16 | Date, conversion | C | C+ | C | C+ |
18 | Merchant category code | M | M+ | M | M+ |
19 | Acquiring institution country code | M | M+ | M | M+ |
22 | POS entry mode | M | -- | M | -- |
23 | Card sequence number | C | C+ | C | C+ |
25 | POS condition code | M | -- | M | -- |
28 | Amount, Fee | C | C+ | C | C |
29 | Amount, Fee | C | C | C | C |
32 | Acquiring institution code | M | M+ | M | M+ |
33 | Forwarding institution code | C | C+ | C | C+ |
35 | Track 2 data | C | -- | C | -- |
37 | Retrieval reference number | M | M+ | M | M+ |
38 | Authorization code | -- | M | -- | M |
39 | Response code | -- | M | -- | M |
41 | Card acceptor terminal ID | M | M+ | M | M+ |
42 | Card acceptor ID | M | -- | M | -- |
43 | Card acceptor name / location | M | -- | M | -- |
44 | Additional Response Data | -- | C | -- | -- |
45 | Track 1 data | C | -- | C | -- |
48 | Additional Data 1 | M | -- | M | -- |
49 | Currency code, transaction | M | M+ | M | M+ |
50 | Currency code, settlement | C | C+ | C | C+ |
51 | Currency code, card holder billing | C | C+ | C | C+ |
52 | PIN data | C | -- | C | -- |
55 | Chip data | C | C | C | C |
56 | Customer Related Data | C | C+ | C | C+ |
61 | POS Data | M | -- | M | -- |
102 | Account Identification 1 | O | O | O | O |
120 | Additional Data 2 | C | C+ | C | C+ |
Table 33: e-commerce Payment (Government Revenue Payment) Message
5.5.24 e-commerce Payment (Recurring Payment)
The table below describes e-commerce Payment (Recurring Payment) message.
DE Field | Description | 0100/0200 (Acquirer ➔ NCHL) | 0110/0210 (NCHL ➔ Acquirer) | 0100/0200 (NCHL ➔ Issuer) | 0110/0210 (Issuer ➔ NCHL) |
---|---|---|---|---|---|
1 | Secondary bit map | C | C | C | C |
2 | Primary Account Number | M | M+ | M | M+ |
3 | Processing Code | M | M+ | M | M+ |
4 | Amount, Transaction | M | M+ | M | M+ |
5 | Amount, Settlement | C | C+ | C | C+ |
6 | Amount, card holder billing | C | C+ | C | C+ |
7 | Date/time transmission | M | M+ | M | M+ |
9 | Conversion rate, Settlement | C | C+ | C | C+ |
10 | Conversion rate, card holder billing | C | C+ | C | C+ |
11 | System trace audit number | M | M+ | M | M+ |
12 | Time, local transaction | M | M+ | M | M+ |
13 | Date, local transaction | M | M+ | M | M+ |
14 | Date, expiry | C | -- | C | -- |
15 | Date, Settlement | C | C+ | C | C+ |
16 | Date, conversion | C | C+ | C | C+ |
18 | Merchant category code | M | M+ | M | M+ |
19 | Acquiring institution country code | M | M+ | M | M+ |
22 | POS entry mode | M | -- | M | -- |
23 | Card sequence number | C | C+ | C | C+ |
25 | POS condition code | M | -- | M | -- |
28 | Amount, Fee | C | C+ | C | C |
29 | Amount, Fee | C | C | C | C |
32 | Acquiring institution code | M | M+ | M | M+ |
33 | Forwarding institution code | C | C+ | C | C+ |
35 | Track 2 data | C | -- | C | -- |
37 | Retrieval reference number | M | M+ | M | M+ |
38 | Authorization code | -- | M | -- | M |
39 | Response code | -- | M | -- | M |
41 | Card acceptor terminal ID | M | M+ | M | M+ |
42 | Card acceptor ID | M | -- | M | -- |
43 | Card acceptor name / location | M | -- | M | -- |
44 | Additional Response Data | -- | C | -- | -- |
45 | Track 1 data | C | -- | C | -- |
48 | Additional Data 1 | M | -- | M | -- |
49 | Currency code, transaction | M | M+ | M | M+ |
50 | Currency code, settlement | C | C+ | C | C+ |
51 | Currency code, card holder billing | C | C+ | C | C+ |
52 | PIN data | C | -- | C | -- |
55 | Chip data | C | C | C | C |
56 | Customer Related Data | C | C+ | C | C+ |
61 | POS Data | M | -- | M | -- |
102 | Account Identification 1 | O | O | O | O |
120 | Additional Data 2 | C | C+ | C | C+ |
Table 34: e-commerce Payment (Recurring Payment) Message
5.5.25 e-commerce Payment (Insurance Payment)
The table below describes e-commerce Payment (Insurance Payment) message.
DE Field | Description | 0100/0200 (Acquirer ➔ NCHL) | 0110/0210 (NCHL ➔ Acquirer) | 0100/0200 (NCHL ➔ Issuer) | 0110/0210 (Issuer ➔ NCHL) |
---|---|---|---|---|---|
1 | Secondary bit map | C | C | C | C |
2 | Primary Account Number | M | M+ | M | M+ |
3 | Processing Code | M | M+ | M | M+ |
4 | Amount, Transaction | M | M+ | M | M+ |
5 | Amount, Settlement | C | C+ | C | C+ |
6 | Amount, card holder billing | C | C+ | C | C+ |
7 | Date/time transmission | M | M+ | M | M+ |
9 | Conversion rate, Settlement | C | C+ | C | C+ |
10 | Conversion rate, card holder billing | C | C+ | C | C+ |
11 | System trace audit number | M | M+ | M | M+ |
12 | Time, local transaction | M | M+ | M | M+ |
13 | Date, local transaction | M | M+ | M | M+ |
14 | Date, expiry | C | -- | C | -- |
15 | Date, Settlement | C | C+ | C | C+ |
16 | Date, conversion | C | C+ | C | C+ |
18 | Merchant category code | M | M+ | M | M+ |
19 | Acquiring institution country code | M | M+ | M | M+ |
22 | POS entry mode | M | -- | M | -- |
23 | Card sequence number | C | C+ | C | C+ |
25 | POS condition code | M | -- | M | -- |
28 | Amount, Fee | C | C+ | C | C |
29 | Amount, Fee | C | C | C | C |
32 | Acquiring institution code | M | M+ | M | M+ |
33 | Forwarding institution code | C | C+ | C | C+ |
35 | Track 2 data | C | -- | C | -- |
37 | Retrieval reference number | M | M+ | M | M+ |
38 | Authorization code | -- | M | -- | M |
39 | Response code | -- | M | -- | M |
41 | Card acceptor terminal ID | M | M+ | M | M+ |
42 | Card acceptor ID | M | -- | M | -- |
43 | Card acceptor name / location | M | -- | M | -- |
44 | Additional Response Data | -- | C | -- | -- |
45 | Track 1 data | C | -- | C | -- |
48 | Additional Data 1 | M | -- | M | -- |
49 | Currency code, transaction | M | M+ | M | M+ |
50 | Currency code, settlement | C | C+ | C | C+ |
51 | Currency code, card holder billing | C | C+ | C | C+ |
52 | PIN data | C | -- | C | -- |
55 | Chip data | C | C | C | C |
56 | Customer Related Data | C | C+ | C | C+ |
61 | POS Data | M | -- | M | -- |
102 | Account Identification 1 | O | O | O | O |
120 | Additional Data 2 | C | C+ | C | C+ |
Table 35: e-commerce Payment (Insurance Payment) Message
5.5.26 e-commerce Payment (EMI Payment)
The table below describes e-commerce Payment (EMI Payment) message.
DE Field | Description | 0100/0200 (Acquirer ➔ NCHL) | 0110/0210 (NCHL ➔ Acquirer) | 0100/0200 (NCHL ➔ Issuer) | 0110/0210 (Issuer ➔ NCHL) |
---|---|---|---|---|---|
1 | Secondary bit map | C | C | C | C |
2 | Primary Account Number | M | M+ | M | M+ |
3 | Processing Code | M | M+ | M | M+ |
4 | Amount, Transaction | M | M+ | M | M+ |
5 | Amount, Settlement | C | C+ | C | C+ |
6 | Amount, card holder billing | C | C+ | C | C+ |
7 | Date/time transmission | M | M+ | M | M+ |
9 | Conversion rate, Settlement | C | C+ | C | C+ |
10 | Conversion rate, card holder billing | C | C+ | C | C+ |
11 | System trace audit number | M | M+ | M | M+ |
12 | Time, local transaction | M | M+ | M | M+ |
13 | Date, local transaction | M | M+ | M | M+ |
14 | Date, expiry | C | -- | C | -- |
15 | Date, Settlement | C | C+ | C | C+ |
16 | Date, conversion | C | C+ | C | C+ |
18 | Merchant category code | M | M+ | M | M+ |
19 | Acquiring institution country code | M | M+ | M | M+ |
22 | POS entry mode | M | -- | M | -- |
23 | Card sequence number | C | C+ | C | C+ |
25 | POS condition code | M | -- | M | -- |
28 | Amount, Fee | C | C+ | C | C+ |
29 | Amount, Fee | C | C | C | C |
32 | Acquiring institution code | M | M+ | M | M+ |
33 | Forwarding institution code | C | C+ | C | C+ |
35 | Track 2 data | C | -- | C | -- |
37 | Retrieval reference number | M | M+ | M | M+ |
38 | Authorization code | -- | M | -- | M |
39 | Response code | -- | M | -- | M |
41 | Card acceptor terminal ID | M | M+ | M | M+ |
42 | Card acceptor ID | M | -- | M | -- |
43 | Card acceptor name / location | M | -- | M | -- |
44 | Additional Response Data | -- | C | -- | -- |
45 | Track 1 data | C | -- | C | -- |
48 | Additional Data 1 | M | -- | M | -- |
49 | Currency code, transaction | M | M+ | M | M+ |
50 | Currency code, settlement | C | C+ | C | C+ |
51 | Currency code, card holder billing | C | C+ | C | C+ |
52 | PIN data | C | -- | C | -- |
55 | Chip data | C | C | C | C |
56 | Customer Related Data | C | C+ | C | C+ |
61 | POS Data | M | -- | M | -- |
102 | Account Identification 1 | O | O | O | O |
120 | Additional Data 2 | C | C+ | C | C+ |
Table 36: e-commerce Payment (Insurance Payment) Message
5.5.27 e-commerce Payment (Tax Refund)
The table below describes e-commerce Payment (Tax Refund) message.
DE Field | Description | 0100/0200 (Acquirer ➔ NCHL) | 0110/0210 (NCHL ➔ Acquirer) | 0100/0200 (NCHL ➔ Issuer) | 0110/0210 (Issuer ➔ NCHL) |
---|---|---|---|---|---|
1 | Secondary bit map | C | C | C | C |
2 | Primary Account Number | M | M+ | M | M+ |
3 | Processing Code | M | M+ | M | M+ |
4 | Amount, Transaction | M | M+ | M | M+ |
5 | Amount, Settlement | C | C+ | C | C+ |
6 | Amount, card holder billing | C | C+ | C | C+ |
7 | Date/time transmission | M | M+ | M | M+ |
9 | Conversion rate, Settlement | C | C+ | C | C+ |
10 | Conversion rate, card holder billing | C | C+ | C | C+ |
11 | System trace audit number | M | M+ | M | M+ |
12 | Time, local transaction | M | M+ | M | M+ |
13 | Date, local transaction | M | M+ | M | M+ |
14 | Date, expiry | C | -- | C | -- |
15 | Date, Settlement | C | C+ | C | C+ |
16 | Date, conversion | C | C+ | C | C+ |
18 | Merchant category code | M | M+ | M | M+ |
19 | Acquiring institution country code | M | M+ | M | M+ |
22 | POS entry mode | M | -- | M | -- |
23 | Card sequence number | C | C+ | C | C+ |
25 | POS condition code | M | -- | M | -- |
28 | Amount, Fee | C | C+ | C | C+ |
29 | Amount, Fee | C | C | C | C |
32 | Acquiring institution code | M | M+ | M | M+ |
33 | Forwarding institution code | C | C+ | C | C+ |
35 | Track 2 data | C | -- | C | -- |
37 | Retrieval reference number | M | M+ | M | M+ |
38 | Authorization code | -- | M | -- | M |
39 | Response code | -- | M | -- | M |
41 | Card acceptor terminal ID | M | M+ | M | M+ |
42 | Card acceptor ID | M | -- | M | -- |
43 | Card acceptor name / location | M | -- | M | -- |
44 | Additional Response Data | -- | C | -- | -- |
45 | Track 1 data | C | -- | C | -- |
48 | Additional Data 1 | M | -- | M | -- |
49 | Currency code, transaction | M | M+ | M | M+ |
50 | Currency code, settlement | C | C+ | C | C+ |
51 | Currency code, card holder billing | C | C+ | C | C+ |
52 | PIN data | C | -- | C | -- |
55 | Chip data | C | C | C | C |
56 | Customer Related Data | C | C+ | C | C+ |
61 | POS Data | M | -- | M | -- |
102 | Account Identification 1 | O | O | O | O |
120 | Additional Data 2 | C | C+ | C | C+ |
Table 37: Tax Refund Message
5.5.28 Network Management
5.5.28.1 Network - Echo Message
The table below describes Network echo message.
DE Field | Description | 0800 (Acquirer ➔ NCHL) | 0810 (NCHL ➔ Acquirer) | 0800 (NCHL ➔ Issuer) | 0810 (Issuer ➔ NCHL) |
---|---|---|---|---|---|
1 | Secondary bit map | M | M | M | M |
7 | Date/time transmission | M | M+ | M | M+ |
11 | System trace audit number | M | M+ | M | M+ |
15 | Date, Settlement | C | C+ | C | C+ |
39 | Response code | -- | M | -- | M |
70 | Network management information code | M | M+ | M | M+ |
Table 38: Network - Echo Message
5.5.28.2 Network – Signon/ Logon Message
The table below describes Network Signon/ Logon message.
DE Field | Description | 0800 (Acquirer ➔ NCHL) | 0810 (NCHL ➔ Acquirer) | 0800 (NCHL ➔ Issuer) | 0810 (Issuer ➔ NCHL) |
---|---|---|---|---|---|
1 | Secondary bit map | M | M | M | M |
7 | Date/time transmission | M | M+ | M | M+ |
11 | System trace audit number | M | M+ | M | M+ |
15 | Date, Settlement | C | C+ | C | C+ |
39 | Response code | -- | M | -- | M |
70 | Network management information code | M | M+ | M | M+ |
Table 39: Network – Signon/ Logon Message
5.5.28.3 Network – Signoff/ Logoff Message
The table below describes Network Signoff/ Logoff message.
DE Field | Description | 0800 (Acquirer ➔ NCHL) | 0810 (NCHL ➔ Acquirer) | 0800 (NCHL ➔ Issuer) | 0810 (Issuer ➔ NCHL) |
---|---|---|---|---|---|
1 | Secondary bit map | M | M | M | M |
7 | Date/time transmission | M | M+ | M | M+ |
11 | System trace audit number | M | M+ | M | M+ |
15 | Date, Settlement | C | C+ | C | C+ |
39 | Response code | -- | M | -- | M |
70 | Network management information code | M | M+ | M | M+ |
Table 40: Network – Signoff/ Logoff Message
5.5.28.4 Network – Cutover Message
The table below describes Network Cutover message.
DE Field | Description | 0800 (Acquirer ➔ NCHL) | 0810 (NCHL ➔ Acquirer) | 0800 (NCHL ➔ Issuer) | 0810 (Issuer ➔ NCHL) |
---|---|---|---|---|---|
1 | Secondary bit map | M | M | M | M |
7 | Date/time transmission | M | M+ | M | M+ |
11 | System trace audit number | M | M+ | M | M+ |
15 | Date, Settlement | C | C+ | C | C+ |
39 | Response code | -- | M | -- | M |
70 | Network management information code | M | M+ | M | M+ |
Table 41: Network – Cutover Message
5.5.28.5 Network – Key Exchange Message
The table below describes Network Key Exchange message.
DE Field | Description | 0800 (Acquirer ➔ NCHL) | 0810 (NCHL ➔ Acquirer) | 0800 (NCHL ➔ Issuer) | 0810 (Issuer ➔ NCHL) |
---|---|---|---|---|---|
1 | Secondary bit map | M | M | M | M |
7 | Date/time transmission | M | M+ | M | M+ |
11 | System trace audit number | M | M+ | M | M+ |
15 | Date, Settlement | C | C+ | C | C+ |
39 | Response code | -- | M | -- | M |
48 | Additional data (Key Exchange) | C | -- | C | -- |
70 | Network management information code | M | M+ | M | M+ |
Table 42: Network – Key Exchange Message
5.5.29 STIP Advice Message to Issuer
The table below describes Network Management message.
DE Field | Description | 0120 (NCHL ➔ Issuer) | 0130 (Issuer ➔ NCHL) |
---|---|---|---|
1 | Secondary bit map | C | C |
2 | Primary Account Number | M | M+ |
3 | Processing Code | M | M+ |
4 | Amount, Transaction | M | M+ |
5 | Amount, Settlement | C | C+ |
6 | Amount, card holder billing | C | C+ |
7 | Date/time transmission | M | M+ |
9 | Conversion rate, Settlement | C | C+ |
10 | Conversion rate, card holder billing | C | C+ |
11 | System trace audit number | M | M+ |
12 | Time, local transaction | M | M+ |
13 | Date, local transaction | M | M+ |
14 | Date, expiry | C | -- |
15 | Date, Settlement | C | C+ |
16 | Date, conversion | C | C+ |
18 | Merchant category code | M | M+ |
19 | Acquiring institution country code | M | M+ |
22 | POS entry mode | M | -- |
23 | Card sequence number | C | C+ |
25 | POS condition code | M | -- |
28 | Amount, Fee | C | C+ |
29 | Amount, Fee | C | C |
32 | Acquiring institution code | M | M+ |
33 | Forwarding institution code | C | C+ |
35 | Track 2 data | C | -- |
37 | Retrieval reference number | M | M+ |
38 | Authorization code | -- | M |
39 | Response code | -- | M |
41 | Card acceptor terminal ID | M | M+ |
42 | Card acceptor ID | M | -- |
43 | Card acceptor name / location | M | -- |
48 | Additional Data 1 | M | -- |
49 | Currency code, transaction | M | M+ |
50 | Currency code, settlement | C | C+ |
51 | Currency code, card holder billing | C | C+ |
54 | Additional Amounts | -- | O |
56 | Customer Related Data | C | C+ |
61 | POS Data | M | -- |
102 | Account Identification 1 | O | O |
120 | Additional Data 2 | C | C+ |
121 | Additional Data 3 (Advice Reason Code) | C | C+ |
Table 43: STIP Advice Message
5.5.30 File Update Message
5.5.30.1 Card Add File Update Message
The table below describes File Update message of add card for STIP or VIP purpose.
DE Field | Description | 0302 (Issuer → NCHL) | 0312 (NCHL → Issuer) |
---|---|---|---|
1 | Secondary bit map | C | C |
2 | Primary Account Number | M | M+ |
7 | Date/time transmission | M | M+ |
11 | System trace audit number | M | M+ |
14 | Date, expiry | C | -- |
15 | Date, Settlement | C | C+ |
23 | Card sequence number | C | C+ |
33 | Forwarding Institution Code | C | C+ |
37 | Retrieval Reference Number | M | M+ |
39 | Response code | -- | M |
91 | File Update Code | C | C+ |
124 | File Action Code | -- | C |
125 | File Data Record | C | -- |
Table 44: File Update Message
5.5.30.2 Card Block/ Unblock File Update Message
The table below describes File Update message of Card block and unblock for STIP or VIP purpose.
DE Field | Description | 0302 (Issuer → NCHL) | 0312 (NCHL → Issuer) |
---|---|---|---|
1 | Secondary bit map | C | C |
2 | Primary Account Number | M | M+ |
7 | Date/time transmission | M | M+ |
11 | System trace audit number | M | M+ |
15 | Date, Settlement | C | C+ |
33 | Forwarding Institution Code | C | C+ |
37 | Retrieval Reference Number | M | M+ |
39 | Response code | -- | M |
91 | File Update Code | C | C+ |
124 | File Action Code | -- | C |
125 | File Data Record | C | -- |
Table 45: File Update Message
5.5.30.3 PIN Change File Update Message
The table below describes File Update message of PIN change for STIP or VIP purpose.
DE Field | Description | 0302 (Issuer → NCHL) | 0312 (NCHL → Issuer) |
---|---|---|---|
1 | Secondary bit map | C | C |
2 | Primary Account Number | M | M+ |
7 | Date/time transmission | M | M+ |
11 | System trace audit number | M | M+ |
15 | Date, Settlement | C | C+ |
23 | Card sequence number | C | C+ |
33 | Forwarding Institution Code | C | C+ |
37 | Retrieval Reference Number | M | M+ |
39 | Response code | -- | M |
91 | File Update Code | C | C+ |
124 | File Action Code | -- | C |
125 | File Data Record | C | -- |
Table 46: File Update Message