Table of Contents - APTAStandards.com
Table of Contents - APTAStandards.com Table of Contents - APTAStandards.com
Exhibit 4.8-5 Transaction Groups Group UdType Description Picc 1 Picc transactions- transactions related to Picc ad justments such as issue, unblock Application 2 Application transactions- transactions related to Application adjustment such as create, delete, block, unblock Product 3 Product transactions- transactions related to fare processing, autoloads, add values, actionlists, product usage Other 4 Other transactions Audit registers 5 Audit registers Events 6 Event records Project Specific Txns 7 Project specific transactions. Use of the UDSubType values must be non-overlapping across projects. The “Audit Registers”, “Events”, “Project Specific Transactions” and the “Other” transactions are deemed optional and beyond the scope of this specification. The messages that fall into these transaction groups depend on the requirements of the specific operator/scheme manager. All messages have a purpose field, which allows transactions of the same purpose to be processed via different paths from transactions of another purpose. They also allow grouping for reporting purposes. Exhibit 4.8-6 provides a list of the purpose codes supported by the specification. 4.8-6 Transaction Purposes Transaction Description Purpose code M Maintenance Transactions F Financial Transactions which affect the Master Database B Blocking Transactions S Miscellaneous Transactions U Non Financial Usage Transactions 4.8.4.1 Transaction Data The Product Transaction Group (UD Type=3) messages, listed in exhibit 4.8-7, are ERG equivalent to the “Farecard Usage Transaction” messages as proposed by the WG4. Each message in every transaction group is assigned a unique sub-type ID based on the fare product used and the entry/exit condition of the journey. Page 62
4.8-7 Product Transactions Usage Messages UdSubType MESSAGE 8 TXN_PRODUCT_PURSE_USE 31 TXN_PRODUCT_PURSE_USE_JOURNEY 32 TXN_PRODUCT_PASS_USE_JOURNEY 33 TXN_PRODUCT_MULTIRIDE_USE_JOURNEY 34 TXN_PRODUCT_PURSE_REBATE_ON_EXIT 35 TXN_PRODUCT_PURSE_USE_ON_ENTRY 41 TXN_PRODUCT_PASS_USE_ON_ENTRY 36 TXN_PRODUCT_MULTIRIDE_USE_ON_ENTRY 37 TXN_PRODUCT_PURSE_USE_ON_EXIT 38 TXN_PRODUCT_PASS_USE_ON_EXIT 39 TXN_PRODUCT_MULTIRIDE_USE_ON_EXIT 40 TXN_PRODUCT_SURCHARGE_REBATE_ON_EXIT The following Product Transaction Group messages, listed on exhibit 4.8-8, are equivalent to the “Add Value Transaction” messages as proposed by the WG4. ERG specifications do not offer any messages that are equivalent of “Financial Audit Data”. Exhibit 4.8-8 Product Transactions Add Value Messages UdSubType Description 1 TXN_PRODUCT_PURSE_ADD 2 TXN_PRODUCT_PASS_ADD 3 TXN_PRODUCT_MULTIRIDE_ADD 9 TXN_PRODUCT_PURSE_ADD_REVERSE 10 TXN_PRODUCT_PASS_ADD_REVERSE 11 TXN_PRODUCT_MULTIRIDE_ADD_REVERSE 4.8.4.2 Card Management Data The “PICC related transactions” group offers fourteen messages that are generated in response to an exception or a specific event occurred on a card. Ten of these messages are listed in Exhibit 4.8-9, and have direct equivalents in the WP4 proposed Card Management Data messages: Page 63
- 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: Field Name Description reading the
- 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 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 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
4.8-7 Product Transactions Usage Messages<br />
UdSubType MESSAGE<br />
8 TXN_PRODUCT_PURSE_USE<br />
31 TXN_PRODUCT_PURSE_USE_JOURNEY<br />
32 TXN_PRODUCT_PASS_USE_JOURNEY<br />
33 TXN_PRODUCT_MULTIRIDE_USE_JOURNEY<br />
34 TXN_PRODUCT_PURSE_REBATE_ON_EXIT<br />
35 TXN_PRODUCT_PURSE_USE_ON_ENTRY<br />
41 TXN_PRODUCT_PASS_USE_ON_ENTRY<br />
36 TXN_PRODUCT_MULTIRIDE_USE_ON_ENTRY<br />
37 TXN_PRODUCT_PURSE_USE_ON_EXIT<br />
38 TXN_PRODUCT_PASS_USE_ON_EXIT<br />
39 TXN_PRODUCT_MULTIRIDE_USE_ON_EXIT<br />
40 TXN_PRODUCT_SURCHARGE_REBATE_ON_EXIT<br />
The following Product Transaction Group messages, listed on exhibit 4.8-8, are<br />
equivalent to the “Add Value Transaction” messages as proposed by the WG4.<br />
ERG specifications do not <strong>of</strong>fer any messages that are equivalent <strong>of</strong> “Financial Audit<br />
Data”.<br />
Exhibit 4.8-8 Product Transactions Add Value Messages<br />
UdSubType Description<br />
1 TXN_PRODUCT_PURSE_ADD<br />
2 TXN_PRODUCT_PASS_ADD<br />
3 TXN_PRODUCT_MULTIRIDE_ADD<br />
9 TXN_PRODUCT_PURSE_ADD_REVERSE<br />
10 TXN_PRODUCT_PASS_ADD_REVERSE<br />
11 TXN_PRODUCT_MULTIRIDE_ADD_REVERSE<br />
4.8.4.2 Card Management Data<br />
The “PICC related transactions” group <strong>of</strong>fers fourteen messages that are generated in<br />
response<br />
to an exception or a specific event occurred on a card. Ten <strong>of</strong> these messages<br />
are listed in Exhibit 4.8-9, and have direct equivalents in the WP4 proposed Card<br />
Management Data messages:<br />
Page 63
Change language