Table of Contents - APTAStandards.com
Table of Contents - APTAStandards.com Table of Contents - APTAStandards.com
it map where each bit represents the presence or absence of a specific RIS Data Object. E ach “1” in the object map indicates the presence of the corresponding object in the message, and each “0” indicates the absence of the object. Any additional object may be adde d to the message simply by marking the Object bit map and placing the objects in the correct sequence in part 3 of the message. There are four extra bits that are reserved for implementer definition in the object bitmap. These extra bits can be utilized to send implementation specific objects or data elements that are not necessarily compliant with RIS Part 3. 4.9.3.4 PART 4 Part 4 contains transaction specific data elements that are unique to the type of the message such as the cardholder personal information in a “PICC Registration” message. 4.9.4 Message Types R IS Part 4 provides the following six main message categories with unique individual messages within the each category. • CID Transaction Messages • PICC Scheme Control Messages • Interface to Transit Benefits Processors • Interface to Other Clearing houses • ISO 8583 Interchange message specifications • ACH – Automated Clearing house messages 4.9.4.1 CID Transaction Messages CID Transaction messages include the following three categories of transactions that are based on the CID to PICC interactions: • PICC Initialization messages include such card activities as initialization, issuance, registration, card inquiry, and limited use card initialization • Load and Unload messages include all direct load and autoload activities performed on the card • Fare payment (Usage) messages document in- and out-of-region card use for all common fare product types available in the US. The Part 1 of the CID Transaction Messages contains twelve data elements as illustrated in Exhibit 4.9-2. Page 68
Item Number Exhibit 4.9-2 Part 1 Fields Data Element Name Exhibit 1.1 MessageIdentifier 1.2 MessageVersion 1.3 MessageRevision 1.4 LocationDataGroup (GRP) 4.8-3 1.5 VehicleDataGroup (GRP) 4.8-4 1.6 EquipmentDataGroup (GRP) 4.8-5 1.7 PICCDataGroup (GRP) 4.8-6 1.8 TransactionDatetime 1.9 EmployeeDataGroup (GRP)* 4.8-7 1.10 PostDateTime 1.11 ApplicationCertCode 1.12 ActionEventDataGroup (GRP) 4.8-8 The location data group describes different characteristics of the location a transaction occurred as listed in Exhibit 4.9-3. Exhibit 4.9-3 LocationDataGroup CountryID RegionID AgencyID LocationID LocationIDDestination (Optional) LocationIDSubArea (Optional) Exhibit 4.9 -4 lists the data elements of the “Vehicle Data Group” which provides the details of the transit vehicle where the transaction took place. Exhibit 4.9-4 VehicleDataGroup VehicleID (Optional) RouteID (Optional) ZoneID (Optional) ZoneIDDestination (Optional) RunID (Optional) Direction-code (Optional) “ Equipment Data Group”, shown in Exhibit 4.9-5, contains the data elements that describe the device that performed the transaction. Page 69
- Page 21 and 22: 4.1.4.2 Card Management Data The st
- Page 23 and 24: with ISO/IEC 7816-6, there is no re
- Page 25 and 26: these messages constitutes a file.
- Page 27 and 28: Phone interviews and/or email corre
- Page 29 and 30: The ITSO message body consists of i
- Page 31 and 32: Exhibit 4.2-2 Product Types Type Co
- Page 33 and 34: Capability Values or RFU Product Pr
- Page 35 and 36: opted to contract these services ou
- Page 37 and 38: e given careful consideration for a
- Page 39 and 40: - Transaction date and time - Trans
- Page 41 and 42: cardholder related data as in the c
- Page 43 and 44: CLIENT Exhibit 4.3-9 OFX Security S
- Page 45 and 46: may well be eliminated if, and when
- Page 47 and 48: Exhibit 4.4-4 Condition Dialogue St
- Page 49 and 50: 4.4.7 Security Requirements The Mes
- Page 51 and 52: Application Retailer Product Retail
- Page 53 and 54: Exhibit 4.6-1 CID Edge Interface Me
- Page 55 and 56: 4.6.8 Timing and Routing The CID Ed
- Page 57 and 58: 4.7.4.1 Transaction Data The “Far
- Page 59 and 60: 4.7.4.3 System and Device Data The
- Page 61 and 62: Following the authentication proces
- Page 63 and 64: Data” transaction messages propos
- Page 65 and 66: Field Name Description reading the
- Page 67 and 68: 4.8-7 Product Transactions Usage Me
- Page 69 and 70: 4.8.4.5 Peer-to-Peer Clearing and S
- Page 71: standard does not mandate the compl
- Page 75 and 76: 4.9.4.2 PICC Scheme Control Message
- Page 77 and 78: • Registration • Negative List
- Page 79 and 80: 5.0 FINDINGS This section presents
- Page 81 and 82: Exhibit 5-2 illustrates the relevan
- Page 83 and 84: Required. This set of specification
- Page 85 and 86: Project/Specification/Standard Spon
- Page 87 and 88: APPENDIX B COMPLETED CRITERIA FORMS
- Page 89 and 90: ISO/IEC 8583 Criteria Transaction D
- Page 91 and 92: TRANSLINK ® Criteria Transaction D
- Page 93 and 94: RIS PART 4 Criteria Transaction Dat
- Page 95 and 96: ITSO DATA ELEMENTS Message Type Dat
- Page 97 and 98: ITSO DATA ELEMENTS Message Type Dat
- Page 99 and 100: ITSO DATA ELEMENTS Message Type Dat
- Page 101 and 102: Amount Net Reconciliation Receiving
- Page 103 and 104: TRANSLINK Message Type Data Element
- Page 105 and 106: Autoload non-purse counter remote l
- Page 107 and 108: card status failure reason Business
- Page 109 and 110: RIS PART 4: FOR A LIST OF DATA OBJE
Item<br />
Number<br />
Exhibit 4.9-2 Part 1 Fields<br />
Data Element Name Exhibit<br />
1.1 MessageIdentifier<br />
1.2 MessageVersion<br />
1.3 MessageRevision<br />
1.4 LocationDataGroup (GRP) 4.8-3<br />
1.5 VehicleDataGroup (GRP) 4.8-4<br />
1.6 EquipmentDataGroup (GRP) 4.8-5<br />
1.7 PICCDataGroup (GRP) 4.8-6<br />
1.8 TransactionDatetime<br />
1.9 EmployeeDataGroup (GRP)* 4.8-7<br />
1.10 PostDateTime<br />
1.11 ApplicationCertCode<br />
1.12 ActionEventDataGroup (GRP) 4.8-8<br />
The location data group describes different characteristics <strong>of</strong> the location a transaction<br />
occurred as listed in Exhibit 4.9-3.<br />
Exhibit 4.9-3<br />
LocationDataGroup<br />
CountryID<br />
RegionID<br />
AgencyID<br />
LocationID<br />
LocationIDDestination (Optional)<br />
LocationIDSubArea (Optional)<br />
Exhibit 4.9 -4 lists the data elements <strong>of</strong> the “Vehicle Data Group”<br />
which provides the<br />
details <strong>of</strong> the transit vehicle where the transaction took place.<br />
Exhibit 4.9-4<br />
VehicleDataGroup<br />
VehicleID (Optional)<br />
RouteID (Optional)<br />
ZoneID (Optional)<br />
ZoneIDDestination (Optional)<br />
RunID (Optional)<br />
Direction-code (Optional)<br />
“ Equipment Data Group”, shown in Exhibit 4.9-5, contains the data elements that<br />
describe<br />
the device that performed the transaction.<br />
Page 69
Change language