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.
Is my card data sent to a server? No. Parsing happens entirely in your browser. Nothing you paste is transmitted, logged, or stored.
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.
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.
No. Parsing happens entirely in your browser. Nothing you paste is transmitted, logged, or stored.
This tool comes out of our EMV Level 3 work. If you are scoping a contact, contactless, or unattended certification, see our EMV capabilities →