96

Kernel Identifier – Terminal

Kernel Identifier – Terminal is the reader's own declaration of which contactless kernels it actually implements, structured to mirror the card-side Kernel Identifier (9F2A) it's related to: its first three bytes follow the same encoding 9F2A uses, so Entry Point can directly compare what a card's directory entry asks for against what this specific terminal can actually do, with a fourth byte specifically flagging Kernel 8 support as a separate capability. This is the field that makes kernel selection a genuine negotiation rather than a card simply dictating terms: a terminal that doesn't support the kernel a card's 9F2A calls for can't process that application via that interface at all, regardless of what the card wants, and Entry Point has to fall back to whatever the terminal's own capability set actually allows. A terminal fleet upgraded to support a new kernel but still reporting an old, pre-upgrade value in 96 will continue silently rejecting or mishandling exactly the applications the upgrade was meant to enable, purely because this one capability-declaration field wasn't updated alongside the actual kernel implementation. See EMV Contactless Book B.

Interactive decoder

Paste a hex value for this tag to decode it in your browser. Nothing is sent anywhere.

Binary (4): C3010000

This tag is not a bitmap; the decoder shows a format-based interpretation.

Decoded example

Example value: C3010000

Related tags

Properties

Tag96
NameKernel Identifier – Terminal
FormatBinary
Length1–8 bytes
SourceTerminal
Templates
BooksEMV Contactless Book B

Frequently asked questions

What is EMV tag 96?
Kernel Identifier – Terminal is the reader's own declaration of which contactless kernels it actually implements, structured to mirror the card-side Kernel Identifier (9F2A) it's related to: its first three bytes follow the same encoding 9F2A uses, so Entry Point can directly compare what a card's directory entry asks for against what this specific terminal can actually do, with a fourth byte specifically flagging Kernel 8 support as a separate capability. This is the field that makes kernel selection a genuine negotiation rather than a card simply dictating terms: a terminal that doesn't support the kernel a card's 9F2A calls for can't process that application via that interface at all, regardless of what the card wants, and Entry Point has to fall back to whatever the terminal's own capability set actually allows. A terminal fleet upgraded to support a new kernel but still reporting an old, pre-upgrade value in 96 will continue silently rejecting or mishandling exactly the applications the upgrade was meant to enable, purely because this one capability-declaration field wasn't updated alongside the actual kernel implementation. See EMV Contactless Book B.
What format and length does EMV tag 96 use?
Tag 96 uses the Binary format and is normally 1–8 bytes long.
Is tag 96 provided by the card or the terminal?
Tag 96 (Kernel Identifier – Terminal) is provided by the Terminal.

Sources

  • EMV-Contactless-Book-B-Entry-Point-Specification-v2.11, p. 41

Receive site updates

Subscribe to receive site updates directly to your email

We won't send spam. You can unsubscribe at any time.