Tools — Payments
ISO 8583 & EMV TLV decoder
Paste an ISO 8583 message or EMV BER-TLV hex and see every field decoded. Runs in your browser, nothing is uploaded or stored, and PANs are always masked.
Never paste real card data. Use test numbers only. PANs and Track 2 are masked to first 6 + last 4 in the output.
Result
Supported subset
ISO 8583:1987-style, ASCII encoding: 4-digit MTI, 16 hex character primary bitmap (+ secondary when bit 1 is set), ASCII LLVAR/LLLVAR lengths. Data elements: 2, 3, 4, 7, 11, 12, 13, 14, 18, 22, 25, 32, 35, 37, 38, 39, 41, 42, 43, 48, 49, 52, 55, 70. DE55 is hex text decoded as EMV TLV. Not supported: binary/BCD packing, EBCDIC, tertiary bitmap. An unsupported DE in the bitmap stops parsing and is reported with its offset.
Privacy
Runs entirely in your browser. Nothing is uploaded or stored, and PANs are masked in the output. Never paste real card data.
Questions
Is my data uploaded?
No. Decoding runs in your browser and nothing is sent or stored. Still, never paste real card data: use test numbers such as 4111 1111 1111 1111.
Are card numbers shown in full?
Never. PANs (DE2, EMV tag 5A) and Track 2 (DE35, tags 57 and 9F6B) are masked to the first 6 and last 4 digits, Track 2 discretionary data and PIN blocks are redacted, and a warning appears when the input contains a full PAN.
Which ISO 8583 encodings are supported?
ISO 8583:1987-style ASCII messages: a 4-digit MTI, a 16 hex character bitmap (plus a secondary bitmap when bit 1 is set), ASCII LLVAR/LLLVAR lengths, or a hex dump of those ASCII bytes. Supported data elements: 2, 3, 4, 7, 11, 12, 13, 14, 18, 22, 25, 32, 35, 37, 38, 39, 41, 42, 43, 48, 49, 52, 55, 70. Binary or BCD packed messages and EBCDIC are not supported.
What happens with an unsupported field?
Parsing stops at that field and reports 'unsupported DE n at offset x'. Everything decoded before it is still shown.
How is DE55 handled?
DE55 is read as hex text (its length counts hex characters) and decoded as EMV BER-TLV with common tag names.