Ambimat GroupAmbimatAmbiSecureV2XeSIM & eUICCAmbiAutomationEngineering BlogAhmedabad · India · Est. 1982

EMV data is encoded as BER-TLV — each field is a Tag, a Length, and a Value. The tag identifies the data element (for example 0x5A is the Application PAN, 0x9F26 is the Application Cryptogram, 0x82 is the Application Interchange Profile), and tags may be primitive (a value) or constructed (nesting more TLV objects). This reference lists the common EMV tags seen in contact and contactless transaction flows across the EMV Books and the contactless kernels.

EMV

EMV tag reference database

Searchable EMV tag reference. Books 3, 4, and Contactless. Filter by category to narrow down to the tags you need.

TagNameCategoryDescription
4F #AID (Application Identifier)identifierIdentifies the application present on the card.
50 #Application LabelidentifierMnemonic for the cardholder.
57 #Track 2 Equivalent Datacard-dataMaps to mag stripe track 2 — PAN, expiry, service code.
5A #PANcard-dataPrimary Account Number, BCD-coded.
5F20 #Cardholder Namecard-data
5F24 #Application Expiration Datecard-dataYYMMDD.
5F25 #Application Effective Datecard-data
5F28 #Issuer Country Codecard-data
5F2A #Transaction Currency Codetransaction
5F2D #Language Preferencecard-data
5F30 #Service Codecard-data
5F34 #Application PAN Sequence Numbercard-data
6F #FCI TemplatetemplateReturned in SELECT response.
70 #AEF Data Templatetemplate
77 #Response Message Template Format 2templateGENERATE AC response.
80 #Response Message Template Format 1template
82 #Application Interchange Profile (AIP)capability2 bytes: SDA, DDA, cardholder verif, terminal risk, issuer auth, CDA support.
84 #DF Nameidentifier
88 #SFIidentifierShort File Identifier.
8C #CDOL1dolCard Risk Management DOL 1.
8D #CDOL2dol
8E #CVM ListsecurityCardholder Verification Method List.
8F #CA Public Key Indexcrypto
90 #Issuer Public Key Certificatecrypto
92 #Issuer Public Key Remaindercrypto
94 #AFLidentifierApplication File Locator.
95 #TVRtransactionTerminal Verification Results.
9A #Transaction DatetransactionYYMMDD.
9C #Transaction Typetransaction00=Goods, 01=Cash, 09=Cashback, 20=Refund.
9F02 #Amount, Authorised (Numeric)transaction
9F03 #Amount, Other (Numeric)transaction
9F07 #Application Usage Controlcapability
9F08 #Application Version Number — cardcapability
9F09 #Application Version Number — terminalcapability
9F10 #Issuer Application Data (IAD)card-data
9F1A #Terminal Country Codetransaction
9F26 #Application Cryptogram (ARQC/TC/AAC)cryptoThe headline 8-byte cryptogram from GENERATE AC.
9F27 #Cryptogram Information Data (CID)crypto0x80 ARQC, 0x40 TC, 0x00 AAC.
9F32 #Issuer Public Key Exponentcrypto
9F33 #Terminal Capabilitiescapability
9F34 #CVM Resultssecurity
9F35 #Terminal Typecapability
9F36 #Application Transaction Counter (ATC)transaction
9F37 #Unpredictable Numbertransaction
9F38 #PDOLdolProcessing Options Data Object List.
9F40 #Additional Terminal Capabilitiescapability
9F42 #Application Currency Codetransaction
9F44 #Application Currency Exponenttransaction
9F46 #ICC Public Key Certificatecrypto
9F47 #ICC Public Key Exponentcrypto
9F48 #ICC Public Key Remaindercrypto
9F4B #Signed Dynamic Application Datacrypto
9F4E #Merchant Name and Locationtransaction
9F66 #Terminal Transaction Qualifiers (TTQ)capabilityEMV Contactless qVSDC.
A5 #FCI Proprietary Templatetemplate
BF0C #FCI Issuer Discretionary Datatemplate

What this reference covers

Spec

EMV Books 3 and 4; EMV Contactless C-2 / C-3.

Usage notes

A tag's first byte tells you its shape: bit 6 (0x20) set means the object is constructed and its value is itself TLV; a low nibble of 0x1F in the first byte means the tag continues into further bytes (two-byte tags like 0x9F02). Parse length first, then read exactly that many value bytes before moving to the next tag.

  • Templates such as 0x70 (READ RECORD) and 0x77 (response message template) are constructed — decode their contents recursively.
  • Proprietary tags in the 0x9Fxx and 0xDFxx space are kernel- and issuer-specific; confirm meaning against the relevant EMV kernel specification.
  • Use the TLV parser to expand a full record and the EMV tag dictionary tool for quick lookups.

Frequently asked questions

What is an EMV tag?

A BER-TLV identifier for a data object defined in EMV Books 3 and 4 and the contactless specifications — 5A is the application PAN, 9F02 the authorised amount.

Why are many EMV tags two bytes?

Because the single-byte space ran out. A first byte with its low five bits set signals continuation, which is how the 9Fxx family exists.

What is a DOL?

A Data Object List such as PDOL or CDOL1 — the card lists tags and lengths, and the terminal returns the values concatenated in that exact order with no tags and no lengths.

What is the difference between contact and contactless tag sets?

Contactless adds its own tags and profiles on top of the Book 3 set, which is why a tag present in a contactless flow may be absent from a contact transaction.

Which tags must never be logged?

Anything carrying cardholder or cryptographic data — full PAN, track equivalents and key material. Logging findings are a common cause of certification failure.