Table of Contents - APTAStandards.com
Table of Contents - APTAStandards.com Table of Contents - APTAStandards.com
• Create/amend ITSO ID • Deleting an ITSO Shell The Creating ITSO Shell message would be the equivalent of an initialization message, while Activating ITSO Shell is the equivalent of an issuing transaction. The Create/Amend ITSO ID message is designed to transmit cardholder specific data (see Appendix C) and would represent both the Registration and Personalization messages of UTFS. The Interoperability List Transaction is intended to exchange operating parameters between the host and the CID. Even though the specification allows the definition of implementation specific parameter types, the following list contains the currently set-up parameter tables: • Card Type Parameters • Peak Times • Public Holidays • Transfers • Rebates • Loyalty Rules • Currency • Zone Table Reference • Zone Table Bitmap • Sale Price • Format Version Code parameters • Change Instructions 4.2.4.3 System and Device Data HOPS to POST Configuration messages are designed to update or change the main devic e and application related parameters between a central system and a CID as illustrated in Exhibit 4.2-4. Exhibit 4.2-4 HOPS to POST Configuration Messages Capability Values Location 0=Not Used 1=Fixed 2= mobile or RFU Security 0= Not Used 1=Not tamper proof, 2=Tamper Proof, 3= Tamper proof and no radiation Communication 0= Not Used 1= Offline, 2=permanently online 3= dial out capability, 4=dial in/polled capability Page 28
Capability Values or RFU Product Priority Selection Prioritization according to a table Message Security 0=Not Used 1=Messages Saved after Transmission 2= Messages Not Saved after Transmission RFU Printing Capability 0=Not Used 1=Receipt Printer Available RFU Cardholder Display 0=Not Used 1=Display Facing Cardholder RFU Maximum Purse Value 0=Not Used 1=Cannot Modify 2=Can modify IPE Priority Selection 0=Not Used 1=Prioritization According to parameter table 2= Prioritization According to customer stated preference RFU The device level commands are intended for very high-level device configuration settings and not for low-level device hardware status data, or parameter update. 4.2.4.4 Event Data ITSO does not define any device level message types. 4.2.4.5 Peer to Peer Clearing & Settlement Since the clearing and reimbursement arrangements may vary dramatically between schemes, ITSO does not define financial settlement between entities. Settlement is beyond the scope of this specification. 4.2.5 Data Elements The specification provides a wide variety of data elements that represent most product types and entities offered in Europe and North America. ITSO includes 34 fixed length standard data elements (fields) that are present in every message, and supplemented with transaction specific data based on the message type. The fields that are not utilized by a particular implementation should be “0” filled and presented in messages where required. This may create messages with lengths up to 100 bytes per message. Page 29
- 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: Exhibit 4.2-2 Product Types Type Co
- 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 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
Capability Values<br />
or RFU<br />
Product Priority Selection Prioritization according to a table<br />
Message Security 0=Not Used<br />
1=Messages Saved after<br />
Transmission<br />
2= Messages Not Saved after<br />
Transmission<br />
RFU<br />
Printing Capability 0=Not Used<br />
1=Receipt Printer Available<br />
RFU<br />
Cardholder Display 0=Not Used<br />
1=Display Facing Cardholder<br />
RFU<br />
Maximum Purse Value 0=Not Used<br />
1=Cannot Modify<br />
2=Can modify<br />
IPE Priority Selection 0=Not Used<br />
1=Prioritization According to<br />
parameter table<br />
2= Prioritization According to<br />
customer stated preference<br />
RFU<br />
The device level <strong>com</strong>mands are intended for very high-level device configuration<br />
settings and not for low-level device hardware status data, or parameter update.<br />
4.2.4.4 Event Data<br />
ITSO<br />
does not define any device level message types.<br />
4.2.4.5 Peer to Peer Clearing & Settlement<br />
Since<br />
the clearing and reimbursement arrangements may vary dramatically between<br />
schemes, ITSO does not define financial settlement between entities. Settlement is<br />
beyond the scope <strong>of</strong> this specification.<br />
4.2.5 Data Elements<br />
The specification provides a wide variety <strong>of</strong> data elements that represent most product<br />
types and entities <strong>of</strong>fered in Europe and North America. ITSO includes 34 fixed length<br />
standard data elements (fields) that are present in every message, and supplemented<br />
with transaction specific data based on the message type. The fields that are not utilized<br />
by a particular implementation should be “0” filled and presented in messages where<br />
required. This may create messages with lengths up to 100 bytes per message.<br />
Page 29
Change language