Table of Contents - APTAStandards.com
Table of Contents - APTAStandards.com Table of Contents - APTAStandards.com
Dataset Identifier 4.1.4 Message Types Exhibit 4.1-2 Composite Data Element Dataset Length The standard provides the following general message classes, some of which can be applied to back end transaction types for public transit as defined by UTFS WP4. • Authorization Messages • Verification Messages • Financial Presentment Messages • Financial Accumulation Presentment • File action messages • Reversal Message Class • Chargeback message class • Reconciliation message class • Administrative message class • Error messages • Fee collection messages • Network Management messages • Key management messages The following sections addresses the relevance and application of the messages to the message types defined by the UTFS WP4 in the Interface Specification Functional Description. 4.1.4.1 Transaction Data Composite Data Element Dataset Sub Optional TLV Bitmap(s) Element Sub Elements The MTI 240, Financial Presentment Notification Messages have been designed to communicate the financial data for an approved transaction amount for billing or posting purposes. This message type can be applied to Fare Card Usage and Add Value Transaction types defined by UTFS. The message has 37 optional and mandatory data elements. (See Appendix C for a full list of data elements in this message) In addition to its standard financial transaction message types, this standard allocates further sub-classification for an electronic purse transaction type within the financial presentment message class. Page 16
4.1.4.2 Card Management Data The standard provides MTI 800 series network management message class to control the following types of network management activity: • System condition management, which is used to establish and report system availability and to give instructions pertaining to message handling during periods of system unavailability • System security management, which is used to control security aspects of the interchange system such as key and password management and security alerts. These messages may be used as part of a security procedure, e.g., automatic periodic key changes • System accounting management, which is used to identify the end of a reconciliation period. These messages may be used as part of a reconciliation process • System audit controls management, which is used to test integrity of interchange links and/or used as a part of an integrity check or failure recovery scheme • Batch and file transfer header and trailer control management, which is used to denote the start and/or end of batch or file transfer File Action Instruction/Notification Messages (362/340) can be utilized to inform the receiver of a file action to be completed. The sender can periodically specify that the receiver acknowledge the receipt of the most recently sent group of instruction messages. The Da ta Record data element present in these message classes is utilized for the actual transfer of data and may or may not be based on the message types identified in this standard. Data Record data element is variable length and its structure and the content can be specified by the parties involved in the exchange. This allows parties in the transmission to further define the requirements of the Data Record data element, allowing the File Action Instruction/Notification messages to be utilized for Card Management transactions as proposed by the WP4. The types of file actions that are defined by the standard are listed below: • Add record • Change record • Delete record • Replace record • Inquiry • Replace file • Add file • Delete File • Card administration • Reserved for private use Page 17
- 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: Although there is no “one-to-one
- 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
Dataset<br />
Identifier<br />
4.1.4<br />
Message Types<br />
Exhibit 4.1-2 Composite Data Element<br />
Dataset<br />
Length<br />
The standard provides the following general message classes, some <strong>of</strong> which can<br />
be<br />
applied<br />
to back end transaction types for public transit as defined by UTFS WP4.<br />
• Authorization Messages<br />
• Verification Messages<br />
• Financial Presentment Messages<br />
• Financial Accumulation Presentment<br />
• File action messages<br />
• Reversal Message Class<br />
• Chargeback message class<br />
• Reconciliation message class<br />
• Administrative message class<br />
• Error messages<br />
• Fee collection messages<br />
• Network Management messages<br />
• Key management messages<br />
The following sections addresses the relevance and application <strong>of</strong> the messages to the<br />
message types defined by the UTFS WP4 in<br />
the Interface Specification Functional<br />
Description.<br />
4.1.4.1 Transaction<br />
Data<br />
Composite Data Element<br />
Dataset Sub Optional TLV<br />
Bitmap(s)<br />
Element Sub Elements<br />
The MTI 240, Financial Presentment Notification Messages have been designed to<br />
<strong>com</strong>municate the financial data for an approved transaction amount for billing or<br />
posting purposes. This<br />
message type can be applied to Fare Card Usage and Add Value<br />
Transaction types defined by UTFS. The message has 37 optional and mandatory data<br />
elements. (See Appendix C for a full list <strong>of</strong> data elements in this message)<br />
In addition to its standard financial transaction message types, this standard allocates<br />
further<br />
sub-classification for an electronic purse transaction type within the financial<br />
presentment message class.<br />
Page 16
Change language