SB n°327: Updates to Book B

EMV® Specification Bulletin No. 327 First Edition, May 2026 Updates to EMV® Contactless Book B – Entry Point Specification Applicability This Specification Bulletin applies to: • EMV Contactless Specifications for Payment Systems, Book B, Entry Point Specification version 2.11, June 2023 Related Documents • SB 299, Introduction of a New POI Information Identifier for Transit Operators Effective Date • 1 April 2027 Description This specification bulletin contains clarifications and corrections to Book B. (These are in addition to clarifications and corrections published in SB 299.) Details of Changes This specification bulletin discusses changes to the following topics: A. Table Reference in Book 1 B. Kernel Identifier --- Terminal C. Use of Multiple POI Information IDs D. SPI Command E. Change On-Device CVM to CDCVM Key Yellow highlights existing text with areas of addition or change. Blue highlights existing text to be deleted. Red text indicates final text; that is, text that has been changed or inserted. © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Page 1 EMV® Specification Bulletin No. 327 First Edition A. Table Reference in Book 1 In Section 3.3.3, in the text between Requirement 3.3.3.4 and Requirement 3.3.3.5, correct the table reference as shown: Change: The response to the SELECT (AID) command is structured as defined in [EMV Book 1] Table 45, and is received and processed by Entry Point, including the Status Word SW1 SW2. To: The response to the SELECT (AID) command is structured as defined in [EMV Book 1] Table 10, and is received and processed by Entry Point, including the Status Word SW1 SW2. © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Page 2 EMV® Specification Bulletin No. 327 First Edition B. Kernel Identifier --- Terminal In Section 3.4, Table 3-7, add the clarifying footnotes as shown for Byte 4 as shown below (footnote numbers will be updated when the next version of the specification is published): Change: Byte Meaning Byte 1-3 Bit assignments are identical to Kernel Identifier Byte 1-3 in Table 3-4 and Table 3-5 Byte 4 Byte 5 Byte 6 Byte 7 Byte 8 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 To: 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 and Table 3-5 bit 8: 1b = Kernel 8 supported by reader4 bit 7: 1b = Kernel 8 supported for the transaction5 bit 6-1: Each bit RFU Each bit RFU Each bit RFU Each bit RFU Each bit RFU 4 Set to 1b if the reader is loaded with Kernel 8, regardless of the presence of configuration data. 5 Set to 1b if the reader is configured with the combination of the AID selected and Kernel 8, for the transaction type conducted. © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Page 3 EMV® Specification Bulletin No. 327 C. Use of Multiple POI Information IDs In Annex A.1, Table A-2, add clarification in the description for POI Information ID '0002' as shown: Change: '0002' Transit Operator ID Identifies a particular transit operator. The unique value will be assigned when a transit operator registers with EMVCo. To: '0002' Transit Operator ID Identifies a particular transit operator*. The unique value will be assigned when a transit operator registers with EMVCo. *As a single reader may handle multiple operators, there can be multiple Transit Operator IDs. First Edition b 3 b 3 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Page 4 EMV® Specification Bulletin No. 327 First Edition D. SPI Command In Section C.1.3, make the changes shown below: Change: The data field of the command message is the command template tag ('83') and length, followed by the following data: • If the SDOL is provided by the card, data object values according to the SDOL. DOL coding is as defined in [EMV Book 3] section 5.4 and the construction of the SDOL requested data is performed according to the rules in that section. • If the Terminal Category of the terminal is on the Terminal Categories Supported List (tag '9F3E') returned by the card in the FCI of the SELECT (PPSE) response, then the POI Information ID, length, and value of the following data objects in the POI Information: • (Required) the Terminal Category of the terminal • (Optional) any other POI Information IDs15 Figure C-1 illustrates the SPI command message data field. Double lines indicate the data is always included in the data field and single lines indicate the data is conditionally or optionally included in the data field, as defined above. To: The data field of the command message is the command template tag ('83') and length, followed by the following data: • If the SDOL is provided by the card, data object values according to the SDOL. DOL coding is as defined in [EMV Book 3] section 5.4 and the construction of the SDOL requested data is performed according to the rules in that section. • If the Terminal Category of the terminal is on the Terminal Categories Supported List (tag '9F3E') returned by the card in the FCI of the SELECT (PPSE) response, then the POI Information ID, length, and value of the following data objects in the POI Information: o Terminal Category of the terminal o Any other POI Information IDs15 Additional POI Information (POI Information ID '0002' or greater), if configured on the terminal, shall be provided to the card only when the Terminal Category of the terminal is on the Terminal Categories Supported List provided by the card. If a terminal is not configured with POI Information ID '0001' (Terminal Category), then any additional POI Information configured at the terminal that have POI Information ID greater than '0001' shall only be retrieved by the card by including POI Information (Tag '8B') in SDOL. © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Page 5 EMV® Specification Bulletin No. 327 First Edition Figure C-1 illustrates the SPI command message data field. Double lines indicate the data is always included in the data field and single lines indicate the data is conditionally or optionally included in the data field, as defined above. © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Page 6 EMV® Specification Bulletin No. 327 First Edition E. Change On-Device CVM to CDCVM In Annex B, update as shown below: Change: Restart flag Internal reader flag that indicates whether a kernel is being started for a new transaction or continuing with an ongoing transaction (e.g. in order to complete online processing, to perform on-device CVM, to recover from a communication error, etc.). To: Restart flag Internal reader flag that indicates whether a kernel is being started for a new transaction or continuing with an ongoing transaction (e.g. in order to complete online processing, to perform CDCVM, to recover from a communication error, etc.). © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Page 7 EMV® Specification Bulletin No. 327 First Edition 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 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the user and EMVCo found at www.emvco.com. EMV® is a registered trademark or trademark of EMVCo, LLC in the United States and other countries. Page 8