ISO 8583 reference: message structure, MTI, bitmaps and fields

What ISO 8583 is

ISO 8583 is the international standard that defines the message format used by card-based payment systems. Published by ISO/TC 68 (financial services), it describes how terminals, acquirers, payment networks and issuers exchange authorizations, financial transactions, reversals, file updates, reconciliation and network management between each other. Virtually every card rail — including VISA, Mastercard, American Express, JCB, Discover, UPI as well as most domestic schemes — relies on an ISO 8583 dialect.

The spec does not mandate a transport (it is commonly carried over TCP, X.25 in legacy deployments, or HTTP tunnels) and does not impose a single character encoding. A single byte sequence can therefore be interpreted differently depending on the scheme profile (VISA BASE I / BASE II, Mastercard IPM / MIP) and the acquirer configuration.

Versions of the standard

ISO 8583:1987

The original release. Defines the MTI, primary and secondary bitmaps and 128 data elements. This is by far the most deployed version on production payment rails — most VISA and Mastercard traffic is still 1987-compatible.

ISO 8583:1993

Restructures some data elements, adds clarifications around file actions (class 3xx) and network management (class 8xx), and tightens the semantics of the repeat indicators. Many schemes adopted cherry-picked 1993 features while keeping the 1987 skeleton.

ISO 8583:2003

A structural modernization, notably widening several fields and updating cryptographic references. Rarely used end-to-end in card payments: the industry largely froze on 1987/1993-compatible profiles.

Message anatomy

Every ISO 8583 frame is a concatenation of the following blocks, in this order:

1. Optional header — scheme- or carrier-specific (for example, VISA’s BASE I header, or an ISO network-management prefix). Not part of the ISO standard itself.
2. MTI — four digits identifying the message. See MTI.
3. Primary bitmap — 64 bits (8 bytes binary, or 16 hex characters when encoded as ASCII hex) indicating which of data elements 1 through 64 are present.
4. Secondary bitmap — present when bit 1 of the primary bitmap is set; covers data elements 65 through 128.
5. Data elements — concatenated in ascending order of their field number. Fixed-length fields consume exactly their declared length; variable-length fields (LLVAR, LLLVAR) start with a 2- or 3-digit length indicator.

Common encodings on the wire include pure binary, BCD (two digits per byte), ASCII and EBCDIC. A single message can mix encodings: for instance, the MTI may be BCD while the PAN (field 2) is ASCII digits.

Message Type Indicator (MTI)

The MTI is a four-digit code sitting at the very start of the ISO 8583 payload (after any carrier header). Each digit encodes one facet of the message.

Common MTI values

Bitmaps

A bitmap is a fixed-width binary map that declares which data elements are present in the message. The primary bitmap is 64 bits wide and covers fields 1 to 64: each bit set to 1 means the corresponding field is present, each bit set to 0 means it is absent.

Bit 1 of the primary bitmap is special: when set, it signals that a secondary bitmap — another 64 bits — follows immediately and covers fields 65 to 128. That is why the Bitmap itself is declared as data element 1 in the field table below.

Example. A primary bitmap of 7234054128C08000 (hex) decodes as binary 0111 0010 0011 0100 0000 0101 0100 0001 0010 1000 1100 0000 1000 0000 0000 0000, which means the following fields are present: 2, 3, 4, 7, 11, 12, 14, 22, 24, 26, 32, 35, 37, 41, 42, 49. Bit 1 is 0, so no secondary bitmap follows.

The ISO standard also defines a tertiary bitmap carried in field 65 when even finer field ranges are needed, but it is extremely rare on card rails.

Data elements (fields 1–128)

The base ISO 8583 field catalog. Individual schemes and acquirers can — and do — override lengths, tighten formats or attach private meaning to the reserved fields (48, 62, 63, 120–127). Always consult the scheme-specific specification before relying on a wire definition in production.

Format abbreviations

VISA vs Mastercard specifics

Both VISA and Mastercard inherit the ISO 8583 skeleton but layer their own semantics on top of it.

• VISA runs the BASE I (authorization) and BASE II (clearing) profiles over VIP. Private fields — especially 48, 62 and 63 — carry VISA-proprietary subfields. Lengths for certain fields are tightened (for example field 22 — POS entry mode — and field 44 — additional response data).
• Mastercard uses the IPM (Integrated Product Message) format for clearing and MIP for the network transport layer. Mastercard makes heavy use of PDS (Private Data Subelements) packed inside fields 48, 124 and 127, each with its own tag/length/value encoding.

Because the two schemes disagree on the format of several private and national fields, the same raw bytes can decode cleanly under one profile and break alignment under the other. That is exactly what ISOParser highlights: paste your message into the parser and compare the VISA and Mastercard interpretations side by side.

References

• Wikipedia — ISO 8583 (general overview, field catalog).
• ISO catalogue — ISO 8583-1:2003 (official, paid).