9F75

Unprotected Data Envelope 1

Unprotected Data Envelope 1 is the first member of the same free-read, non-integrity-protected Kernel 2 envelope family already covered in this dictionary via Envelope 2 (9F76) and Envelope 5 (9F79) - the same design tradeoff applies here: data that doesn't need cryptographic guarantees to be useful, kept in its own lightweight field rather than overloading the security-critical parts of the card's data model. It's related to both 9F76 and to Protected Data Envelope 2 (9F71, covered alongside it here), which sits in the equivalent numbered position in the write-protected half of the same envelope design - the pairing across the protected and unprotected families by number (1 to 2, and so on through the sequence) reflects how Kernel 2's data-storage feature was structured, not a claim about what specific content either envelope carries. As with its unprotected siblings, an application reading 9F75 is trusting its content without a cryptographic basis for that trust, and its exact payload is scheme- or issuer-specific rather than defined by core EMV. See EMV Contactless Book C-2.

Interactive decoder

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

Binary (3): 0A0A0A

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

Decoded example

Example value: 0A0A0A

Related tags

Properties

Tag9F75
NameUnprotected Data Envelope 1
FormatBinary
Lengthvariable
SourceCard (ICC)
Templates
BooksEMV Contactless Book C-2

Frequently asked questions

What is EMV tag 9F75?
Unprotected Data Envelope 1 is the first member of the same free-read, non-integrity-protected Kernel 2 envelope family already covered in this dictionary via Envelope 2 (9F76) and Envelope 5 (9F79) - the same design tradeoff applies here: data that doesn't need cryptographic guarantees to be useful, kept in its own lightweight field rather than overloading the security-critical parts of the card's data model. It's related to both 9F76 and to Protected Data Envelope 2 (9F71, covered alongside it here), which sits in the equivalent numbered position in the write-protected half of the same envelope design - the pairing across the protected and unprotected families by number (1 to 2, and so on through the sequence) reflects how Kernel 2's data-storage feature was structured, not a claim about what specific content either envelope carries. As with its unprotected siblings, an application reading 9F75 is trusting its content without a cryptographic basis for that trust, and its exact payload is scheme- or issuer-specific rather than defined by core EMV. See EMV Contactless Book C-2.
What format and length does EMV tag 9F75 use?
Tag 9F75 uses the Binary format and is normally variable long.
Is tag 9F75 provided by the card or the terminal?
Tag 9F75 (Unprotected Data Envelope 1) is provided by the Card (ICC).

Sources

  • C-2-Kernel-2-V2.11-Final-June-2023, p. 434

Receive site updates

Subscribe to receive site updates directly to your email

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