Table of Contents - APTAStandards.com

More documents

Recommendations

Info

UdSubType Title Exhibit 4.8-9 Picc Transaction Messages Description 1 TXN_PICC_INITIALISE PICC initialization of reinitialization 2 TXN_PICC_ISSUE Issue of personalized or anonymous card. 3 TXN_PICC_PERSONALISE Personalization of the card. 4 TXN_PICC_PERSONALISE_UP Personalization details are DATE amended. 5 TXN_PICC_BLOCK CID blocks a PICC from usage due to hotlisting or failure to meet other validity processing rules such as expiry. Or as part of the initialization/issuing process. 6 TXN_PICC_UNBLOCK CID unblocks a previously blocked PICC. 7 TXN_PICC_KEYS_UPDATE CID upgrades the security keys on a PICC to a later version. 12 TXN_PICC_ACTIONLIST Actionlist performed on a PICC. 13 TXN_PICC_UNACTIONLIST Un-actionlist a PICC. 14 TXN_PICC_RANGE_ACTIONLI ST_UPDATE A new PICC range actionlist is generated. The “ Application Transactions” group offers messages intended for the creation and management of a transit application on the card. The following are the message types offered by the specification: • Create • Delete • Block • Unblock • Replace The ERG APTA specifications do not provide any messages for CID in the “Card Parameter Update” category. 4.8.4.3 System and Device Data This specification does not define any System and Device Data category messages. 4.8.4.4 Event Data This specification does not define any Event Data category messages. Page 64
4.8.4.5 Peer-to-Peer Clearing and Settlement ERG APTA Specifications have been developed for the regional system settlement approach but some of the messages could be conceivably used for a peer-peer settlement model. 4.8.4.6 Additional Messages Offered The following additional messages are offered by the ERG specifications and intended for card/product activities conducted by customer service personnel. • Product and e-cash refund • Product replacement • Bad Debt settlement • Issuing reversal 4.8.5 Data Elements The ERG APTA specifications cover the data elements supported by the UTFS Workpackage 1 and are listed in Appendix C. The APTA-002 specification provides the type definitions for the data elements used in conjunction with the APTA-001 specification. 4.8.6 Message Sequences The ERG APTA Specifications do not define message sequences. 4.8.7 Security Requirements ERG’s approach to message security is to protect each transaction with a MAC, ensuring that the content and source of the transaction can be validated. This MAC is applied over a subset of the complete message structure. 4.8.8 Timing and Routing The ERG APTA Specification s do not define Timing and Routing requirements. 4.8.9 Usability ERG provided the specification in its entirety for APTA to use within their APTA UTFS WP 4 efforts at no cost. It may be openly reviewed and changed if necessary. However, ERG prefers that it be not used piecemeal. In case APTA prefers to adapt the specification in its entirety and submit changes to it, ERG is willing to offer their internal change process to maintain the central control of the document in return for a fee based on time and materials. Page 65
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: 4.8-7 Product Transactions Usage Me
Page 71 and 72: standard does not mandate the compl
Page 73 and 74: Item Number Exhibit 4.9-2 Part 1 Fi
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 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?