What tag 9F10 contains, its format and length, an example value and where it goes wrong in testing.
Tag 9F10 is the Issuer Application Data. It is a block of data the issuer's card application returns with the cryptogram. Its contents are defined by the issuer and the card scheme, not by EMVCo.
Tag 9F10 is the Issuer Application Data. It is a block of data the issuer's card application returns with the cryptogram. Its contents are defined by the issuer and the card scheme, not by EMVCo.
In many implementations it carries a key derivation index, a cryptogram version number and the Card Verification Results, and some formats add further counters and flags. Because the layout is scheme-specific, you decode it with the scheme's specification or the issuer's documentation.
The terminal does not interpret it. It forwards it in the online request, usually inside field 55, so the issuer can see how the card reached its decision.
| Property | Value |
|---|---|
| Tag | 9F10 |
| Name | Issuer Application Data |
| Abbreviation | IAD |
| Format | Binary |
| Length | Up to 32 bytes |
| Source | Card (ICC) |
9F10 06011203A00000
An example of the length and shape only. The meaning of each byte depends on the issuer and scheme format.
Paste a full EMV data string into the TLV parser to see every tag decoded together, or search all tags in the EMV tag lookup. See the full tag list.
If your payment app has to pass EMV Level 3, see our certification services and Foundry.
We have taken 133 payment applications through EMV Level 3 across many regions. Tell us about your project.
Talk to us Book a meeting with a founder