What is BER-TLV in EMV?

BER-TLV (Basic Encoding Rules Tag-Length-Value) is the data encoding format defined in ISO 8825-1 and used throughout the EMV specification. Each data object has a tag (identifying the data type), a length, and a value. Some tags are 'constructed' (containing nested TLV objects) while others are 'primitive' (containing raw data).

What is the difference between TLV and BER-TLV?

TLV is the generic concept of Tag-Length-Value encoding. BER-TLV is the specific ASN.1 Basic Encoding Rules implementation used in smart card and EMV standards. In practice, the terms are used interchangeably in the EMV context, though BER-TLV has stricter rules for multi-byte tags and length encoding.

How do I parse EMV TLV data?

Paste the hex-encoded TLV string into an online parser like the CardWise EMV TLV Parser. The parser will decode each tag, look up its name in the EMV tag dictionary, show the length, and display the value. Constructed objects are recursively parsed to show nested TLV structures.

Disclosure: As an Amazon Associate, CardWise earns from qualifying purchases at no additional cost to you. This does not affect our recommendations.

TLV/BER-TLV Parser Comparison — Decoding EMV's Data Language

EMV payment cards, smart cards, and PKI certificates all speak the same data language: BER-TLV (Basic Encoding Rules, Tag-Length-Value). Every piece of data — from your card number to the cryptogram — is encoded as a TLV object with a tag that identifies the data type, a length, and the value itself. Parsing TLV correctly is essential for EMV development, smart card debugging, and security auditing.

This comparison reviews the available TLV parsers and how they handle tag resolution, constructed objects, multi-byte tags, length encoding, and EMV-specific tag dictionaries.

TLV Structure

Tag (1-2 bytes)  Length (1-3 bytes)  Value (N bytes)
  |                 |                   |
  Identifies        Size of value       The actual data
  data type         that follows

Examples:
9F02 → Amount, Authorized (numeric, 6 bytes)
5A   → Application Primary Account Number (PAN)
9F36 → Application Transaction Counter (ATC)
8A   → Authorization Response Code
57   → Track 2 Equivalent Data

Some tags are constructed (bit 5 of the first tag byte = 1), meaning their value contains nested TLV objects. For example, tag 70 (EMV Reply Template for SDA) is constructed and contains primitive tags like 90 (Issuer Public Key Certificate) and 9F32 (Issuer Public Key Exponent).

Parser Comparison

Feature	CardWise EMV TLV Parser	emv-lab.dev	PC/SC TLV Tools
Platform	Web (browser, no install)	Web	Desktop (CLI/GUI)
EMV Tag Dictionary	Full (EMV 4.3 Book 3 + kernel specs)	Full EMV + payment scheme tags	Basic EMV tags
Constructed Object Parsing	Recursive (unlimited depth)	Recursive	Recursive
Multi-byte Tags	Yes (9Fxx, BFxx)	Yes	Yes
Length Encoding	1-byte, 2-byte, 3-byte forms	Yes	Yes
Tag Name Resolution	EMV + ISO 7816 + GlobalPlatform	EMV + payment scheme	EMV only
Privacy	Client-side (no upload)	Server-side (data sent to server)	Local
Hex Input Format	Flexible (spaces, newlines, uppercase/lowercase)	Requires clean hex	Requires clean hex
Error Handling	Reports exact offset of malformed TLV	Generic error	Generic error

Privacy Consideration

Security note: TLV data from a real payment card can contain the card's PAN, track 2 data, and cryptogram information. If you paste this data into a server-side parser, the data is transmitted over the internet to the parser's backend. The CardWise EMV TLV Parser performs all decoding client-side in your browser — no TLV data ever leaves your device. This is critical when parsing data from production cards during security testing.

Common EMV Tags

Tag	Name	Description
4F	Application Identifier (AID)	Identifies the card application (e.g., A0000000041010 for Visa Debit)
5A	Application PAN	Primary Account Number (16 digits)
57	Track 2 Equivalent Data	PAN + expiration date + service code
5F24	Application Expiration Date	YYMMDD format
8A	Authorization Response Code	00 = approved, 05 = declined, etc.
9F02	Amount, Authorized	Transaction amount in minor units (cents)
9F36	Application Transaction Counter	Incrementing counter for each transaction
9F26	Application Cryptogram (AC)	The EMV cryptogram (ARQC, TC, or AAC)
9F10	Issuer Application Data	Card-specific data for issuer verification
70	EMV Reply Template for SDA	Constructed: contains SDA certificates and data

How to parse EMV TLV: Capture the raw response from the card (e.g., the READ RECORD APDU response). Paste the hex string into the CardWise EMV TLV Parser. The parser will identify each tag, resolve its name, show the length, and recursively decode constructed objects. You can also use the EMV Tag Lookup to search for a specific tag by its hex code.

ACR122U NFC Reader — Capture raw EMV TLV data from contactless payment cards. Use with the CardWise TLV Parser for instant client-side decoding. — Check Price on Amazon

Use Cases for TLV Parsing

EMV development: Debug contactless transaction flows by inspecting the TLV data exchanged between the card and terminal.
Card personalization: Verify that the correct TLV data objects were written to the card during personalization.
Security auditing: Inspect the cryptogram, ATC, and issuer application data to verify transaction integrity.
Interoperability testing: Compare TLV responses from different card manufacturers to ensure terminal compatibility.
PKI certificate parsing: X.509 certificates use DER encoding (a variant of BER-TLV). A BER-TLV parser can decode the certificate's ASN.1 structure.

Related Comparisons

ATR Parser Comparison — decoding the smart card's initial identification
GPO vs AC Commands — where TLV data is exchanged in the EMV flow
EMV vs Magnetic Stripe — why TLV encoding replaced track data
ASN.1 Parser Comparison — parsing X.509 certificates and DER structures

Summary

The CardWise EMV TLV Parser stands out for client-side privacy and comprehensive tag resolution. When parsing TLV data from production cards, never paste it into a server-side tool. The CardWise parser decodes entirely in your browser, supports recursive constructed object parsing, and includes the full EMV tag dictionary plus ISO 7816 and GlobalPlatform tags.

Ready to decode TLV data? Try our EMV TLV Parser or the EMV Tag Lookup.

← ATR Parser Comparison GPO vs AC Commands →