Table of Contents - APTAStandards.com

More documents

Recommendations

Info

4.8-3 APTA System Header Field Name Description SettlementDate Current settlement date of the system. ReconciliationDate Agency operation date Hostname Host name of the Site Computer that receives transaction from the Picc Device AcquirerId The Unique ID of the Acquirer involved in the transaction. 4.8.3.2 APTA System Common Header This is the common header structu re that immediately follows the System Header in every UD message. UD is defined as “Usage Data” in the context of the ERG specifications. Exhibit 4.8-4 APTA System Common Header Field Name Description formatVersion Format version (ie structure) of the usage data payload. This field is updated every time a new structure definition is released. The formatVersion of this APTA Data Definition is: 0x000001 txnDateTime The time (in seconds) at which the UD record is generated. Format is Unix Time_t (UTC 0) i.e. 0 = 1/1/1970, 00:00:00 UTC. BusinessDate The Business Date on which this UD record was generated sourceParticipantId The Unique ID of the Operator associated with the Picc device on which the UD transaction is generated. DeviceId A unique number assigned to each device SamId The numeric identification of the Security Access Module (SAM) used in the transaction. This field is 0 if no sam was involved. This field should be used to identify the source device of the transaction since it is the SAM that MACs the transaction. A mapping between SamId and deviceId could be maintained by Page 60
Field Name Description reading the SamId and DeviceId data arriving in the header. Udsn UD sequence number. The UDSN will reset back to 0 when it increments past 0xFFFFFFFF. Transac tion Status Indicates if the UD transaction is a normal or test transaction. Test transactions are ignored. UdTyp e Main UD group that defines the type of transaction. UdSubtype Sub UD groups within UD. 4.8.3.3 Variant Data Variant Data consist of a group of selected data structures to form the body of a message. The message type determines the kind and quantity of data structures to exist in a message. For example a “Product Purse Use” Message contains the following data structures from the Exhibit 4.8-2: • SysComHdr_t • SysPiccCom_t • SysApplicationCom_t • DevUdPurseCommonHdr_t • SysFinDetails_t • DevUdPurseLavHdr_t • SysSecurityHdr_t 4.8.4 Message Types As in the TransLink system, ERG specifications break transaction data into types and subtypes to provide the system with a unique level of message identification. Messages fall into one of the following seven main transaction types (UdType), as illustrated in Exhibit 4.8-5. Each transaction group contains further message types (UDSubType) within them. Page 61
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: Data” transaction messages propos
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
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

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?