SB n° 278: Book A B updates re C8

EMV® Specification Bulletin No. 278 First Edition, December 2022 Update of Book A and B Due to Introduction of Book C-8 This Specification Bulletin updates the relevant sections of EMV® Contactless Books A and B to reflect information about the newly introduced specification, EMV Contactless Book C-8

Applicability

This Specification Bulletin applies to: ⚫ EMV Contactless Specifications for Payment Systems, Book A, Architecture and General Requirements, version 2.10, March 2021 ⚫ EMV Contactless Specifications for Payment Systems, Book B, Entry Point Specification, version 2.10, March 2021 Related Documents ⚫ SB No.268: Introduction of New Data Object: Kernel Identifier–Terminal (tag ‘96’), April 2022 Effective Date ⚫ April 2023

Description

With the publication of EMV Contactless Specifications for Payment Systems, Book C-8, several relevant sections in Books A and B also need to be updated. The following section provides a detailed description of the updates. Specification Changes Updates to Book A ✓ In Section 2.1 Volumes of the Contactless Specifications, insert the following after Book C-7: Kernel 7 Specification: Book C-8: Kernel 8 Specification ✓ In Section 5.6.4, replace Table 5-1 with the following: Table 5-1: Example Combination Table per Transaction Type

countries.

Kernel 2 Kernel 3 Kernel 4 Kernel 5 Kernel 6 Kernel 7 Kernel 8 AID1  AID2    … AIDn-1 AIDn         ✓ In Annex A Data Elements for the Data Record and Discretionary Data, replace Table A.1 with the following: Table A.1: Kernel Data Record and Discretionary Data Reference Kernel 2 Kernel 3 Kernel 4 Kernel 5 Kernel 6 Kernel 7 Kernel 8 Chapter 4.6, Lists of Data Objects in OUT Annex B, Online Messages and Clearing Records Annex A, Kernel 4 Data Elements Annex C, Kernel 5 Transaction Record Annex B.9 Annex C, Data Elements Annex A, Data Dictionary Updates to Book B ✓ In Section 2.1 Volumes of the Contactless Specifications, insert the following after Book C-7: Kernel 7 Specification: Book C-8: Kernel 8 Specification ✓ In Section 3.3.1.2, replace Table 3-4 and Table 3-5 with the following: Table 3-4: Format of the Kernel Identifier (tag ‘9F2A’) – Byte 1

countries.

b8 b7 b6 b5 b4 b3 b2 b1 Meaning x x Type of kernel 0 0 0 1 An international kernel, with a Kernel Identifier assigned by EMVCo and coded in the Short Kernel ID RFU 1 0 A domestic kernel, with Kernel Identifier in EMVCo format, coded by the concatenation of the Short Kernel ID and the Extended Kernel ID (see Table 3-5) 1 1 A domestic kernel, with the Kernel Identifier in proprietary format, coded by the concatenation of the Short Kernel ID and the Extended Kernel ID (see Table 3-5) x x x x x x Short Kernel ID The kernel is associated with the 0 0 0 0 0 0 corresponding ADF Name 0 0 0 0 0 1 1st kernel 0 0 0 0 1 0 Kernel 2 0 0 0 0 1 1 Kernel 3 0 0 0 1 0 0 Kernel 4 0 0 0 1 0 1 Kernel 5 0 0 0 1 1 0 Kernel 6 0 0 0 1 1 1 Kernel 7 0 0 1 0 0 0 Kernel 8 0 0 1 0 0 1 9th kernel – – – – – – 1 1 1 1 1 1 63rd kernel Table 3-5: Format of the Kernel Identifier (tag ‘9F2A’) – Byte 2 to Byte 811 11 Kernel Identifier is of variable size and may be one, three, or more bytes in length, but not two bytes.

countries.

Byte Byte 2 Byte 3 Byte 4 Byte 5 Byte 6 Byte 7 Byte 8 Meaning Extended Kernel ID: For international legacy kernel: RFU For domestic legacy kernel using the EMVCo format: Currency Code as defined by [ISO 4217] For domestic legacy kernel using a proprietary format: Proprietary Each bit RFU Each bit RFU Each bit RFU Each bit RFU Each bit RFU ✓ In Section 3.4 Kernel Activation – Start D, replace 3.4.1.4, with the following: 3.4.1.4 ⚫ ⚫ ⚫ ⚫ Entry Point shall set the Kernel Identifier–Terminal (tag '96') as follows: Set Byte 1 to 3 to the value of the Kernel ID from the selected combination. If the Extended Kernel ID is not present in Kernel Identifier (tag '9F2A'), set Byte 2 and 3 = '00 00'. Set Byte 4 bit 8 = 1b when the reader supports Kernel 8. Set Byte 4 bit 7 = 1b when the AID of the selected card application and Kernel 8 are a Combination {AID – Kernel ID} on the reader for the transaction type being conducted. Set Byte 5 to 8 = '00 00 00 00'. Table 3-7: Format of the Kernel Identifier-Terminal (tag ‘96’) Byte Byte 1-3 Byte 4 Byte 5 Byte 6 Byte 7 Byte 8 Meaning Bit assignments are identical to Kernel Identifier Byte 1-3 in Table 3-4 bit 8: 1b = Kernel 8 supported by reader bit 7: 1b = Kernel 8 supported for the transaction bit 6-1: Each bit RFU Each bit RFU Each bit RFU Each bit RFU Each bit RFU ✓ In Annex A, Table A-1, change the entry as below: Name Kernel Identifier– Terminal Description Identifies the kernel used for the transaction Source Format Template Tag Length Entry b - ‘96' 1 or 3-8 Point

countries.

countries.

Legal Notice

The EMV® Specifications are provided “AS IS” without warranties of any kind, and EMVCo neither assumes nor accepts any liability for any errors or omissions contained in these Specifications. EMVCO DISCLAIMS ALL REPRESENTATIONS AND WARRANTIES, EXPRESS OR IMPLIED, INCLUDING WITHOUT LIMITATION IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT, AS TO THESE SPECIFICATIONS. EMVCo makes no representations or warranties with respect to intellectual property rights of any third parties in or in relation to the Specifications. EMVCo undertakes no responsibility to determine whether any implementation of the EMV® Specifications may violate, infringe, or otherwise exercise the patent, copyright, trademark, trade secret, know-how, or other intellectual property rights of third parties, and thus any person who implements any part of the EMV® Specifications should consult an intellectual property attorney before any such implementation. Without limiting the foregoing, the Specifications may provide for the use of public key encryption and other technology, which may be the subject matter of patents in several countries. Any party seeking to implement these Specifications is solely responsible for determining whether its activities require a license to any such technology, including for patents on public key encryption technology. EMVCo shall not be liable under any theory for any party’s infringement of any intellectual property rights in connection with the EMV® Specifications

countries.