EMV TLV Parser

Paste BER-TLV hex from a card response, a terminal log or ISO 8583 field 55. Every tag is named and the bitmaps (TVR, TSI, AIP, CVM List, AFL, DOLs) are decoded.

Runs only in your browser. Nothing you paste is sent anywhere. Use test data only; never paste live card numbers or production keys into any online tool.

Decoded

EMV tag reference

TagNameFormatDescription

About EMV TLV

What is BER-TLV?

EMV cards and terminals exchange data as Tag-Length-Value objects. The tag says what the data is, the length says how many bytes follow, and the value holds the data. A tag whose first byte has bit 6 set (for example 6F, 70, 77) is constructed: its value is itself a list of TLV objects.

How are multi-byte tags and lengths encoded?

If the low five bits of the first tag byte are all set (1F), the tag continues; each following byte with bit 8 set means one more byte. Lengths below 128 take one byte. Longer values use 81 followed by one length byte, or 82 followed by two.

Why do some objects show padding?

Cards may pad records with 00 or FF bytes between objects. The parser skips them, as EMV Book 3 allows. An FF followed by another byte is read as a tag, such as FF8105.