Tomcat
Professional
- Messages
- 2,689
- Reaction score
- 963
- Points
- 113
Migration to microprocessor cards has less impact on the host of the servicing bank than on the host of the issuer. The servicing bank must update the software modules for controlling the devices of the application of its host in order to ensure that the terminal receives the data related to the chip (chip related data), and without meaningful processing of this data send it to the issuing host. The DE 55 composite data element specifically designed for the purposes in question in ISO 8583 messages is used to transfer chip-related data to the issuer host.
Table 6.10 shows the minimum set of chip data transmitted in the authorization request / clearing message from the servicing bank to the issuer. This set of data can be expanded at the discretion of a particular payment system. For example, to the data listed in Table 6.10, the serving bank can optionally add CVM Results, Terminal Capabilities, Terminal Type objects, etc.
Note that the leading payment systems are completing work aimed at making the DE 55 data element mandatory in the
Tab. 6.10. Minimum set of chip data in an authorization request and clearing message
ring messages of the servicing bank. The servicing bank must store the cryptograms of the transactions performed in its devices and present them at the request of the relevant issuers.
During the processing of the transaction, the terminal can transmit to the card at different stages of the operation, various values of the random variable Unpredictable Number. The authorization request must contain the value of this value contained in the data of the first GENERATE AC command. The clearing message must contain the last Unpredictable Number received by the card from the terminal. The servicing bank receives this value from the terminal.
Table 6.11 shows the minimum set of chip data that must be contained in the issuer's response to the authorization request.
Tab. 6.11. The minimum set of chip data in the issuer's response to the authorization request
Table 6.10 shows the minimum set of chip data transmitted in the authorization request / clearing message from the servicing bank to the issuer. This set of data can be expanded at the discretion of a particular payment system. For example, to the data listed in Table 6.10, the serving bank can optionally add CVM Results, Terminal Capabilities, Terminal Type objects, etc.
Note that the leading payment systems are completing work aimed at making the DE 55 data element mandatory in the
Tab. 6.10. Minimum set of chip data in an authorization request and clearing message
| Item number | Name | Tag | Format | Length, bytes |
| 1 | Application Cryptogram (TC / ARQC or AAC) | '9F26' | b | eight |
| 2 | Cryptogram Information Data | '9F27' | b | 1 |
| 3 | Issuer Application Data (IAD) | '9F10' | b | Van up 32 |
| 4 | Unpredictable Number | '9F37' | b | 4 |
| 5 | Application transaction counter (АТС) | '9F36' | b | 2 |
| 6 | Terminal Verification Result | '95' | b | 5 |
| 7 | Transaction Date | '9A' | n | 3 |
| 8 | Transaction Type | '9C | n | 1 |
| 9 | Amount, Authorized | '9F02' | n | 6 |
| 10 | Transaction Currency Code | '5F2A' | n | 2 |
| 11 | Application Interchange Profile | '82' | b | 2 |
| 12 | Terminal country code | '9F1A' | n | 2 |
| 13 | Amount other | '9F03' | n | 6 |
ring messages of the servicing bank. The servicing bank must store the cryptograms of the transactions performed in its devices and present them at the request of the relevant issuers.
During the processing of the transaction, the terminal can transmit to the card at different stages of the operation, various values of the random variable Unpredictable Number. The authorization request must contain the value of this value contained in the data of the first GENERATE AC command. The clearing message must contain the last Unpredictable Number received by the card from the terminal. The servicing bank receives this value from the terminal.
Table 6.11 shows the minimum set of chip data that must be contained in the issuer's response to the authorization request.
Tab. 6.11. The minimum set of chip data in the issuer's response to the authorization request
| Item number | Name | Tag | Format | Length, bytes | Appointment |
| 1 | Issuer Authentication Data | '91' | b | from 8 Up to 16 | Provides the data required by the card to authenticate the issuer |
| 2 | Issuer Script Template 1 Template 2 |
| b | up to 128 | Allows the issuer to send commands to the card |
