AIP Decoder
Decode the Application Interchange Profile (EMV tag 82) 2-byte value to show which EMV functions are supported by the card.
Follows EMV 4.4 Book 3 Annex C1 · Book C-2Application Interchange Profile (tag 82), incl. Kernel 2 bits·verified Oct 2026· double-checked Oct 2026— every bit checked against openemv/emv-utils, proxmark3 and binaryfoo
Try it as a puzzle: put the steps of a chip payment in order →
Byte 1 is defined by EMV Book 3 for contact and contactless cards alike, except bit 2. Byte 1 bit 2 and byte 2 are left to the contactless kernels; the meanings shown are Kernel 2's (Mastercard, Book C-2), and other kernels may use these bits differently.
What the Application Interchange Profile (82) declares
The Application Interchange Profile (AIP), EMV tag 82, is a 2-byte bitmap in which the card declares which EMV functions it supports for the selected application. The terminal reads it immediately after GET PROCESSING OPTIONS and uses it to plan the rest of the transaction — there is no point attempting dynamic data authentication, for example, if the card's AIP says it is not supported.
The flags that matter
Byte 1 carries the meaningful capabilities: SDA (static data authentication), DDA (dynamic data authentication), "Cardholder verification is supported", "Terminal risk management is to be performed", "Issuer authentication is supported", CDA (combined DDA/application cryptogram generation) and, from EMV 4.4, XDA (the elliptic-curve method). Byte 1 bit 2 and byte 2 are left to the contactless kernels: Kernel 2 (Mastercard) uses them for "On device cardholder verification is supported", "EMV mode is supported" and "Relay resistance protocol is supported". The combination of the SDA/DDA/CDA/XDA bits tells you which offline authentication method the card and terminal will negotiate, which is the single most common reason a chip transaction behaves differently from another.
Common questions
SDA, DDA and CDA are all clear — how does the card authenticate?
It does not authenticate offline (unless an EMV 4.4 card sets XDA). The terminal sets "Offline data authentication was not performed" in the TVR and relies on going online, and an offline-only terminal will typically decline.
Where does the AIP come from in a trace?
It is returned in the GPO response together with the AFL. In format 1 (template 80) the AIP is simply the first two bytes of the value, with no tag; in format 2 (template 77) it is tag 82 next to tag 94 (AFL).
Bit definitions follow EMV 4.4 Book 3 Annex C1 and, for the contactless bits, Book C-2. Decoding runs entirely in your browser.