|
Name |
Description |
| 9F40 |
Additional Terminal Capabilities |
Indicates the data input and output capabilities of the terminal |
| 9F05 |
Application Discretionary Data |
Issuer or payment system specified data relating to the application |
| 61 |
Application Template |
Contains one or more data objects relevant to an application directory entry according to ISO/IEC 7816-5 |
| 8C |
Card Risk Management Data Object List 1 (CDOL1) |
List of data objects (tag and length) to be passed to the ICC in the first GENERATE AC command |
| 8D |
Card Risk Management Data Object List 2 (CDOL2) |
List of data objects (tag and length) to be passed to the ICC in the second GENERATE AC command |
| — |
Card Status Update (CSU) |
Contains data sent to the ICC to indicate whether the issuer approves or declines the transaction, and to initiate actions specified by the issuer. Transmitted to the card in Issuer Authentication Data. |
| 83 |
Command Template |
Identifies the data field of a command message |
| 9F27 |
Cryptogram Information Data |
Indicates the type of cryptogram and the actions to be performed by the terminal |
| 9F45 |
Data Authentication Code |
An issuer assigned value that is retained by the terminal during the verification process of the Signed Static Application Data |
| — |
Default Dynamic Data Authentication Data Object List (DDOL) |
DDOL to be used for constructing the INTERNAL AUTHENTICATE command if the DDOL in the card is not present |
| — |
Default Transaction Certificate Data Object List (TDOL) |
TDOL to be used for generating the TC Hash Value if the TDOL in the card is not present |
| 9F49 |
Dynamic Data Authentication Data Object List (DDOL) |
List of data objects (tag and length) to be passed to the ICC in the INTERNAL AUTHENTICATE command |
| — |
Enciphered Personal Identification Number (PIN) Data |
Transaction PIN enciphered at the PIN pad for online verification or for offline verification if the PIN pad and IFD are not a single integrated device |
| BF0C |
File Control Information (FCI) Issuer Discretionary Data |
Issuer discretionary part of the FCI |
| A5 |
File Control Information (FCI) Proprietary Template |
Identifies the data object proprietary to this specification in the FCI template according to ISO/IEC 7816-4 |
| 9F47 |
Integrated Circuit Card (ICC) Public Key Exponent |
ICC Public Key Exponent used for the verification of the Signed Dynamic Application Data |
| 9F10 |
Issuer Application Data |
Contains proprietary application data for transmission to the issuer in an online transaction |
| 91 |
Issuer Authentication Data |
Data sent to the ICC for online issuer authentication |
| 9F32 |
Issuer Public Key Exponent |
Issuer public key exponent used for theverification of the Signed Static Application Data and the ICC Public Key Certificate |
| 71 |
Issuer Script Template 1 |
Contains proprietary issuer data for transmission to the ICC before the second GENERATE AC command |
| 72 |
Issuer Script Template 2 |
Contains proprietary issuer data for transmission to the ICC after the second GENERATE AC command |
| 5F2D |
Language Preference |
1–4 languages stored in order of preference, each represented by 2 alphabetical characters according to ISO 639
Note: EMVCo strongly recommends that cards be personalised with data element '5F2D' coded in lowercase, but that terminals accept the data element whether it is coded in upper or lower case. |
| 9F4F |
Log Format |
List (in tag and length format) of data objects representing the logged data elements that are passed to the terminal when a transaction log record is read |
| — |
Message Type |
Indicates whether the batch data capture record is a financial record or advice |
| 9F38 |
Processing Options Data Object List (PDOL) |
Contains a list of terminal resident data objects (tags and lengths) needed by the ICC in processing the GET PROCESSING OPTIONS command |
| — |
Proprietary Authentication Data |
Contains issuer data for transmission to the card in the Issuer Authentication Data of an online transaction.
For a cryptogram defined by the Common Core Definitions with a Cryptogram Version of '4', the Proprietary Authentication Data element shall be 0 bytes long. The only Cryptogram Version currently defined for the Common Core Definitions is '4'. |
| 80 |
Response Message Template Format 1 |
Contains the data objects (without tags and lengths) returned by the ICC in response to a command |
| 77 |
Response Message Template Format 2 |
Contains the data objects (with tags and lengths) returned by the ICC in response to a command |
| 88 |
Short File Identifier (SFI) |
Identifies the SFI to be used in the commands related to a given AEF or DDF. The SFI data object is a binary field with the three high order bits set to zero. |
| 9F4B |
Signed Dynamic Application Data |
Digital signature on critical application parameters for DDA or CDA |
| 93 |
Signed Static Application Data |
Digital signature on critical application parameters for SDA |
| 9F4A |
Static Data Authentication Tag List |
List of tags of primitive data objects defined in this specification whose value fields are to be included in the Signed Static or Dynamic Application Data |
| 9F33 |
Terminal Capabilities |
Indicates the card data input, CVM, and security capabilities of the terminal |
| 9F1D |
Terminal Risk Management Data |
Application-specific value used by the card for risk management purposes |
| 9F1F |
Track 1 Discretionary Data |
Discretionary part of track 1 according to ISO/IEC 7813 |
| 9F20 |
Track 2 Discretionary Data |
Discretionary part of track 2 according to ISO/IEC 7813 |
| 57 |
Track 2 Equivalent Data |
Contains the data elements of track 2 according to ISO/IEC 7813, excluding start sentinel, end sentinel, and Longitudinal Redundancy Check (LRC), as follows:
Primary Account Number (n, var. up to 19)
Field Separator (Hex 'D') (b)
Expiration Date (YYMM) (n 4)
Service Code (n 3)
Discretionary Data (defined by individual payment systems) (n, var.)
Pad with one Hex 'F' if needed to ensure whole bytes (b) |
| 97 |
Transaction Certificate Data Object List (TDOL) |
List of data objects (tag and length) to be used by the terminal in generating the TC Hash Value |
| 99 |
Transaction Personal Identification Number (PIN) Data |
Data entered by the cardholder for the purpose of the PIN verification |
