Table of Contents - APTAStandards.com

with ISO/IEC 7816-6, there is no requirement for a dataset identifier or dataset bitmap
as these functions are covered by the ISO/IEC 7816-6 TLV coding structures. The result
is that the dataset identifier is replaced by the “T” element, the dataset length object
by
the “L” element, and the sub elements by the “V” element. Data that is not compliant
with the ISO/IEC 7816-6 can still be submitted in this
field as long as it follows the
standard composite data element structure as defined by the standard as illustrated in
Exhibit 4.1-3.
Exhibit 4.1-3 Standard Composite Data Element Structure
Dataset
Identifier
Field 55 ICC Related Data
Dataset
Length
Dataset
Bitmaps
Sub
Element
Exhibit 4.1-4 contains a sample application of the ICC field with the transit industry
related data elements.
Exhibit 4.1-4 Sample Structure of Field 55
Field 55 ICC Data
Name Value Description
Dataset Identifier 71 Fare Transaction
Dataset Length 512 Total length of the sub-elements present
Dataset Bitmap 0110000001100000 Indicates the following fields that are present
Sub-elements
Transit Application Profile Object
Product Index Object
Pass and Transfer Object
Transaction History Object
Dataset Identifier 43 Load Value Transaction
Dataset Length 384 Total length of the sub-elements present
Dataset Bitmap 0001010000100000 Indicates the following fields that are present
Sub-elements
Stored Value (SV) Product Object
Add Value Transaction History Object
Transaction History Object
4.1.6 Message Sequences
The standard provides detailed sequences for message exchange and routing rules.
Typically messages consist of a “request-response” pair that is initiated by either card
issuers or acquirers, as illustrated in Exhibit 4.1-5. There are provisions for message
repetitions when original request message is not responded. Additionally, the standard
Page 19