What tag 9F26 contains, its format and length, an example value and where it goes wrong in testing.
Tag 9F26 is the Application Cryptogram, the 8-byte value the card computes to prove that it took part in the transaction. It comes back in the response to the GENERATE AC command.
Tag 9F26 is the Application Cryptogram, the 8-byte value the card computes to prove that it took part in the transaction. It comes back in the response to the GENERATE AC command.
The kind of cryptogram depends on the card's decision, which is reported in tag 9F27 (Cryptogram Information Data). An ARQC asks to go online, a TC approves the transaction offline, and an AAC declines it.
The card builds the cryptogram from transaction data supplied by the terminal, such as the amount, currency, date, terminal verification results and unpredictable number, plus card data like the application transaction counter. It uses keys that only the card and the issuer share, so the terminal cannot verify an ARQC itself. The issuer host checks it when the authorization request arrives.
In an online message the cryptogram usually travels inside the ICC data of ISO 8583 field 55.
| Property | Value |
|---|---|
| Tag | 9F26 |
| Name | Application Cryptogram |
| Abbreviation | AC |
| Format | Binary |
| Length | 8 bytes |
| Source | Card (ICC) |
9F26 A1B2C3D4E5F60718
An 8-byte cryptogram. Its value looks random. Only the issuer can check it, so a log review compares the type in 9F27 and the data inputs, not the value itself.
For worked examples, read Reading an EMV Log: What Tags 9F26, 9F27, 95 and 82 Tell You. 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