Format: LLLVARb…999
Description: Field 60 – Reserved Private Data - will be used to send requests and responses related to services not dealt with by other fields. 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> ………
-
LLL: This describes the aggregate length of the data in field 60.
Format: 2 bytes BCD.
-
TAG: This sub-field contains a numeric value describing the data that is to follow in the length and value fields. The tag values and the actual data they represent are outlined in the table below.
Format: 1 bytes BCD.
-
LENGTH: This sub-field contains a numeric value that may vary from 1 to 993 describing the length of the data that is to follow in the value sub-field.
Format: 2 bytes BCD.
-
VALUE: This sub-field contains the data associated with a particular tag. The length of this data should be the same as that indicated in the length sub-field.
Format: see table below for individual tag formats.
Tag
Description
Format
Length
01
Application ID
an 8
8
Tag 01: Application ID (Appl ID)
Indicates that the application used by the POS device has been tested and certified for the market segment indicated. The Device Type and Unique Software Version components drive DCC functionality.
This field is required in all incoming message types with the exception of reconciliation messages and network management messages. It will not appear in any response.
|
Position |
Name |
Description / Available Values |
|||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
1-2 |
Protocol Version Number |
Based on protocol version. Consists of the version number's major digit and second minor digit. Version 2.1 =21. Future increments will proceed as follows:
|
|||||||||||||||||||||||||
|
3-4 |
Unique Software Version |
This value must be agreed with Elavon prior to use. |
|||||||||||||||||||||||||
|
5 |
Device Type |
|
|||||||||||||||||||||||||
|
6 |
Market Segment |
|
|||||||||||||||||||||||||
|
7 |
Capture Type |
|
|||||||||||||||||||||||||
|
8 |
Communication Module (Optional Position) |
|
1.1Field 61: Reserved Private Data II
Format: LLLVARb…999
Field 61 will be used to send requests and responses related to services not dealt with by other fields. This field utilises the Tag, Length, Value (TLV) structure to delineate different sub-elements in the following manner:
<LLL><TAG><LENGTH><VALUE><TAG><LENGTH><VALUE> ………
LLL: This describes the aggregate length of the data in data element 61. Format: 2 bytes BCD.
TAG: This sub-field contains an alphanumeric or numeric value describing the data that is to follow in the length and value fields. The tag values and the actual data they represent are outlined in the table below. Format: 1 byte BCD.
LENGTH: This sub-field contains a numeric value that may vary from 0 to 999 describing the length of the data that is to follow in the value subfield. Format: 2 bytes BCD (first nibble will be zero filled).
VALUE: This sub-field contains the data associated with a particular tag. The length of this data should be the same as that indicated in the length subfield. Format: see table below for individual tag formats.
|
Tag |
Description |
Format |
Length |
|---|---|---|---|
|
01 |
Encrypted Track Data – Cardholder Present |
an48 |
48 |
|
02 |
Encrypted PAN – Cardholder Not Present |
an32 |
32 |
|
03 |
Encrypted Expiry Date – Cardholder Not Present |
an16 |
16 |
|
04 |
Asymmetric Terminal Cryptogram |
b2048 |
256 |
1.1.1Tag 01 Encrypted Track Data – Cardholder Present
Contains Track data for asymmetric encrypted transactions. ASCII Hex format.
1.1.2Tag 02 Encrypted PAN – Cardholder Not Present
Contains PAN data for asymmetric encrypted transactions. ASCII Hex format.
1.1.3Tag 03 Encrypted Expiry Date – Cardholder Not Present
Contains Expiry data for asymmetric encrypted transactions. ASCII Hex format.
1.1.4Tag 04 Asymmetric Terminal Cryptogram
Contains the asymmetric cryptogram.