Book C-6 Kernel Specification

© 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. EMV ® Contactless Specifications for Payment Systems Book C-6 Kernel 6 Specification Version 2.12 June 2026 EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page ii / 151 © 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. Legal Notice Unless the user has an applicable separate agreement with EMVCo or with the applicable payment system, any and all uses of these Specifications is subject to the terms and conditions of the EMVCo Terms of Use agreement available at www.emvco.com and the following supplemental terms and conditions. The license granted in the EMVCo Terms of Use specifically excludes (a) the right to disclose, distribute or publicly display these Specifications or otherwise make these Specifications available to any third party, and (b) the right to make, use, sell, offer for sale, or import any software or hardware that practices, in whole or in part, these Specifications. Further, EMVCo does not grant any right to use the Kernel Specifications to develop contactless payment applications designed for use on a Card (or components of such applications). As used in these supplemental terms and conditions, the term “Card” means a proximity integrated circuit card or other device containing an integrated circuit chip designed to facilitate contactless payment transactions. Additionally, a Card may include a contact interface and/or magnetic stripe used to facilitate payment transactions. To use the Specifications to develop contactless payment applications designed for use on a Card (or components of such applications), please contact the applicable payment system. To use the Specifications to develop or manufacture products, or in any other manner not provided in the EMVCo Terms of Use, please contact EMVCo. These 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 these 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 these 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 these Specifications. EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page iii / 151 © 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. Revision Log – Version 2.12 The following changes have been made to the document since the publication of Version 2.11. Some of the numbering and cross references in this version have been updated to reflect changes introduced by the published bulletins. The numbering of existing requirements did not change, unless explicitly stated otherwise. Incorporated changes described in the following Specification Updates: 1. Section 2.2 updated to clarify the handling of optional card data elements. 2. Figure 3-6 updated to add step 2a to clear the Tearing Log. Other editorial changes: 1. Figure 3-6 updated to correct typos in steps 4 and 6. EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page iv / 151 © 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. Contents Legal Notice ............................................................................................................ ii Revision Log – Version 2.12 .................................................................................. iii Contents ................................................................................................................. iv Figures .................................................................................................................... ix Tables ...................................................................................................................... x 1 Introduction ..................................................................................................... 11 1.1 Scope ....................................................................................................... 11 1.2 Audience .................................................................................................. 11 1.3 Volumes of Contactless Specifications ..................................................... 11 1.4 Reference Specifications .......................................................................... 12 1.5 Overview .................................................................................................. 13 1.6 Data Conventions ..................................................................................... 14 1.7 Terminology.............................................................................................. 14 2 Overview of Kernel 6 Approach ..................................................................... 15 2.1 Configuration ............................................................................................ 15 2.1.1 EMV Transactions (Offline, Online or Deferred Authorization Transactions) ..................................................................................................... 15 2.2 EMV Transaction Processing Flows ......................................................... 16 2.3 Configuration, Functionality, and APDU Command Support ..................... 21 2.3.1 POS System Configuration Options .............................................. 21 2.3.2 Functionality .................................................................................. 21 2.3.3 APDU Command Support ............................................................. 23 2.4 Deferred Authorization .............................................................................. 23 2.5 Data Storage ............................................................................................ 24 2.5.1 General Features .......................................................................... 24 2.5.2 Data Structure Overview ............................................................... 25 2.5.3 Data Containers ............................................................................ 26 2.5.4 Operator Container Update Codes ................................................ 27 2.5.5 Container Identifiers ...................................................................... 28 2.6 Extended Logging .................................................................................... 28 2.7 Tearing Recovery ..................................................................................... 28 2.7.1 Process Overview ......................................................................... 28 EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page v / 151 © 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. 3 Terminal Transaction Processing Steps ....................................................... 30 3.1 Combination Selection Post Processing ................................................... 30 3.2 Read Data Storage ................................................................................... 45 3.3 Initiate Application Processing .................................................................. 48 3.4 Read Application Data .............................................................................. 59 3.5 Tearing Analysis ....................................................................................... 62 3.6 Offline Data Authentication (ODA) for Offline Transactions ....................... 63 3.6.1 Signed Dynamic Application Data ................................................. 66 3.6.2 Card Feature Descriptor Verification ............................................. 67 3.7 Cardholder Verification ............................................................................. 67 3.8 Processing Restrictions ............................................................................ 73 3.9 Terminal Action Analysis .......................................................................... 76 3.10 Online Processing .................................................................................... 82 3.11 Completion ............................................................................................... 83 3.11.1 Post Completion ........................................................................... 83 3.12 Issuer Update Processing......................................................................... 85 3.13 Write Data Storage ................................................................................... 88 4 Application Protocol Data Unit (APDU) Command Description ................... 92 4.1 Summary .................................................................................................. 92 4.2 Select ....................................................................................................... 94 4.3 Get Processing Options ............................................................................ 94 4.3.1 Command Format ......................................................................... 94 4.3.2 Data Field Returned in the Response Message ............................ 95 4.4 Data Get Processing Options ................................................................... 98 4.4.1 Command Format ......................................................................... 98 4.4.2 Data Field Returned in the Response Message ............................ 99 4.5 Resume Get Processing Options .............................................................. 99 4.5.1 Command Format ....................................................................... 100 4.5.2 Data Field Returned in the Response Message .......................... 101 4.6 Read Record .......................................................................................... 101 4.7 Get Data ................................................................................................. 101 4.8 Put Data ................................................................................................. 102 4.8.1 Command Format ....................................................................... 102 4.8.2 Data Field Returned in the Response Message .......................... 102 4.9 Update Record ....................................................................................... 103 EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page vi / 151 © 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. 4.9.1 Command Format ....................................................................... 103 4.9.2 Data Field Returned in the Response Message .......................... 103 4.10 Application Block .................................................................................... 103 4.11 Application Unblock ................................................................................ 104 Annex A Glossary .................................................................................... 105 Annex B Kernel 6 Transaction Outcome and Parameter Settings ........ 111 B.2. Approved ................................................................................................ 111 B.3. Online Request ....................................................................................... 112 B.4. Online Request (Approved + Restart B) ................................................. 113 B.5. Online Request (Declined + Restart B) ................................................... 114 B.6. Declined ................................................................................................. 115 B.7. Try Another Interface .............................................................................. 116 B.8. End Application ...................................................................................... 116 B.9. End Application (for Processing Error) .................................................... 117 B.10. Try Again (Entry of a Confirmation Code) ............................................... 118 B.11. Try Again (for Tearing Recovery) ............................................................ 119 B.12. Select Next ............................................................................................. 120 B.13. Data Record Outcome Parameter .......................................................... 120 B.14. Discretionary Data Outcome Parameter ................................................. 121 Annex C Terminal Configuration: Data Elements .................................. 123 C.1. Offline Only Terminals ............................................................................ 123 C.2. Online Only Terminals ............................................................................ 124 C.3. Offline / Online Terminals ....................................................................... 125 Annex D Data Elements Dictionary ......................................................... 127 D.1. Application Selection Flag (ASF, tag ‘DF62’) .......................................... 127 D.2. Application Selection Registered Proprietary Data (tag ‘9F0A’) .............. 127 D.3. Card ID (tag ‘DF 3E’) .............................................................................. 128 D.4. Card Feature Descriptor (tag ‘DF3B’) ..................................................... 128 D.5. Card Feature Version Number (tag ‘DF3A’) ............................................ 128 D.6. Card Processing Requirements (tag ‘9F71’) ........................................... 129 D.7. Cryptogram Information Data (CID, tag ‘9F27’) ....................................... 130 D.8. Cryptogram Version Number (CVN) ....................................................... 130 D.9. Contactless Card Verification Results (tag ‘9F53’) .................................. 130 D.10. Data Container Read List ....................................................................... 133 EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page vii / 151 © 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. D.11. Data Storage Directory (tag ‘DF3D’) ....................................................... 133 D.12. Data Storage Directory Hash .................................................................. 135 D.13. Data Storage Directory Unpredictable Number ....................................... 135 D.14. Data Storage Enabled ............................................................................ 135 D.15. Data Storage Supported ......................................................................... 135 D.16. Data Storage Write Results .................................................................... 136 D.17. Data Storage Update Template (tag ‘BF10’) ........................................... 136 D.18. Data Store (tag ‘DF3F’) .......................................................................... 136 D.19. Deferred Authorization Supported .......................................................... 137 D.20. Extended Logging Data (tag ‘DF3C’) ...................................................... 137 D.21. Extended Logging Enabled ..................................................................... 138 D.22. Extended Logging Supported ................................................................. 138 D.23. Extended Selection Support Flag ........................................................... 138 D.24. Form Factor Identifier (tag ‘9F6E’) .......................................................... 138 D.25. Offline Balance (tag ‘D1’) ........................................................................ 138 D.26. Merchant Category Code (MCC, tag ‘9F15’) ........................................... 138 D.27. Merchant Name and Location (tag ‘9F4E’) ............................................. 138 D.28. Payment Account Reference (PAR, tag ‘9F24’) ...................................... 139 D.29. Program Identifier (PID, tag ‘DF70’) ........................................................ 139 D.30. Reader Contactless CVM Limit ............................................................... 139 D.31. Reader Contactless Floor Limit .............................................................. 139 D.32. Reader Contactless Transaction Limit .................................................... 139 D.33. Resume Transaction .............................................................................. 139 D.34. Tearing Recovery Enabled ..................................................................... 140 D.35. Tearing Recovery Supported .................................................................. 140 D.36. Tearing Log ............................................................................................ 140 D.37. Terminal Transaction Qualifier (TTQ, tag ‘9F66’) .................................... 140 D.38. Terminal Verification Result (TVR, tag ‘95’) ............................................ 142 D.39. Transaction Certificate (TC) .................................................................... 144 D.40. Transaction Status Information (TSI, tag ‘9B’) ........................................ 144 D.41. Write Data Storage Template (tag ‘BF11’) .............................................. 145 D.42. Zero Amount Allowed Flag ..................................................................... 146 D.43. Zero Amount Allowed Offline Flag .......................................................... 146 Annex E Data Storage Security ............................................................... 148 E.1. Operator Container Update Codes ......................................................... 148 EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page viii / 151 © 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. E.2. Data Container Integrity .......................................................................... 149 EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page ix / 151 © 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. Figures Figure 2-1: Kernel 6 Contactless EMV Transaction Flow ................................................... 18 Figure 2-2: Kernel 6 Contactless EMV Transaction Flow with Data Storage ...................... 19 Figure 2-3: Kernel 6 Contactless EMV Transaction Flow with Tearing Recovery ............... 20 Figure 2-4: Logical Data Storage Data Structure ................................................................ 26 Figure 3-1: EMV Application Selection – Processing Flow (Format Analysis) ..................... 31 Figure 3-2: EMV Application Selection – Processing Flow (PDOL Mandatory Check) ........ 33 Figure 3-3: EMV Application Selection – Processing Flow (PDOL Optional Check) ........... 35 Figure 3-4: EMV Application Selection – Processing Flow (Optional Checks) .................... 37 Figure 3-5: EMV Application Selection – Processing Flow (Optional Feature Checks) ....... 40 Figure 3-6: EMV Application Selection – Processing Flow (Tearing Recovery Check) ....... 43 Figure 3-7: Read Data Storage – Processing Flow ............................................................ 45 Figure 3-8: Initiate Application Processing – Processing Flow ............................................ 49 Figure 3-9: Initiate Application Processing (Mandatory Data Checks: All Transactions) ..... 52 Figure 3-10: Initiate Application Processing (Checks for Online and Decline Decision – No CDA) ............................................................................................................... 55 Figure 3-11: Initiate Application Processing (Checks for CDA) ........................................... 58 Figure 3-12: Read Application Data Process ...................................................................... 60 Figure 3-13: Tearing Analysis ............................................................................................ 62 Figure 3-14: Offline Data Authentication (Global Overview) ............................................... 64 Figure 3-15: Cardholder Verification Method Process (Online PIN, Signature, and No CVM) ........................................................................................................................ 68 Figure 3-16: Cardholder Verification Method Process: Consumer Device CVM (CD CVM) 71 Figure 3-17: Processing Restriction Process ...................................................................... 74 Figure 3-18: Terminal Action Analysis Process .................................................................. 77 Figure 3-19: Terminal Action Analysis Process (Validate Choice) ...................................... 81 Figure 3-20 - Post Completion Processing ......................................................................... 84 Figure 3-21: Issuer Update Process ................................................................................... 87 Figure 3-22: Write Data Storage Process ........................................................................... 89 Figure 4-1: DATA GET PROCESSING OPTIONS – Command Data Format ..................... 99 Figure 4-2: DATA GET PROCESSING OPTIONS – Data Store Data Object Encoding ..... 99 Figure 4-3: Data Storage Directory ................................................................................... 134 Figure 4-4: Data Store Data Object Encoding .................................................................. 137 Figure 4-5: Preparing Data Container MAC ...................................................................... 150 Figure 4-6: Checking Data Container MAC ...................................................................... 151 EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page x / 151 © 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. Tables Table 1-1: References ......................................................................................................12 Table 1-2: Data Conventions ............................................................................................14 Table 1-3: Terminology ....................................................................................................14 Table 2-1: Contactless Functionality ................................................................................21 Table 2-2: APDU Command Support ...............................................................................23 Table 2-3: Data Container Properties ...............................................................................27 Table 4-1: List of APDU Commands Used by This Kernel ................................................92 Table 4-2: GET PROCESSING OPTIONS Command Format ..........................................94 Table 4-3: GET PROCESSING OPTIONS Response Data Objects .................................95 Table 4-4: GET PROCESSING OPTIONS Response Data Field for Contactless EMV Transactions ..................................................................................................95 Table 4-5: DATA GET PROCESSING OPTIONS Command Format ...............................98 Table 4-6: DATA GET PROCESSING OPTIONS Data Storage Write Commit Control ....98 Table 4-7: RESUME GET PROCESSING OPTIONS Command Format ........................ 100 Table 4-8: RESUME GET PROCESSING OPTIONS Parameter P1 Settings ................. 100 Table 4-9: READ RECORD Response Message Data Field for Data Containers ........... 101 Table 4-10: PUT DATA Command Format ..................................................................... 102 Table 4-11: UPDATE RECORD Command Format ........................................................ 103 Table 4-12: Reference Control Parameter ...................................................................... 103 Table 4-13: Minimum Data Elements Returned in Transaction Data Record Outcome Parameter.................................................................................................... 120 Table 4-14: Discretionary Data Outcome Parameter ...................................................... 121 Table 4-15: Offline Only Terminals ................................................................................. 123 Table 4-16: Online Only Terminals ................................................................................. 124 Table 4-17: Online and Offline Terminals ....................................................................... 125 Table 4-18: Card Feature Descriptor Encoding .............................................................. 128 Table 4-19: Card Processing Requirement (CPR) Encoding .......................................... 129 Table 4-20: Cryptogram Information Data (CID) Encoding ............................................. 130 Table 4-21: Contactless Card Verification Results (CL CVR) Encoding ......................... 131 Table 4-22: Directory Entry Encoding ............................................................................. 134 Table 4-23: Data Storage Write Results Encoding ......................................................... 136 Table 4-24: Minimum Data Items Recorded in Tearing Log............................................ 140 Table 4-25: Terminal Transaction Qualifiers (TTQ) Encoding ......................................... 141 Table 4-26: Terminal Verification Result (TVR) Encoding .............................................. 142 Table 4-27: Transaction Status Information (Byte 1) ...................................................... 144 Table 4-28: Transaction Status Information (Byte 2) ...................................................... 145 Table 4-29: Write Data Storage Template ...................................................................... 145 EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page 11 / 151 © 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. 1 Introduction This EMV Contactless Specifications for Payment Systems, Book C-6, Kernel 6 Specification (this Specification) addresses the requirements applicable to Kernel 6, including the: • Overview of Kernel 6 Approach • Terminal Transaction Processing Steps and • Application Protocol Data Unit (APDU) Command Description Baseline functionalities are addressed in [EMV Book B], which should be read as a companion document and is hereby incorporated into this specification by reference. These baseline functionalities include, but are not limited to: • Preliminary Transaction Processing (i.e., Pre-Processing) • Protocol Activation • Combination Selection • Kernel Activation • Outcome Processing and • Data Element Processing 1.1 Scope This Specification describes one of several Kernels defined for use with Entry Point. 1.2 Audience This Specification is intended for use by system designers in payment systems and financial institution staff responsible for implementing financial applications. Note: Throughout this Specification, Contactless Cards and Consumer Devices (such as mobiles) are referenced as Contactless Cards unless Contactless and Consumer Devices must be addressed separately. 1.3 Volumes of Contactless Specifications This Specification is part of an EMVCo eleven-volume set, including: • Book A: Architecture and General Requirements [EMV Book A] • Book B: Entry Point Specification [EMV Book B] • Book C-2: Kernel 2 Specification • Book C-3: Kernel 3 Specification • Book C-4: Kernel 4 Specification • Book C-5: Kernel 5 Specification • Book C-6: Kernel 6 Specification • Book C-7: Kernel 7 Specification • Book C-8: Kernel 8 Specification EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page 12 / 151 © 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. • Book E: Security and Key Management • Level 1 Specifications for Payment Systems, EMV Contactless Interface Specification 1.4 Reference Specifications In addition to the volumes cited in Section 1.3, the following specifications and standards contain provisions that are referenced in this Specification. The latest version shall apply unless a publication date is explicitly stated. If any provision or definition in this Specification differs from those in the listed specifications and standards, the provision or definition herein shall take precedence. Table 1-1: References Abbreviation Title [EMV Book 1] EMV Integrated Circuit Card Specifications for Payment Systems. Book 1 - Application Independent ICC to Terminal Interface Requirements. [EMV Book 2] EMV Integrated Circuit Card Specifications for Payment Systems. Book 2 - Security and Key Management. [EMV Book 3] EMV Integrated Circuit Card Specifications for Payment Systems. Book 3 - Application Specification. [EMV Book 4] EMV Integrated Circuit Card Specifications for Payment Systems. Book 4 - Cardholder, Attendant, and Acquirer Interface Requirements. [EMV Book A] EMV Contactless Specifications for Payment Systems: Book A Architecture and General Requirements [EMV Book B] EMV Contactless Specifications for Payment Systems: Book B Entry Point Specification [ISO/IEC 639-1] Codes for the representation of names of languages – Part 1: Alpha- 2 Code. [ISO/IEC 3166-1] Codes for the representation of names of countries and their subdivisions Part 1 Country Codes. [ISO/IEC 4217] Codes for the representation of currencies and funds. [ISO/IEC 7810] Information technology – Identification cards – Physical characteristics. [ISO/IEC 7813] Information technology – Identification cards – Financial transaction cards. [ISO/IEC 7816-4] Information technology – Identification cards – Integrated circuit cards – Part 4: Organization, security and commands for interchange. [ISO/IEC 7816-5] Identification cards – Integrated circuit cards – Part 5: Registration of application providers. EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page 13 / 151 © 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. Abbreviation Title [ISO/IEC 8583-1] Financial transaction card originated messages – Interchange message specifications – Part 1: Messages, data elements and code values. [ISO/IEC 8825-1] Information technology – ASN.1 encoding rules: Specification of Basic Encoding Rules (BER), Canonical Encoding Rules (CER) and Distinguished Encoding Rules (DER). [ISO/IEC 8859-1] Information Technology – 8-bit single-byte coded graphic character sets – Part 1: Latin alphabet No. 1. [ISO/IEC 9797-1] Information technology – Security techniques - Message Authentication Codes (MACs) – Part 1: Mechanisms using a block cipher. [ISO/IEC 10116] Information technology – Security techniques - modes of operation for an n-bit block cipher. [ISO/IEC 13239] Information technology – Telecommunications and information exchange between systems – High-level data link control (HDLC) procedures. [ISO/IEC 14443-1] Identification cards – Contactless integrated circuit cards – Proximity cards – Part 1: Physical characteristics. [ISO/IEC 14443-2] Identification cards – Contactless integrated circuit cards – Proximity cards – Part 2: Radio frequency power and signal interface. [ISO/IEC 14443-3] Identification cards – Contactless integrated circuit cards – Proximity cards – Part 3: Initialization and anti-collision. [ISO/IEC 14443-4] Identification cards – Contactless integrated circuit cards – Proximity cards – Part 4: Transmission protocol. 1.5 Overview This document includes the following chapters and annexes: • Chapter 1: contains general information regarding this Specification. • Chapter 2: provides a high-level description of the Kernel 6 approach, including configuration, transaction processing flows, terminal and configuration requirements and options, and supported APDU commands. • Chapter 3: specifies detailed transaction processing flows for Kernel 6. • Chapter 4: lists and describes the APDU commands used by Kernel 6. • Annex A: is a glossary of terms and abbreviations used in this specification. • Annex B: contains Kernel 6 Transaction Parameters and Outcomes. • Annex C: lists data elements required for offline only, online only, and offline / online transactions. • Annex D: is a dictionary of data elements for Kernel 6. • Annex E: specifies the Track 2 Equivalent Data. EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page 14 / 151 © 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. • Annex F: provides guidance for Data Storage security. 1.6 Data Conventions The data conventions included in Table 1-2 are used throughout this Specification. Table 1-2: Data Conventions Convention Description ‘…’ Single quotation marks surround a decimal or hexadecimal digit. For example: ‘3A’ or ‘9901’ […] Squared brackets surround a reference document. For example: [EMV Book A]. A Alphanumeric b Binary n Numeric Var Variable length For data elements that have multiple bytes, the first byte or byte 1 is the left-most byte, while the last byte is the right-most byte. 1.7 Terminology The terminology used in this specification is presented in Table 1-3. Table 1-3: Terminology Term Definition Shall, must, or required Denotes a mandatory requirement Should Denotes a recommendation May or optional Denotes an optional feature EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page 15 / 151 © 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. 2 Overview of Kernel 6 Approach A high-level description of the Kernel 6 approach is provided in the following sections: • 2.1: Configuration • 2.2: Transaction Processing Flows • 2.3: Configuration, Functionality, and APDU Command Support • 2.4: Deferred Authorization • 2.5: Data Storage • 2.6: Extended Logging • 2.7: Tearing Recovery 2.1 Configuration The Kernel 6 approach supports only EMV transactions, and it allows the processing of transactions offline or online (based on Terminal capabilities). Access to configurations supporting EMV transactions are enabled by a designated Application Identifier (AID) of ‘A0000001523010’. 2.1.1 EMV Transactions (Offline, Online or Deferred Authorization Transactions) EMV transactions conform to the EMV requirements supporting offline and online capabilities including the functionalities and commands for: • Selecting the application, initializing transaction processing, and reading records to obtain the application data items • Performing Cardholder Verification and Offline Data Authentication (ODA) for offline transactions • Enabling Processing Restrictions, Terminal Action Analysis, Online Processing, and Issuer Update Processing for online transactions, and • Supporting security parameters, including an optimized cryptographic process that enables the generation of an Application Cryptogram (AC) or Combined Dynamic Data Authentication / Application Cryptogram Generation (CDA) using the Unpredictable Number (UN) provided by the reader in the Processing Data Objects List (PDOL). Kernel 6 may optionally be configured to support Deferred Authorization for EMV transactions in environments where real time online authorization is not possible. Kernel 6 supports optional capabilities for Data Storage, Extended Logging and Tearing Recovery, where supported by the card. Unlike contact EMV-based transactions, the reader performs certain checks before the card enters the Radio Frequency (RF) field as specified in [EMV Book B] and after the card has left the RF field. Additional information regarding EMV transaction processing is provided in Section 1 of this Specification. EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page 16 / 151 © 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. 2.2 EMV Transaction Processing Flows The Kernel will initiate the EMV transaction when EMV is supported by the card and the transaction passes the required PDOL checks. Terminal entry point shall perform the pre-processing prior to the activation of the contactless interface of the reader and before the cardholder is invited to present a Contactless Card. Combination Selection shall be processed after card presentment. Because the interaction (i.e., the command-response) between the card and the Terminal can only occur when the card is in the RF field, the process requires adaptations to permit the: • Reduction of the number of commands and adjustment of the transaction flow for both the first and second presentment processes • Definition of data elements taking into account events relevant for contactless transactions • Usage of Entry Point as defined for [EMV Book B], to select the application and activate the corresponding Contactless Kernel 6 • Optional identification of and recovery for torn contactless transactions • Optional retrieval of data items from on-card Data Storage before transaction initiation • Optional writing of data items to on-card Data Storage or Extended Logging during transaction initiation • Generation of a CDA Cryptogram or an Application Cryptogram during the transaction initiation • Execution of Terminal Risk Management before the card is placed in the field and after the card is removed from the field, and • If required, execution of cardholder verification after the card is removed from the field. Issuers may allow a Contactless Card to be presented a second time (via a second presentment) for updating application data or Data Storage. The need for a second presentment is determined by the contactless reader by checking for the presence of Issuer scripts included in the authorization request response and / or Data Storage data prepared by the Terminal. The reader shall store the fields that are required for a second presentment in transient memory as specified in [EMV Book B]. Entry Point uses this transient memory to select the Combination used in the previous Final Combination Selection to deliver the Issuer Update Processing commands and / or Data Storage updates. The EMV configuration uses the Outcome parameters defined in Annex B and provides data for online messages and clearing records. Note: If any of the following optional data object is received from a Contactless Card with an incorrect length or format then the reader shall discard that data object and treat it as if it was not present and continue with the transaction. • Application Expiration Date, Tag: 5F24 • Application Preferred Name, Tag: 9F12 • Application Primary Account Number (PAN), Tag: 5A • Application Selection Flag, Tag: DF62 • Application Selection Registered Proprietary Data (ASRPD), Tag: 9F0A EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page 17 / 151 © 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. • Form Factor Identifier (FFI), Tag: 9F6E • Issuer Code Table Index, Tag: 9F11 • Issuer Identification Number (IIN), Tag: 42 • Issuer Identification Number Extended (IINE), Tag: 9F0C • Language Preference, Tag: 5F2D • Log Entry, Tag: 9F4D • Payment Account Reference (PAR), Tag: 9F24 The EMV transaction flow is illustrated in Figure 2-1. The EMV Mode transaction flow with optional Data Storage is illustrated in Figure 2-2, and with optional Tearing Recovery in Figure 2-3. EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page 18 / 151 © 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. Figure 2-1: Kernel 6 Contactless EMV Transaction Flow READER Protocol Activation Combination Selection Initiate Application Processing Read Application Data List of Supported Applications Transaction-Specific Application Data* Terminal File Records Cardholder Verification Processing Restrictions Terminal Action Analysis CARD SELECT PPSE SELECT AID GET PROCESSING OPTIONS READ RECORD Card in RF Field Command/ Response Optional Process Mandatory Process Pre-Processing Processing Online Completion Entry Point Selection START B Issuer Update Processing Selected Application Processing Updates/ Scripts SELECT AID Issuer Script Try Another interface Terminate Second presentment (second tap) Offline Data Authenticaiton Offline Completion Entry Point Process First presentment (first tap) *Transaction-Specific Application Data are provided in Table 4-4. EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page 19 / 151 © 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. Figure 2-2: Kernel 6 Contactless EMV Transaction Flow with Data Storage READER Protocol Activation Combination Selection Initiate Application Processing Read Application Data List of Supported Applications Transaction-specific and Data Container data Terminal File Records Cardholder Verification Processing Restrictions Terminal Action Analysis CARD SELECT PPSE SELECT AID (DATA) GET PROCESSING OPTIONS READ RECORD Card in RF Field Command/ Response Optional Process Mandatory Process Pre-Processing Processing Online Completion Entry Point Selection START B Issuer Update Processing Selected Application Processing Updates/ Scripts SELECT AID Issuer Script Try Another interface Terminate Second presentment (second tap) Offline Data Authenticaiton Offline Completion Entry Point Process Operator Processing* Read Data Storage Data Storage Process Data Container data Write Data StoragePUT DATA Data Storage Directory and Data Container data GET DATA READ RECORD Operator Processing* First presentment (first tap) *Operator-specific business logic (terminal functionality). EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page 20 / 151 © 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. Figure 2-3: Kernel 6 Contactless EMV Transaction Flow with Tearing Recovery Entry Point Selection START B Initiate Application Processing Read Application Data Selected Application Transaction-Specific Application Data Terminal File Records Cardholder Verification Processing Restrictions Terminal Action Analysis SELECT AID RESUME GET PROCESSING OPTIONS READ RECORD Card in RF Field Command/ Response Optional Process Mandatory Process Processing Online Completion Entry Point Selection START B Issuer Update Processing Selected Application Processing Updates/ Scripts SELECT AID Issuer Script Try Another interface Terminate Second presentment (third tap) Offline Data Authenticaiton Offline Completion Entry Point Process READER Protocol Activation Combination Selection Initiate Application Processing Read Application Data List of Supported Applications Transaction-Specific Application Data Terminal File Records CARD SELECT PPSE SELECT AID GET PROCESSING OPTIONS READ RECORD Pre-Processing Tearing Detected Terminate First presentment (first tap) Resume first presentment (second tap) Tearing Recovery Supported? Yes No Note: Tearing Recovery is also supported for EMV transactions using Data Storage. EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page 21 / 151 © 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. 2.3 Configuration, Functionality, and APDU Command Support Section Summary: • 2.3.1: POS System Configuration Options • 2.3.2: Functionality • 2.3.3: APDU Command Support 2.3.1 POS System Configuration Options The POS System Configuration options are used by the Kernel and must be set as described in [EMV Book A] and [EMV Book B]. In addition, the following configuration options are specific to Kernel 6. 1. Acceptance Environment: Reader will be enabled to support the EMV transactions 2. Kernel AID: Discover AIDs will be configured to be used with Kernel 6. 2.3.2 Functionality Specific Contactless functionalities are included in Table 2-1 and classified based on the following definitions: • Mandatory: This functionality must be present and must conform to the behavior described in this Specification • Conditional: The presence of the functionality is dependent on another function • Optional: This functionality must be present in the Terminal application but the Acquirer may choose not to use the function. Table 2-1: Contactless Functionality Function Kernel 6 Terminal Support Notes Entry Point Processing based on [EMV Book B] Mandatory The Terminal shall support Entry Point processing as defined in [EMV Book B] Combination Selection Post Processing Mandatory See Section 3.1: Combination Selection Post Processing Tearing Recovery Mandatory Read Data Storage Mandatory Operator Processing Mandatory Invocation of proprietary business logic for Data Storage or Extended Logging. Initiate Application Processing Mandatory If a data requested by the PDOL is not present in the Terminal, then the Terminal shall set the value to zeroes. EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page 22 / 151 © 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. Function Kernel 6 Terminal Support Notes Cardholder Verification Method (CVM) • Online PIN • Signature • Consumer Device CVM • No CVM Conditional Mandatory for EMV transactions except as determined by the payment system. Read Application Data • EMV Data in Terminal File records, identified by Short File Identifier (SFI) and record number Conditional Mandatory for Offline capable EMV readers Offline Data Authentication (ODA) • CDA Conditional Mandatory for Offline capable readers and Data Storage (must be performed before Termination Action Analysis) Processing Restrictions • Application Expiration Date • Application Effective Date • Application Version Number • Application Usage Control* • Exception List Mandatory *Conditional – Mandatory for offline transactions Terminal Action Analysis Mandatory Online Processing Conditional Mandatory for Online capable EMV readers Completion • Offline • Online Mandatory Issuer Update Processing • Application Block • Application Unblock • Put Data • Update Record Conditional Mandatory for Online capable EMV readers Write Data Storage Mandatory EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page 23 / 151 © 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. 2.3.3 APDU Command Support The APDU commands included in Table 2-2 are designated as “Mandatory”, “Conditional”, or “Not supported” by the Contactless Kernel 6 Terminal based on the following definitions: • Mandatory: The command must be supported. • Conditional: The command shall be supported if the corresponding functionality is enabled • Not supported: The command is not supported. Table 2-2: APDU Command Support Command Kernel 6 Support APPLICATION BLOCK Mandatory 1 APPLICATION UNBLOCK Mandatory 1 CARD BLOCK Not supported DATA GET PROCESSING OPTIONS Conditional 2 EXTERNAL AUTHENTICATE Not Supported GENERATE APPLICATION CRYPTOGRAM (AC) Not Supported GET CHALLENGE Not Supported GET DATA Mandatory GET PROCESSING OPTIONS Mandatory INTERNAL AUTHENTICATE Not Supported PIN CHANGE / UNBLOCK Not Supported PUT DATA Mandatory 1 READ RECORD Mandatory RESUME GET PROCESSING OPTIONS Conditional 3 SELECT Mandatory UPDATE RECORD Mandatory 1 Notes: 1. Terminal to only pass supported Issuer Script commands to card. 2. Mandatory if Data Storage is supported. 3. Mandatory if Tearing Recovery is supported. 2.4 Deferred Authorization Deferred Authorization enables POS Systems to be used in environments where real time online authorization is not possible. EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page 24 / 151 © 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. With Deferred Authorization, when an EMV transaction requires online authorization (and after successful Offline Data Authentication) the Kernel will provide an Approved Outcome. The POS System or back-office may then request authorization at a later time. Notes: • Even though real time online authorization is not used, Terminals shall request online cryptograms from cards (by setting TTQ B2b8 = ‘1’). Consequently, Terminals must be configured as online capable, with TTQ B1b4 = ‘0’ (Online capable contactless reader) and a Terminal Type (tag ‘9F35’) of “Online only” or “Offline with online capabilities” • Online PIN cardholder verification is not supported. Readers must be configured with TTQ B1b3 = ‘0’ (Online PIN not supported) • The reader must be configured to support Offline Data Authentication, with TTQ B1b1 = ‘1’ (ODA for online authorization supported), and • Issuer Update Processing is not supported, the reader must be configured with TTQ B3b8 = ‘0’ (Issuer update processing not supported). 2.5 Data Storage Data Storage provides transit operators, merchants, and other business entities (referred to generically as operators herein) with the ability to read and write custom merchant data on cards during EMV contactless transactions. Data Storage is an optional feature for card and terminal applications, and may be used as part of an EMV transaction when supported by both. 2.5.1 General Features Data Storage has the following features: • Use of on-card Data Containers, in which operators can store their own data. Three types of Data Container are supported: o Transient Containers – freely readable and writable by any operator o Operator Containers – freely readable and with write access for the allocated operator only, and o Issuer Containers – freely readable with issuer-only write access. • Use of Container IDs to uniquely identify and address individual Data Containers • Use of an on-card Data Storage Directory that records the allocation of Data Containers on the card. The Data Storage Directory is a dynamic data object (comprising a sequence of Directory Entries, one for each allocated Data Container) that can be read by operators using the GET DATA command • Mapping of Data Containers to card file records, allowing the retrieval of their contents by operators using the READ RECORD command • Use of Data Exchange by Kernel to invoke operator-specific* processing in the Terminal prior to Initiate Application Processing • Use of the DATA GET PROCESSING OPTIONS command (which extends the GET PROCESSING OPTIONS command) to update Data Container content during Initiate Application Processing EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page 25 / 151 © 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. • Optional use of the PUT DATA command by operators and issuers to update Data Container content during card second presentment • The capability for issuers to allocate Operator Containers to operators, either during card personalization or via issuer scripting • Use of Offline Data Authentication, container Write Counters and Integrity Codes for operators to authenticate cards and to guard against skimming or replay of container content. * The use of operator-specific logic is proprietary and is outside the scope of this specification. 2.5.2 Data Structure Overview Figure 2-4 shows the logical data structure used by the card for data storage. Summary data storage information is passed from card application to terminal as part of the application selection response. This information includes the version number, the number and location of records in the data store, and the card application’s unique identity. The Kernel can retrieve public Data Storage Directory information from the card using the GET DATA command. This comprises a sequence of Directory Entries, one for each allocated Data Container. A container’s Directory Entry identifies its Container ID, the record holding its content and other attributes. The Kernel can read a Data Container’s content using the READ RECORD command. EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page 26 / 151 © 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. Figure 2-4: Logical Data Storage Data Structure Private Card Directory Data Card Feature Descriptor (tag ‘DF3B’) Version Number Card Feature Version Number (tag ‘DF3A’) Data Storage Data Directory (tag ‘DF3D’) – read using GET DATA Data Storage info passed in SELECT FCI response References Container ID Record Number Container Type Write Counter Integrity Code Directory Entry 1Directory Entry 2 Directory Entry n Update Code Timestamp Update Code Timestamp Update Code Timestamp Directory Entry 1Directory Entry 2 Directory Entry n Contents (0-160 bytes) Data Container 1 Contents (0-160 bytes) Data Container 2 Contents (0-160 bytes) Data Container n References Container ID Record Number Container Type Write Counter Integrity Code Container ID Record Number Container Type Write Counter Integrity Code SFI of Data Store Number of Data Containers in Data Store Card ID References DATA GET PROCESING OPTIONS Data Containers – read using READ RECORD, update using PUT DATA or 2.5.3 Data Containers A Data Container is a logical unit of data storage, addressable by its Container ID. A Data Container must be allocated on a card before an operator can use it to store data. During allocation a mapping is created on the card between the Container ID and the file record that stores the container’s content. There are three types of Data Container, all are freely readable but each have differing write- access and allocation approaches, as shown in Table 2-3. EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page 27 / 151 © 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. Table 2-3: Data Container Properties Property Data Container Type Transient Container Operator Container Issuer Container Allocation By card application By issuer By issuer Read-access Any operator Any operator Any operator Write-access Any operator and the issuer Allocated operator (using Update Codes) and the issuer only Issuer only Transient Containers are allocated as needed by the card application during a transaction at an operator’s terminal. The card will persist the contents of Transient Containers between transactions and until overwritten, either by the same operator, a different operator, or the issuer. When allocating Transient Containers, the card application will select either an unallocated Transient Container (if one is free), or the oldest of its allocated Transient Containers (overwriting its current Container ID and content). Operator Containers are allocated by the issuer, either during card personalization or via issuer scripting. An Operator Container may only be updated by the operator to which it is allocated or the issuer. Operator write-access is enforced using Update Codes; the card will update container content only when the correct Update Code is used by the operator (see below). Issuer Containers are allocated by the issuer, either during card personalization or via issuer scripting. Issuer Containers may only be updated by the issuer (via secure messaging). Card applications implementing data storage must be personalized with a minimum of three Transient Containers. 2.5.4 Operator Container Update Codes The card holds a hidden Update Code for each Operator Container, and will only allow an update to an Operator Container if the terminal can prove that it knows the same Update Code. This works as follows: • To update an Operator Container, the operator computes a hash over the data to be updated, data provided by the card application, and its copy of the Update Code. This hash value is called the Update Code Hash. The computed Update Code Hash is sent to the card application as part of the update request • The card application computes a hash over the same data items, but uses its copy of the Update Code • The card application then compares its computed Update Code Hash with the given Update Code Hash. If they do not match, then the update request will be rejected, otherwise the card will: o Write the new content into the container’s file record o Update the container’s Write Counter, Integrity Code and Timestamp. Operators may also replace the stored Update Code with a new value as part of the update, if required. The operator is free to use any suitable strategy for managing its Update Codes (see Annex E for guidance). Initial Update Code values must be agreed between operators and issuers. EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page 28 / 151 © 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. 2.5.5 Container Identifiers Each allocated Data Container is uniquely identified on a card by its Container ID. Only one Data Container may be allocated per Container ID per card. An operator may be assigned one or more Container IDs by the Data Storage Registration Authority. Any operator requiring simultaneous use of multiple Data Containers will require multiple Container IDs, one for each Data Container needed. The Container ID of zero (‘00000000’) is reserved and is used by card and terminal to indicate an unallocated Data Container. The Data Storage Registration Authority can assign shared Container IDs between operators. This allows groups of two or more operators to share the same Data Container. For example, a group of co-operating transit operators may each be assigned a unique Container ID for their own individual use, plus a shared Container ID for use as a group. The card and terminal make no explicit distinction between unique and shared Container IDs. 2.6 Extended Logging Extended Logging provides merchants with a simple mechanism for recording custom data in a card’s transaction log during EMV contactless transactions. If Extended Logging is enabled, the Kernel will use Data Exchange to invoke operator-specific* processing in the Terminal prior to performing Initiate Application Processing. The Terminal response may provide an Extended Logging Data (tag ‘DF3C’) data element. This data element can contain up to 32 bytes of custom data and, if provided, is appended to the GET PROCESSING OPTIONS command data. The card will include the data in its own transaction log. The card’s cyclic transaction log can be read later at a special terminal using the READ RECORD command. Support for Extended Logging is optional for card and Kernel, and shall be used only when supported by both. * The use of operator-specific logic is proprietary and is outside the scope of this specification. 2.7 Tearing Recovery For contactless transactions, interaction between card and reader can be interrupted if the card is removed prematurely from the RF field or when a protocol error occurs. This can result in “transaction tearing”, where the card and terminal have differing transaction outcomes. With Tearing Recovery, if an EMV transaction tears, the Kernel can invite the cardholder to present the card again. The Kernel may then request the card resume the previous transaction, rather than starting a new transaction. Support for Tearing Recovery is optional for card and Kernel, and shall be used only when supported by both. 2.7.1 Process Overview At the start of transaction processing, the Kernel determines if it needs to recover from a previous torn transaction or begin a new transaction. EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page 29 / 151 © 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. This begins with the Kernel examining the settings in the card’s optional Card Feature Descriptor to determine its support for Tearing Recovery and to extract its unique Card ID. To support Tearing Recovery, the Kernel keeps a record of transaction details in a Tearing Log; populating the log at the start of Initiate Application Processing, then emptying it at the end of successful Read Application Data processing. If the card supports Tearing Recovery and its Card ID matches that recorded in the Tearing Log, then: • The Kernel uses the transaction details recorded in the Tearing Log to send the RESUME GET PROCESSING OPTIONS (RESUME GPO) command to the card • The card compares the PDOL data with that of the previous GET PROCESSING OPTIONS (GPO) or DATA GET PROCESSING OPTIONS (DATA GPO) command (recorded in its own internal log), and: o If there is a match, the card returns the same response message as the previous GPO or DATA GPO command (without updating its CRM counters and accumulators, or incrementing ATC), or o If there is no match, the card processes the command as a new GPO or DATA GPO command (incrementing its ATC and updating CRM counters and accumulators). Else, the Kernel starts a new transaction, and: • Records the new transaction details in the Tearing Log (if Tearing Recovery enabled) • Sends the GPO or DATA GPO command to the card. If there is a timeout or transmission error during the Initiate Application Processing or Read Application Data processing steps, and the Tearing Log is not empty, then the Kernel can invite the cardholder to present the card again. Otherwise, the transaction can proceed and the Kernel can clear the Tearing Log. EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page 30 / 151 © 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. 3 Terminal Transaction Processing Steps This section addresses the Kernel 6 transaction processing requirements, including process flows, in the following sections: • 3.1: Combination Selection Post Processing • 3.2: Read Data Storage • 3.3: Initiate Application Processing • 3.4: Read Application Data • 3.5: Tearing Analysis • 3.6: Offline Data Authentication (ODA) for Offline Transactions • 3.7: Cardholder Verification • 3.8: Processing Restrictions • 3.9: Terminal Action Analysis • 3.10: Online Processing • 3.11: Completion • 3.12: Issuer Update Processing • 3.13: Write Data Storage Details on each APDU command referenced in this section are provided in Section 4, and additional information regarding Outcomes and Outcome Parameters are included in Annex B. 3.1 Combination Selection Post Processing The transaction starts in the Kernel at the handover from Entry Point, which has performed EMV transaction Pre-Processing, Protocol Activation, Combination Selection, and Kernel Activation), or After Kernel Activation, the selected Kernel must check the response sent by the card to the SELECT command. The operations to be performed to validate the answer sent by the card are illustrated in the following figures: • Figure 3-1: Processing Flow (Format Analysis) • Figure 3-2: Processing Flow (PDOL Mandatory Check) • Figure 3-3: Processing Flow (PDOL Optional Check) • Figure 3-4: Processing Flow (Optional Checks) • Figure 3-5: Processing Flow (Optional Feature Checks) • Figure 3-6: Processing Flow (Tearing Recovery Check) EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page 31 / 151 © 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. Figure 3-1: EMV Application Selection – Processing Flow (Format Analysis) Answer to Final SELECT (4) Answer has tag 50 ? (3) Answer has tag A5 ? (2) Answer has tag 84 ? Yes Yes Yes No No No (9) PDOL Analysis (5) Answer has PDOL? Yes No (1) Reset Data Storage Enabled, Extended Logging Enabled, and Tearing Recovery Enabled flags to false (7) Deferred Authorization Supported ? No (8) Set TTQ B2b8 = 1 (Online cryptogram required) Yes (6) Send Try Another Interface Outcome # Description 1 Kernel shall reset its transient Data Storage Enabled, Extended Logging Enabled, and Tearing Recovery Enabled flags to false. 2 The Kernel shall begin the checks on the response received for the final SELECT command. Kernel shall check if “DF name” (tag ‘84’) of the application is provided by the card. If the tag is not present, then go to Step 6. Else continue. EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page 32 / 151 © 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. # Description 3 Kernel shall check if FCI Proprietary Template (tag ‘A5’) is present. If the tag is not present, then go to Step 6. Else continue. 4 Kernel shall check if Application Label (tag ‘50’) is present in the answer provided by the card and is under tag ‘A5’. If the tag is not present as specified, then go to Step 6. Else continue. 5 Kernel shall check if Processing Options Data Object List (PDOL) (tag ‘9F38’) is present in the answer provided by the card and is under tag ‘A5’. If the tag is not present as specified, then go to Step 6. Else go to Step 7. 6 Kernel shall send the Outcome as ‘Try Another Interface’ to request the use of another interface (if one is supported) to the Entry Point. 7 Kernel shall check if it is configured for Deferred Authorizations (true if ‘Deferred Authorization Supported’ flag is present and set to ‘1’). If yes, go to Step 8. Else go to Step 9. 8 Terminal shall indicate in the TTQ that it wishes to process the transaction online (by setting the TTQ B2b8 = ‘1’) 9 Kernel shall go to Figure 3-2 to perform PDOL Analysis. EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page 33 / 151 © 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. Figure 3-2: EMV Application Selection – Processing Flow (PDOL Mandatory Check) (1) TTQ requested and length = (2) Amount Authorized requested and length = Yes Yes No PDOL Analysis (3) Amount Others requested and length = Yes Yes Yes Yes Yes (4) Terminal Country code requested and length = (5) Transaction Currency Code requested and length = (6) Transaction Date requested and length = (7) Transaction Type requested and length = (8a) UN requested Yes No No No No (8b) UN length = No No No Yes (10) Send a Try Another Interface Outcome Optional PDOL checks No (9) Other Interface Supported? Yes NoTerminate EMV ® Contactless Specifications for Payment Systems Kernel 6 Specification v2.12 Page 34 / 151 © 2026 EMVCo, LLC. All rights reserved. Reproduction, distribution and other use of this document is permitted only pursuant to the applicable agreement between the