Table of Contents - APTAStandards.com
Table of Contents - APTAStandards.com Table of Contents - APTAStandards.com
Exhibit 4.3-5 Example Transaction Batch 6847102847615489 S F Muni 1265 Sequence=”23643” TimeStamp=”04/23/04 16:23:06” Type=”Credit” 10.00 Sequence=”1021” PurseAfter=”10.75” 6847102847615489 S F Muni 2102 Sequence=”4343” TimeStamp=”04/23/04 16:27:42” 1.50 Sequence=”1022” PurseAfter=”9.25” < BatchControl> Count=”1” Total=”10.00” Count=”1” Total=”1.50” < NetAmount>8.50CR 4.3.4.2 Card Management Data OFX does not specify card management data. 4.3.4.3 System and Device Data OFX does not specify system and device data. 4.3.4.4 Event Data OFX does not specify event data. 4.3.4.5 Peer to Peer Clearing & Settlement OFX does not specify peer-to-peer clearing and settlement data. 4.3.4.5 Additional Messages Offered Not applicable to OFX. 4.3.5 Data Elements Data elements fall into two main categories in OFX, “Elements” and “Aggregates”. An element is data bounded by a leading start tag and a trailing end tag. An OFX element must contain data and may not contain other elements. This is different than the more generic definition of an element in XML. An aggregate is a collection of elements and/or other aggregates. The enrollment request aggregate can be utilized to transmit Page 36
cardholder related data as in the case of Registration and Personalization messages as proposed by WP4. The structure of the ENROLLRQ aggregate is described in Exhibit 4.3-6. Exhibit 4.3-6 ENROLLQ Description Tag Description Enrollment request Aggregate First Name Middle Name Last Name Address Line 1 Address Line 2 Address Line 3 City State or Province Postal Code 3-letter Country Code Daytime Phone Evening Phone E-mail Actual User ID if known ID Used for tax purposes Mother’s maiden name or other Date of birth Service activation request aggregates are utilized to start, modify, or terminate a service for an account by sending service activation requests. These requests can be utilized to represent CID/card parameter and application update messages in UTFS. The description of the activation request aggregate in OFX is illustrated in Exhibit 4.3-7. Exhibit 4.3-7 Activation Request Aggregate (ACCTRQ) Tag Description Account Service Request Aggregate Service Addition Aggregate Service Change Aggregate Service deletion Aggregate Service to be added/changed/deleted Page 37
- 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: - Transaction date and time - Trans
- 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 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
cardholder related data as in the case <strong>of</strong> Registration and Personalization messages as<br />
proposed by WP4. The structure <strong>of</strong> the ENROLLRQ aggregate is described in Exhibit<br />
4.3-6.<br />
Exhibit 4.3-6 ENROLLQ Description<br />
Tag Description<br />
<br />
Enrollment request Aggregate<br />
First Name<br />
Middle Name<br />
Last Name<br />
<br />
Address Line 1<br />
<br />
Address Line 2<br />
<br />
Address Line 3<br />
<br />
City<br />
<br />
State or Province<br />
Postal Code<br />
3-letter Country Code<br />
Daytime Phone<br />
Evening Phone<br />
<br />
E-mail<br />
<br />
Actual User ID if known<br />
<br />
ID Used for tax purposes<br />
<br />
Mother’s maiden name or other<br />
<br />
<br />
Date <strong>of</strong> birth<br />
Service activation request aggregates are utilized to start, modify, or terminate a service<br />
for<br />
an account by sending service activation requests. These requests can be utilized to<br />
represent CID/card parameter and application update messages in UTFS. The<br />
description <strong>of</strong> the activation request aggregate in OFX is illustrated in<br />
Exhibit 4.3-7.<br />
Exhibit 4.3-7 Activation Request Aggregate (ACCTRQ)<br />
Tag Description<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
<br />
Account Service Request Aggregate<br />
Service Addition Aggregate<br />
Service Change Aggregate<br />
Service deletion Aggregate<br />
Service to be added/changed/deleted<br />
Page 37