What it is
The Application Interchange Profile (AIPApplication Interchange ProfileEMV tag 82 — a bitmap of the functions the card supports (SDA/DDA/CDA, cardholder verification, and more).View in glossary →) is a 2-byte bitmap the card returns in GET PROCESSING OPTIONS to declare which functions it supports: SDAStatic Data AuthenticationOffline check where the terminal verifies a fixed issuer signature over static card data. It cannot prove the card is live, so it is vulnerable to cloning and replay.View in glossary →, DDADynamic Data AuthenticationOffline check where the card signs unique, per-transaction data with its own private key — proving the chip is genuine and not a clone.View in glossary →, CDACombined DDA / Application Cryptogram generationThe strongest offline authentication: the card signs the dynamic data and the transaction cryptogram together in one step, preventing tamper (“wedge”) attacks.View in glossary →, cardholder verification, terminal risk management, issuer authentication, and on-device CVMCardholder Verification MethodHow the cardholder is verified — for example offline PIN, online PIN, signature, or no CVM required.View in glossary →.
The terminal reads these bits to decide which offline data authentication method to attempt and whether to run CVMCardholder Verification MethodHow the cardholder is verified — for example offline PIN, online PIN, signature, or no CVM required.View in glossary → and risk management. Byte 2 bit 8 additionally signals MSDMagnetic-Stripe DataA legacy contactless mode that emulates magnetic-stripe track data instead of doing full EMV chip processing. Largely deprecated.View in glossary → support in some Visa contactless profiles.
Where it appears
Returned by the card in the GET PROCESSING OPTIONS response, at the start of the transaction.
Specification reference
Defined in: EMV 4.x Book 3 (Application Specification), Annex A — Data Element Dictionary
Bit-level definitions below follow: EMV Book 3, Table 45 — Application Interchange Profile (2 bytes)
Bit & value breakdown
EMV Book 3, Table 45 — Application Interchange Profile (2 bytes)
Byte 1
b8 = 0x80RFUReserved for Future UseBits or bytes with no current meaning, reserved by the spec; they must be set to zero. — must be 0b5 = 0x10Cardholder verification is supportedb4 = 0x08Terminal risk management to be performedb3 = 0x04Issuer authentication is supportedb2 = 0x02On-device cardholder verification is supportedByte 2
b7–b1RFUReserved for Future UseBits or bytes with no current meaning, reserved by the spec; they must be set to zero. — must be 0Example values
3900DDA + CVM + TRM + issuer auth supported
1980CVM + issuer auth + CDA, with MSD flagged in byte 2
Meaning by contactless kernel