Paste an ISO 8583 message and read its Message Type Indicator, expand the primary and secondary bitmaps, and see exactly which data elements the message declares — each labeled by field name.
What is ISO 8583? ISO 8583 is the international standard for financial transaction messaging between cards, terminals, acquirers, and issuers. A message has a Message Type Indicator, one or two bitmaps marking which data elements are present, and the data elements themselves.
ISO 8583 is the messaging standard that moves an authorization, reversal, or settlement record between a terminal, an acquirer, a network, and an issuer. Every message opens with a four-character Message Type Indicator describing its version, class, function, and origin, followed by a bitmap that flags which of the 128 possible data elements are present, and then the data elements themselves in order.
This decoder identifies the MTI, expands both bitmaps, and lists every present field with its standard name. Field value parsing depends on each acquirer's data-element format table, so values are not split here — the focus is structure and which elements are declared.
The Message Type Indicator is the four-digit code at the start of the message — for example 0200 is an authorization request and 0210 its response.
Data-element formats vary by network and acquirer specification. The bitmap and field names are universal; reliably splitting values requires the specific format table.
See the ISO 8583 reference for MTI digits, common data elements, processing codes and response codes.
A six-digit field: the first two digits are the transaction type (00 purchase, 01 cash withdrawal, 20 refund, 30 balance inquiry), the next two the from-account type and the last two the to-account type (00 unspecified, 10 savings, 20 checking, 30 credit). Values vary by network and acquirer specification.
It is the issuer or host answer: 00 approved, 05 do not honor, 14 invalid card number, 51 insufficient funds, 91 issuer or switch unavailable. Networks add their own codes, so confirm against your specification.
Host message formats are part of every EMV Level 3 project. See our EMV Level 3 certification services →
We build and certify against acquirer and network specifications regularly. See platform integrations →