[ Konec strani | Domov | Nazaj ]
EMV Minimum Data Elements Requirements
Authorisation and Clearing Messages
Europay International, MasterCard International and Visa International (EMV) have agreed upon a minimum set of data elements to be supported in authorisation request and response messages, as well as clearing messages, for ICC transactions. Acquirers are required to have the capability to include all the data elements for a specific message in their transmissions to the Issuer irrespective of whether some of the data elements are provided/requested by the card/Issuer.
The data elements mandated by EMV for the above messages are all currently described in Part III, Section 2, of the EMV '96 version 3.1.1 Integrated Circuit Card Terminal Specification for Payment Systems. The vast majority of the data elements now mandated by EMV, are already marked in the above specification with an asterisk indicating that they are recommended as part of the minimum requirements for ICC transactions. Since EMV have committed to freeze changes to the core EMV '96 version 3.1.1 specifications till 1 July 2000, modifications to the terminal specification to reflect the full set of mandated data elements will only be effected then. In the meantime, this document should be seen as supplementary to the EMV '96 version 3.1.1 specifications.
The following tables summarise the required data elements by message:
Table 1 - Chip Data Elements to be
supported in the Authorisation Request.
Table 2 - Chip Data Elements to be
supported in the Authorisation Response.
Table 3 - Chip Data Elements to be
supported in the Clearing Message.
The payment systems will individually advise their Members in due course as to the date by which they are expected to support the minimum data requirements.
Table 1 - Chip Data Elements in Authorisation Request
| Field# | Name | Tag | Format | Length | Usage |
| 1 | Application Cryptogram (ARQC) | '9F26' | b | 8 | Allows Card Authentication processing |
| 2 | Cryptogram Information Data | '9F27' | b | 1 | Indicates the type of cryptogram returned (approved, online or denied) by the card and the actions to be performed by the terminal (Advice or not, reason for advice) |
| 3 | Issuer Application Data (IAD) | '9F10' | b | Var. up 32 | Provides data elements the Issuer has elected to have in the authorisation message, for example derivation key and algorithm version numbers. Present if provided by ICC in GENERATE AC command response |
| 4 | Unpredictable Number | '9F37' | b | 4 | Provides variability and uniqueness of the ARQC in order to reduce fraud risk. Present if input to application cryptogram calculation |
| 5 | Application transaction counter (ATC) | '9F36' | b | 2 | Indicates sequential order of transaction performed by the application. Provides variability and uniqueness of ARQC in order to reduce fraud risk |
| 6 | Terminal Verification Result | '95' | b | 5 | Informs Issuer of the reason(s) the transaction went online |
| 7 | Transaction Date | '9A' | n | 3 | Indicates the date the transaction was conducted and the authorisation requested |
| 8 | Transaction Type | '9C' | n | 1 | Indicates the transaction type used for application usage control |
| 9 | Amount Authorised | '9F02' | n | 6 | Indicates the amount sent to the Issuer for authorisation |
| 10 | Transaction Currency Code | '5F2A' | n | 2 | Indicates the currency code of the merchant/terminal associated with the transaction |
| 11 | Application Interchange Profile | '82' | b | 2 | Indicates the specified chip application capabilities |
| 12 | Terminal Country Code | '9F1A' | n | 2 | Indicates the country code of the merchant/terminal associated with the transaction |
| 13 | Amount Other | '9F03' | n | 6 | Indicates the cashback amount sent to the Issuer for authorisation. Present if cashback used for current transaction |
It is assumed that Track2 Equivalent Data (PAN, PAN Sequence Number and expiration date) are already present in Authorisation Message.
Table 2 -Chip Data Elements in Authorisation Response
| Field# | Name | Tag | Format | Length | Usage |
| 1 | Issuer Authentication Data | '91' | b | Var 8 to 16 | Provide data to be transmitted to the card for Issuer authentication |
| 2 | Issuer Script
|
'71' '72' |
b | Var up 128 | Allows the Issuer to provide a command for transmission to the card. Present if commands to ICC are sent by issuer. Acquirer network shall support a minimum of 24 Bytes |
Table 3 -Chip Data Elements in Clearing Message
| Field# | Name | Tag | Format | Length | Usage |
| 1 | Application Cryptogram (TC/ARQC or AAC) | '9F26' | b | 8 | Allows authentication of transaction data in support of chargeback processing, for single message terminal ARQC may be used as TC substitute |
| 2 | Cryptogram Information Data | '9F27' | b | 1 | Indicates the type of cryptogram returned (approved, online or denied) by the card and the actions to be performed by the terminal (Advice or not, reason for advice) |
| 3 | Issuer Application Data (IAD) | '9F10' | b | Var. up 32 | Provides data elements the Issuer has elected to have in the authorisation message such as derivation key and algorithm version numbers. Present if provided by ICC in GENERATE AC command response. |
| 4 | Unpredictable Number | '9F37' | b | 4 | Provides variability and uniqueness of the application cryptogram in
order to reduce fraud risk. Present if input to application cryptogram calculation. |
| 5 | Application transaction counter (ATC) | '9F36' | b | 2 | Indicates sequential order of transaction performed by the application. Provides variability and uniqueness of the application cryptogram in order to reduce fraud risk |
| 6 | Terminal Verification Result | '95' | b | 5 | Informs Issuer of the results of transaction processing performed by the terminal and may be used for dispute management |
| 7 | Transaction Date | '9A' | n | 3 | Indicates the date the transaction was conducted |
| 8 | Transaction Type | '9C' | n | 1 | Indicates the type of transaction conducted by the cardholder |
| 9 | Amount Authorised | '9F02' | n | 6 | Indicates the amount authorised for the transaction and used to generate the application cryptogram). This amount may be different from the transaction amount |
| 10 | Transaction Currency Code | '5F2A' | n | 2 | Indicates the currency code associated with the transaction |
| 11 | Application Interchange Profile | '82' | b | 2 | Indicates the specified chip application capabilities |
| 12 | Terminal Country Code | '9F1A' | n | 2 | Indicates the country code of the merchant/terminal associated with the transaction. Provides liability protection |
| 13 | Amount Other | '9F03' | n | 6 | Indicates the cashback amount sent to the Issuer for authorisation. Present if cashback used for current transaction |
It is assumed that Track2 Equivalent Data (PAN, PAN Sequence Number and expiration date) are already present in Clearing Message.
[ Začetek strani | Domov | Nazaj ]