Reading an EMV Log: What Tags 9F26, 9F27, 95 and 82 Tell You
Four EMV tags explain most of what happened in a chip transaction. Here is how to read them, how to read the ISO 8583 bitmap that carries them, and the free tools that decode both.
A chip transaction log looks like a wall of hex. Most of what you need to know sits in four tags. Learn to read them and a failed test case turns from a mystery into a short list of causes.
9F27: what did the card decide?
Tag 9F27 is the Cryptogram Information Data. The top two bits give the type of cryptogram the card returned.
→ 00 is an AAC. The card declines.
→ 01 is a TC. The card approves the transaction offline.
→ 10 is an ARQC. The card asks to go online.
A value of 80 is binary 1000 0000, so the top bits are 10 and the card wants to go online. A value of 40 is a TC, and 00 is a decline. Read this tag first, because every other question depends on it.
9F26: the cryptogram
Tag 9F26 is the Application Cryptogram, an 8-byte value. The card builds it from transaction data the terminal sends, such as the amount, currency, date, terminal verification results and an unpredictable number, using keys that only the card and the issuer share.
The terminal cannot check an ARQC. The issuer host does. So when a host rejects a cryptogram, the usual cause is a mismatch in the data. The amount, currency, date or one of the other inputs sent online differs from what the card saw, often because middleware reformatted a field.
95: what did the terminal find?
Tag 95 is the Terminal Verification Results, a 5-byte set of flags where the terminal records what happened during its checks.
Take the value 8000008000.
→ The first byte is 80. Bit 8 is set, so offline data authentication was not performed.
→ The fourth byte is 80. Bit 8 is set, so the transaction exceeds the floor limit.
That tells you the terminal did not run offline authentication, which is normal for an online-only terminal, and that the amount was over the floor limit, which is why the transaction went online. Nothing is wrong. Compare that with a TVR that flags a failed authentication or a PIN problem, and you can see how fast this tag narrows things down.
82: what can the card do?
Tag 82 is the Application Interchange Profile, a 2-byte set of flags the card returns to say which EMV functions it supports.
Take the value 3900. The first byte, 39, sets four bits: dynamic data authentication is supported, cardholder verification is supported, terminal risk management is to be performed and combined data authentication is supported. The value 5C00 would show something different: static data authentication, cardholder verification, terminal risk management and issuer authentication.
If the terminal runs a method the card does not support, the AIP is the first place to look.
The ISO 8583 bitmap that carries it all
When the transaction goes online, the chip data travels in an ISO 8583 message, usually in field 55. The message starts with a bitmap that says which fields are present.
The bitmap is 64 bits, written as 16 hex characters. Each bit stands for one field, and a 1 means the field is in the message. If bit 1 is set, a second 64-bit bitmap follows and covers fields 65 to 128.
Take the bitmap 7234000000000000. The first digit 7 is binary 0111, so fields 2, 3 and 4 are present. The next digit 2 is 0010, so field 7 is present. The digit 3 is 0011, so fields 11 and 12 are present, and the digit 4 is 0100, so field 14 is present. The message carries fields 2, 3, 4, 7, 11, 12 and 14.
Free tools to read all of this
We built browser-based tools so you do not have to decode this by hand. They run entirely in your browser. Nothing you paste is sent to a server.
→ EMV tag lookup: search any tag by number or name and decode TVR, TSI, AIP, CID and terminal capabilities. https://paying.co/tools/emv-tag-lookup/
→ EMV TLV parser: paste a full data string and see every tag decoded together. https://paying.co/tools/emv-tlv-parser/
→ ISO 8583 bitmap decoder: turn a bitmap into the list of fields, or build one from field numbers. https://paying.co/tools/iso8583-bitmap-decoder/
→ EMV tag reference: pages for the most common tags, with examples and what goes wrong in testing. https://paying.co/emv-tags/
Use test data only. Do not paste real card numbers into any tool.
When the log is not enough
Reading tags tells you what happened. It does not tell you how to get a payment application through certification. If you are heading into EMV Level 3, see https://paying.co/emv-certification/ or talk to us at https://paying.co/contact-us/.