EMV Contactless Kernels — Hierarchy & Dependencies
How EMVCo's contactless specification fans out into seven scheme kernels and the unified Kernel 8: the structural dependency tree, what happens during a tap, and how the scheme kernels converge into C-8.
Kernel-to-scheme mapping
Book B (Entry Point) reads the card's AID and activates exactly one Book C kernel. Each kernel below links to its full guide.
| Kernel | Book | Scheme | Product | Status | |
|---|---|---|---|---|---|
| Kernel 2 | C-2 | Mastercard | PayPass / M-Chip | Active | Guide → |
| Kernel 3 | C-3 | Visa | payWave / qVSDC | Active | Guide → |
| Kernel 4 | C-4 | American Express | ExpressPay | Active | Guide → |
| Kernel 5 | C-5 | JCB | J/Speedy | Active | Guide → |
| Kernel 6 | C-6 | Discover | D-PAS | Active | Guide → |
| Kernel 7 | C-7 | UnionPay | QuickPass | Active | Guide → |
| Kernel 8 | C-8 | EMVCo (common) | Unified kernel v1.1 | Emerging | Guide → |
Kernel 1 (C-1) is retired — removed in Book A v2.7; its Visa AIDs migrated to C-3 and JCB AIDs to C-5.
Structural dependency
Spec families → Books → kernels → schemes, mapped onto the L1/L2/L3 runtime stack. Solid lines are static composition; the orange path is the Entry Point's runtime, AID-driven dispatch.
Runtime tap sequence
What happens during a tap: PPSE → candidate AID list → Entry Point match → kernel activation → outcome. Book B drives the dispatch; the activated Book C kernel then runs the exchange.
APDU detail is illustrative; exact tags and flow vary by kernel and Books A–D bundle version.
Convergence to Kernel 8
Six scheme kernels run in parallel under one Books A–D bundle, then fold into the unified EMVCo kernel. Verified anchors marked ◆: C-1's retirement and C-8's publication (v1.0 Oct 2022, v1.1 2022/23).
PayProbe note: C-2…C-7 stay live during rollout — test both the scheme kernels and C-8 in parallel.
Kernel 8 adoption (October 2026): EMVCo has approved Book C-8 implementations from Ingenico (the first, October 2024, when type-approval testing opened), Castles Technology (July 2026) and ID TECH (August 2026). The specification is still v1.1, corrected by SB 325, and no card scheme has published a deadline for terminal support yet.
Bulletins to know (EMVCo Q2 2026): SB 317 removes the Mag-stripe Mode implementation option from Kernel 2, leaving "with/without Data Exchange" and "Data Storage"; SB 314 / SB 319 extend Kernel 2's Terminal Risk Management Data (tag 9F1D) with Deferred Authorisation and Transit Gate bits plus a payment-system byte; SB 325 corrects Book C-8 (Service Code removed, "decryption failed" signal, First Wire flag length); SB 326/327 correct Books A and B v2.11; DSB 331 adds RRP timing parameters for Kernel 2. TTA Bulletin 293 confirms every kernel with a Letter of Approval valid before January 2031 must keep processing after the 2038 date rollover.
Per-kernel guides & tools
Live decoders: TTQ Decoder · CTQ Decoder · Kernel 8 Qualifier · EMV TLV Decoder
Next steps
Related articles
Common questions
What is the EMV contact kernel?
The EMV Level 2 software that runs a chip-insert transaction: application selection, reading records, offline data authentication, cardholder verification, terminal risk management and the GENERATE AC exchange defined in EMV Books 1–4. One contact kernel serves every scheme, unlike contactless.
What is the difference between contact and contactless kernels?
Contact uses a single EMV kernel for all schemes. Contactless historically had one kernel per scheme (C-2 Mastercard, C-3 Visa, C-4 Amex, C-5 JCB, C-6 Discover, C-7 UnionPay); EMVCo’s Kernel 8 is a common contactless kernel designed to replace them over time.