EMVTag Series 7-static signature data

EMVTag Series 7-static signature data
? 5F24 application Validity Period

L: 3

-M (required)

1) The application expiration date of the chip is 5F24, and the service code is 5F30. The expiration date must be consistent with the Service Code in Tag57.

2) In qPBOC, the application failure date 5F24 cannot be placed in the last record specified by AFL for the terminal to read.

3) The application expiration date (5F24) cannot be later than the expiration date of the Public Key Certificate of the issuing bank.

Feedback for sending: Standard debit transaction, electronic cash transaction, expiration date of the application returned by the card 5F24 = 491231, expiration date of the Public Key Certificate of the issuing bank = December 2030, the expiration date of the application must be earlier than the expiration date of the Public Key Certificate of the issuing bank.

[Cpp]View plaincopyprint?

1. // The Public Key Index of the authentication center must be 3 or 2 ^ 16 + 1 CA_E = 03
2. // Authentication center Public Key modulo 8F
3. // CA_ I Public Key Certificate of the issuing bank (90)
4. // The terminal restores the issuer's public key CA_O = DeRSA (CA_N, CA_E, CA_ I)
5. CA_O =
6. 6A02 623036FF 12300009870101b001d5c5c2bfe845e14e75681f84173e1e4f9543e7fcca
7. Bytes
8. Bytes
9. Bytes
   
   

   If the 5F24 value is different from the date in section 57, the silver check center will notify you as follows:

   ========================================================== ==================================

   Standard debit transaction, electronic cash transaction, the expiration date of the application returned by the card 5F24 = 491231 the expiration date of the Public Key Certificate of the issuing bank = December 2030 the expiration date of the application should be earlier than the expiration date of the Public Key Certificate of the issuing bank.

   Ask your organization to modify the card.

   ========================================================== ==================================

   ? 9F07 Application Usage Control

   
   

   L: 2

   Byte 1:

   8: 1 = domestic cash transactions are valid

   Bits 7:1 = International cash transactions are valid

   Bits 6= domestic goods valid

   Bits 5:1 = International Goods valid

   Bits = valid domestic services

   Bit: = International Service effective

   Bits: 2: 2 = ATM valid

   Bit: = valid for terminals other than ATM

   Byte 2:

   Bits = allow domestic return

   Bits 7:1 = allow international return

   6-1: RFU (000000)

   JR/T 0025 limit: In byte 1, the bits and 6 values are the same; the bits and 5 values are the same

   Specify the limitations on the card application specified by the issuing bank, including the region usage and service type. Provides more flexible Card Service Control (similar to service code ).

   Bit8	1	Domestic cash transactions are valid
   Bit7	1	International cash transactions are valid
   Bit6	1	Valid domestic goods
   Bit5	1	Valid International Goods
   Bit4	1	Valid services in China
   Bit3	1	Effective international services
   Bit2	1	Valid for ATM
   Bit1	1	Valid for terminals other than ATM
   Bit8	0	Domestic return allowed
   Bit7	0	Allow international return
   Bit6-Bit0	0	RFU

   
   

   Recommended template value: FF 00

   
   

   
   

   ? 5F28 Issuing Bank Country Code
   

   L: 2

   -C (conditional): If application purpose control is available (9F07)

   
   

   
   

   
   

   ? 93 signature static application data

   L: NI

   -C (conditional): If SDA is supported

   The data signature signed by the issuer. Generate with the specified data in the card. Verified by the terminal during the SDA process

   ? 5F25 application Effective Date

   L: 3

   Application activation date in the card

   -O (optional): optional data element.

   ? 9F4A static data authentication tag list

   L: var.

   C

   Lists the tags of basic data objects. The tag values are included in the signed static application data or the IC card Public Key Certificate.

   It can only include tags of application interaction features (AIP)

   ? 9F63 card product identification information (if any)

   L: 16 bytes

   Byte 1-byte 8: Bank ID code

   1

   Byte 9-11: card product identifier

   Byte 9:

   Bits 8: 1 = Citizen Card

   Position 7: 1 = military card

   Bits 6: 1 = accumulate

   Location 5: 1 = traffic card

   Digit 4: 1 = Social Security card

   Digit 3: 1 = student card

   Location 2: 1 = aviation card

   1: 1 = public payment card

   Byte 10: reserved in this specification

   Byte 11: reserved by the issuer

   Bytes 12-14: reserved in this specification

   Bytes 15-16: reserved by the issuer

   NFC mobile phone, mobile phone accessories, Sim card, SD card network test, must write Tag9F63, and the data content and format must comply with the Q/CUP037.2.1-2011 requirements.

   1) For mobile payment IC cards, no matter what account type (01, 02, 03), 9F63 is required and entered in accordance with UnionPay specifications;

   2) for general financial IC cards, 9F63 is optional according to the PBOC specification and serves as the card product information. If this domain is included, enter it according to the PBOC specification. the value of 9F63 in the card printing data generated by DP is placed in 01 application. Therefore, if 9F63 exists in 01 application of personal file, the value must be written to the DGI of the card. This information will take effect at UAT from now on, and will be announced on the effective date of production.

   Example: 9F63 | 16 | 30313034313030300000000000006000 |