Table of Contents - APTAStandards.com

More documents

Recommendations

Info

Exhibit 4.9-5 EquipmentDataGroup DeviceID DeviceTransactionSeq (Optional) CIDID CIDTransactionSeq “PICCDataGroup” contains the data elements that describe the characteristic of the card used in the transaction, Exhibit 4.9-6. Exhibit 4.9-6 PICCDataGroup PICCSerialNumber PICCDataStatusAsRead PICCDataStatusAsWritten PICCKeySetID PICCTransactionSeq PICCTransitApplicationStatus (Optional) PICCPurseSVUse (Optional) The “ EmployeeDataGroup” comprises the data elements displayed in Exhibit 4.9-7, and identifies the employee who is logged on to the device at the time of the transaction. Exhibit 4.9-7 EmployeeDataGroup EmployeeID EmployeeType EmployeePICCID (Optional) The “ActionEventDataGroup” group contains the data elements that are used to document the current state of action event directives as listed in Exhibit 4.9-8 Exhibit 4.9-8 ActionEventDataGroup ActionEventIDAsRead ActionEventIDAsWritten ActionEventMapAsRead ActionEventMapAsWritten Page 70
4.9.4.2 PICC Scheme Control Messages The RIS Part 4 defines a central control body that is responsible for the administration and the governance of the fare collection scheme. The following are the message categories that are issued by the “control body” in order to distribute the implementation specific application parameters: • Action List • Negative List • Fare Policy Framework • Key Management 4.9.4.3 Interface to Transit Benefits Processors The messages in this category are used by Third Party Transit Benefits Administrators to communicate benefit load instructions and action confirmations to the party who manages the action list administration. The Action List Administration facility returns confirmations when the Action List directives are fulfilled. For example, a C101 benefit load request message originating from the Transit Benefits Processor, is responded with a C10 2 Benefit load Confirmation message from the Regional Clearing House or Action List Administrator 4.9.4.4 Interface to Other Clearing houses (RCH-to-RCH) This category of messages are used between clearing houses, when a card from a certain region is used in another region belonging to a different RCH, to notify each other of the activity associated with that card. The messages exchanged are a subset of those defined for a single RCH, and listed in Appendix D. 4.9.4.5 ISO 8583 Interchange message specifications The RIS Part 4 supports the ISO/IEC 8583 messages for all credit/debit card processing related transactions between the RCH and the third party financial transaction acquirers. 4.9.4.6 ACH – Automated Clearing house messages The specification supports the ACH messages as defined by the Electronic Payments Associatio n (NACHA) for message exchanges between the RCH and the third party Automated Clearing Houses (ACH). Page 71
Page 1 and 2:
SMART CARD STANDARDS AND SPECIFICAT
Page 3 and 4:
4.4.7 Security Requirements........
Page 5 and 6:
Document History Revision Reason Fo
Page 7 and 8:
Acronym List UTFS Universal Transit
Page 9 and 10:
technology to achieve interoperabil
Page 11 and 12:
This report encompasse s the review
Page 13 and 14:
Identify S m art Card Indust ry S t
Page 15 and 16:
The standards and specifications th
Page 17 and 18:
These standards and specifications
Page 19 and 20:
Although there is no “one-to-one
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 and 72: standard does not mandate the compl
Page 73: Item Number Exhibit 4.9-2 Part 1 Fi
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 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
show all

Table of Contents - APTAStandards.com

Create successful ePaper yourself

Delete template?

Save as template?