AIP decoder (82)
The Application Interchange Profile (AIP, tag 82) is two bytes in which the card says which functions it supports, such as the offline data authentication methods (SDA, DDA, and CDA) and cardholder verification. The card returns it in the GET PROCESSING OPTIONS response, and the terminal sends it to the issuer in DE 55.
Look at it when offline data authentication or cardholder verification does not run as expected, and compare it with the terminal capabilities (9F33): a method runs only when both sides support it.
Each set bit is a function the card supports or a step it asks the terminal to perform. Bits marked as reserved belong to other specifications, such as the contactless ones.
Worked example: in the GPO response example the AIP is 19 80. Byte 1 says cardholder verification is supported, terminal risk management is to be performed, and CDA is supported; byte 2, bit 8 is reserved for the EMV contactless specifications.
New to EMV? Read EMV in 5 minutes or browse the glossary
Everything runs in your browser. Nothing you enter leaves this page.
Spaces, line breaks, colons, and the 0x prefix are ignored. Toggle the bits to build a value; the hex updates as you go.
Hex value: 0000
How to read it: bytes are numbered from 1 on the left, and bits from 8 (the leftmost) to 1 (the rightmost). A set bit is 1. Bits reserved for future use (RFU) should be 0.
| Bit | State | Meaning |
|---|---|---|
| b8 | ||
| b7 | ||
| b6 | ||
| b5 | ||
| b4 | ||
| b3 | ||
| b2 | ||
| b1 |
| Bit | State | Meaning |
|---|---|---|
| b8 | ||
| b7 | ||
| b6 | ||
| b5 | ||
| b4 | ||
| b3 | ||
| b2 | ||
| b1 |