The EMV tags you meet most often, with format, length, source, examples and browser-based decoders for the bit fields.
EMV tags identify the data elements a card, terminal and host exchange during a chip transaction. This reference covers the tags that show up most in logs, test cases and host messages, with a decoder for each bit field.
These are the EMV tags that appear most often in logs, test cases and host messages. Each page gives the format, length, an example and the problems that show up in testing. Tags that are bit fields, such as the TVR, TSI, AIP and CID, have a decoder you can use in the browser.
| Tag | Name | Format | Length | Source |
|---|---|---|---|---|
| 9F26 | Application Cryptogram | Binary | 8 bytes | Card (ICC) |
| 9F27 | Cryptogram Information Data | Binary | 1 byte | Card (ICC) |
| 9F10 | Issuer Application Data | Binary | Up to 32 bytes | Card (ICC) |
| 95 | Terminal Verification Results | Binary | 5 bytes | Terminal |
| 9B | Transaction Status Information | Binary | 2 bytes | Terminal |
| 82 | Application Interchange Profile | Binary | 2 bytes | Card (ICC) |
| 9F34 | Cardholder Verification Method (CVM) Results | Binary | 3 bytes | Terminal |
| 9F37 | Unpredictable Number | Binary | 4 bytes | Terminal |
| 9F36 | Application Transaction Counter | Binary | 2 bytes | Card (ICC) |
| 5F2A | Transaction Currency Code | Numeric | 2 bytes | Terminal |
| 9A | Transaction Date | Numeric | 3 bytes | Terminal |
| 9C | Transaction Type | Numeric | 1 byte | Terminal |
| 9F02 | Amount, Authorised | Numeric | 6 bytes | Terminal |
| 9F1A | Terminal Country Code | Numeric | 2 bytes | Terminal |
| 9F33 | Terminal Capabilities | Binary | 3 bytes | Terminal |
| 4F | Application Identifier (AID) - card | Binary | 5 to 16 bytes | Card (ICC) |
| 84 | Dedicated File (DF) Name | Binary | 5 to 16 bytes | Card (ICC) |
| 5A | Application Primary Account Number (PAN) | Compressed numeric | Up to 10 bytes | Card (ICC) |
| 57 | Track 2 Equivalent Data | Binary | Up to 19 bytes | Card (ICC) |
EMV data is carried as BER-TLV: a tag, a length and a value. A tag is one or two bytes. When the low five bits of the first byte are all 1, the tag continues into a second byte, which is why tags such as 9F26 and 5F2A are two bytes long. The length follows, and then the value. Constructed tags hold other tags inside them.
The TLV parser decodes a full string, and our blog post Reading an EMV Log walks through 9F26, 9F27, 95 and 82 with worked examples. The EMV tag lookup searches the whole dictionary by tag or name.
In an online authorization, the chip data travels in ISO 8583 field 55. Track 2 equivalent data and the PAN can also appear in fields 35 and 2. See the ISO 8583 reference and the ISO 8583 decoder.
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