EMVTag Series 9-card management data,

EMVTag Series 9-card management data,

Ø 5F30 Service Code

F: n 3

T: 5F30

L: 2

-O (optional): Optional Data Element

 

According to the GB/T 17552 standard, the Service Code (5F30) value in the card must be exactly the same as the service code value in binary channel equivalent data 57, if a card has a magnetic stripe and two channels have data, it must be consistent with the service code value in the two channels.

 

 

Ø 8C Card Risk Management Data Object List 1 (CDOL1)

L: var. Up-to-date to 252

-M (required)

 

Lists the data transmitted by the card Request terminal in the 1st generated application ciphertext commands. Supports ciphertext version 01 and authorization control. The content is the terminal data object (TAG and length), data includes: Authorization amount, other amount, terminal country code, terminal verification result, transaction currency code, Transaction date, transaction type, unpredictable number of terminals, transaction time and merchant name.

 

 

Data Object Name	Tag)	Length
Authorization amount	9F02	6
Other Amount	9F03	6
Terminal Country Code	9F1A	2
Terminal Verification Result	95	5
Transaction currency code	5F2A	2
Transaction date	9A	3
Transaction type	9C	1
Unpredictable count	9F37	4
Transaction time	9F21	3
Merchant name	9F4E	20

 

 

 

Recommended template value: 9F02 069F 0306 9F1A 0295 055F 2A02 9A03 9C01 9F3704 9F2103 9F4E14

 

8D Card Risk Management Data Object List 2 (CDOL2)

L: var. Up-to-date to 252

-M (required)

 

Lists the data transmitted by the card Request terminal in the second command to generate the application ciphertext. The content is the terminal data object (TAG and length), including: the response code of the issuing bank, authorization amount, other amount, terminal country code, terminal verification result, transaction currency code, Transaction date, transaction type, unpredictable number of terminals and transaction time.

 

Data Object Name	Tag	Length
Authorization response code	8A	2
Authorization amount	9F02	6
Other Amount	9F03	6
Terminal Country Code	9F1A	2
Terminal Verification Result	95	5
Transaction currency code	5F2A	2
Transaction date	9A	3
Transaction type	9C	1
Unpredictable count	9F37	4
Transaction time	9F21	3

 

 

Recommended template value: 8A02 9F02 069F 0306 9F1A 0295 055F 2A02 9A03 9C01 9F3704 9F2103

Ø 9F08 application version

L: 2

-M (required)

 

The version number assigned by the payment system to the application, which provides a way to transplant new features in the future. The hacker compares the version number of the current user and the card.

 

Recommended template value: PBOC2.0 is 00 20, PBOC3.0 is 00 30

 

Ø 9F49 Dynamic Data Authentication Object List DDOL

L: var. Up to 252

C: If DDA is supported

The data list that the terminal sends to the card in the internal authentication command, including the label and length of the Data Object

 

 

 

Ø serial number of the 5F34 card number

L: 1

Used to indicate different applications using the same account in the card

-O (optional): optional data element.

 

When qPBOC is offline, 5F34 is returned when the GPO response and reading records are not supported. The correct method is that 5F34 returns only when GPO is responding. Ask the card issuer not to use 5F34 as "data for static signature ". From January 1, September 27, 2011, repeated 5F34 cards are no longer allowed to pass the detection.

 

 

 

Ø 9F14 lower limit of continuous offline transactions

L: 1

-C (conditional): If the frequency of the terminal is checked

Maximum number of consecutive offline transactions allowed by the terminal with the connection capability specified by the issuing bank

 

Ø 9F23 continuous offline transaction limit

L: 1

-C (conditional): If the terminal frequency check is supported

The maximum number of consecutive offline transactions allowed before the card is processed online.