EMV TLV Parser & Builder
Paste BER-TLV hex from a chip or contactless transaction and read it as a labeled, nested tag tree. Key tags are bit-decoded — AIP, TVR, CVM, CID, TTQ — and DOLs are expanded into the data they request.
About EMV BER-TLV
EMV chip and contactless data is encoded as BER-TLV: every data element is a Tag, a Length, and a Value. Tags can be a single byte or several; the constructed bit (0x20) marks objects that contain more TLV objects nested inside, like the FCI template (6F) or the Read Record template (70). This parser walks that structure recursively and labels each tag from the EMVCo specification.
What gets decoded
- Several hundred EMVCo and common proprietary tags, labeled by name
- Bitwise decoding for AIP (82), TVR (95), TSI (9B), CID (9F27), Terminal Capabilities (9F33), TTQ (9F66) and CTQ (9F6C)
- DOL expansion for CDOL1, CDOL2, PDOL, DDOL and TDOL — showing exactly which data each list requests
- ASCII rendering for text tags such as Application Label and Cardholder Name, plus date and currency humanizers
Frequently asked questions
What is BER-TLV in EMV?
BER-TLV (Tag-Length-Value under Basic Encoding Rules) is how EMVCo encodes payment data exchanged between a card and terminal. Each object carries a tag, a length, and a value, and constructed objects nest further objects inside.
Is my card data sent to a server?
No. Parsing happens entirely in your browser. Nothing you paste is transmitted, logged, or stored.
Need help with a certification?
This tool comes out of our EMV Level 3 work. If you are scoping a contact, contactless, or unattended certification, see our EMV capabilities →