What tag 82 contains, its format and length, an example value and where it goes wrong in testing.
Tag 82 is the Application Interchange Profile. It is a 2-byte bit field the card returns to tell the terminal which EMV functions it supports, such as SDA, DDA, CDA, cardholder verification and issuer authentication.
Tag 82 is the Application Interchange Profile. It is a 2-byte bit field the card returns to tell the terminal which EMV functions it supports, such as SDA, DDA, CDA, cardholder verification and issuer authentication.
The terminal reads the AIP after application selection, in the response to GET PROCESSING OPTIONS. It uses the flags to decide which steps to run. For example, if the card supports CDA, the terminal can ask for a combined data authentication and cryptogram.
| Property | Value |
|---|---|
| Tag | 82 |
| Name | Application Interchange Profile |
| Abbreviation | AIP |
| Format | Binary |
| Length | 2 bytes |
| Source | Card (ICC) |
82 3900
0x39 sets four bits: DDA supported, cardholder verification supported, terminal risk management to be performed and CDA supported.
Enter the value in hex. The decoder runs in your browser and nothing is sent anywhere.
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