Format: LLLVARb…999
Description: Field 55 is used to transport ICC data. This data element utilises the Tag, Length, Value (TLV) structure to delineate different sub-elements in the following manner:
<LLL><TAG><LENGTH><VALUE><TAG><LENGTH><VALUE> ………
|
Tag |
Length |
PDS Data |
|---|---|---|
|
b ..2 |
b 1 |
b ..127 |
-
LLL: This describes the aggregate length of the data in data element 55.
-
TAG: Contains the tag identifying the EMV data object transported in this PDS (e.g. PDS “9F26” corresponds to the EMV tag “9F26”). The PDS Tag consists of either one or two bytes, represented as hexadecimal. The second byte is provided only if the continuation indicator in the first bye is set. Refer to the EMV 98 Specifications for the structure and definition of the EMV tags and definition of the continuation indicator.
-
LENGTH: Specifies the length (in bytes) of the PDS data, expressed as a binary number in the range 1 to 127.
-
VALUE: Contains the actual data from the corresponding EMV data object, as identified by the PDS Tag.
PDS’s can appear in any order in Field 55.
If DCC is accepted by the cardholder at POS, DCC amount and DCC currency code are used to generate cryptograms. In the case of zero decimal place currencies (e.g. Japanese Yen), follow the example below:
Where Field 6 (Cardholder Billing Amount) = 1000 (10 Yen) use the value 10 to generate the cryptogram.
Note: For Amex processing, the ARC value used in the 2nd Generate AC should be drawn from TAG 91 (IAD) and not TAG 8A (Authorisation Response Code).
| Required Column Legend |
O |
Optional |
|
OR |
Optional Response |
|
|
M |
Mandatory |
|
|
C |
Conditional |
| Format Column Legend |
b..mmm |
String 1 (length) + up to mmm bytes |
|
b m |
String of m bytes |
|
|
b m(n 2m) |
String of m bytes (consisting of 2m BCD digits) |
|
|
b m (an m) |
String of m bytes |
|
EMV PDS Name |
Required |
Values |
Format |
Bytes |
|---|---|---|---|---|
|
Length Attribute |
|
0LLL – BCD length of data to follow. |
n 3 |
2 |
|
TAG 71 |
OR |
Issuer Script Template 1 Scripts from issuer sent to terminal for delivery to ICC. Collective length cannot be greater than 128 bytes. |
n ..8 |
See value |
|
TAG 72 |
OR |
Issuer Script Template 2 Scripts from issuer sent to terminal for delivery to ICC. Collective length cannot be greater than 128 bytes. |
n ..8 |
See value |
|
TAG 82 |
M |
Specifies the application functions that are supported by the card. The terminal attempts to execute only those functions that the ICC supports. |
b 16 |
2 |
|
TAG 84 |
M |
Dedicated File (DF) Name Taken from the application (application-specific data). As described in ISO/IEC 7816-4. |
b VAR |
..16 |
|
TAG 8A |
O |
Authorisation Response Code The ISO 8583 response code received from the network or generated by the terminal. |
n 4 |
2 |
|
TAG 91 |
OR |
Issuer Authentication Data Sent by the issuer if online issuer authentication is required. |
b VAR |
16 |
|
TAG 95 |
M |
Terminal Verification Results Status of the different functions as seen by the terminal during the processing of a transaction. |
b 40 |
5 |
|
TAG 9A |
M |
Transaction Date Taken from terminal clock. |
n 6 |
3 |
|
TAG 9C |
M |
Transaction Type Taken from the transaction data. |
n 2 |
1 |
|
TAG 5F2A |
M |
Transaction Currency Code Taken from the terminal initialisation table or the chip card. |
b 16 |
2 |
|
TAG 9F02 |
M |
Authorization Amount Amount of the transaction as provided by the terminal to the card for cryptogram generation. |
n 12 |
6 |
|
TAG 9F03 |
M for cashback if “9F03” provided by terminal |
Amount, Other Secondary amount associated with the transaction representing a cash back amount. |
n 12 |
6 |
|
TAG 9F09 |
O |
Terminal Application Version Number Taken from the application (application specific data). |
b 16 |
2 |
|
TAG 9F10 |
M if provided by card |
Issuer Application Data Retrieved from the card. |
b VAR |
..32 |
|
TAG 9F1A |
M |
Terminal Country Code Taken from terminal initialisation table or chip card. |
n 3 |
2 |
|
TAG 9F1E |
O |
Interface Device Serial Number Unique and permanent serial number assigned to the interface device by the manufacturer. |
an 8 |
8 |
|
TAG 9F26 |
M |
Application Cryptogram Used to approve offline transactions. |
b 64 |
8 |
|
TAG 9F27 |
M |
Cryptogram Information Data Used to approve offline transactions. |
b 8 |
1 |
|
TAG 9F33 |
M |
Terminal Capabilities Specifies the capabilities of the terminal. |
b 24 |
3 |
|
TAG 9F34 |
M
|
Cardholder Verification Method Results Results of the last cardholder verification method. |
b 18 |
3 |
|
TAG 9F35 |
O |
Terminal Type Specifies the type of terminal. |
n 2 |
1 |
|
TAG 9F36 |
M |
Application Transaction Counter (ATC) Received from the card. |
b 16 |
2 |
|
TAG 9F37 |
M |
Unpredictable Number Value to provide variability and uniqueness to the generation of the application cryptogram. |
b 32 |
4 |
|
TAG 9F41 |
O |
Transaction Sequence Counter Counter maintained by the terminal that is incremented by one for each transaction. |
n..8 |
4 |
|
TAG 9F53 |
O |
Transaction Category Code / Merchant Category Code Usually provided by the acquirer. |
an 1 |
1 |
|
TAG 5F34 |
M if provided by card |
PAN Sequence Number Retrieved from the card. |
n 2 |
1 |
|
TAG 9F6E |
C |
Third Party Data Visa/Diners: Contactless Form Factor Indicator MasterCard: Third Party Data |
n 8 |
4 |
|
TAG 9F7C |
O |
Visa Customer Exclusive Data |
an VAR |
..64 |