Decoder

ISO 8583 Bitmap Decoder

edit_note By the Paying.co engineering team · Updated August 6, 2026

Paste a primary or secondary bitmap in hex or binary and see which of the 128 data elements it declares. You can also go the other way and build a bitmap from a list of field numbers.

Quick answer

What is an ISO 8583 bitmap? The bitmap is a 64-bit field after the MTI where each bit marks whether the matching data element is present. A 1 means present. If bit 1 is set, a second 64-bit bitmap covers fields 65 to 128.

ISO 8583 bitmap16 or 32 hex characters, or 64 or 128 bits
Build a bitmap from field numberscomma or space separated

How an ISO 8583 bitmap works

The bitmap is the table of contents of an ISO 8583 message. After the four-digit MTI comes a 64-bit primary bitmap, usually written as 16 hex characters. Each bit stands for one data element: bit 1 is field 1, bit 2 is field 2, and so on up to field 64. A bit set to 1 means that field is present in the message body. A bit set to 0 means it is absent.

The secondary bitmap

Bit 1 of the primary bitmap is special. When it is 1, a second 64-bit bitmap follows and covers fields 65 to 128. That is why a bitmap that begins with 8 or higher in its first hex character usually means a 32-character bitmap. Some networks also define a tertiary bitmap for fields 129 to 192.

Worked example

Take the primary bitmap 7234000000000000. The first hex digit 7 is binary 0111, so fields 2, 3 and 4 are present and field 1 is not. The next digit 2 is 0010, so field 7 is present. The digit 3 is 0011, so fields 11 and 12 are present, and the digit 4 is 0100, so field 14 is present. The message therefore carries fields 2, 3, 4, 7, 11, 12 and 14 and nothing else.

Hex versus binary bitmaps

Some systems send the bitmap as 16 hex characters. Others send it as 8 raw bytes, which you will see as 16 hex characters in a log dump. Paste either form here. You can also paste 64 or 128 characters of 0 and 1.

Building a bitmap

The builder runs the other way. List the field numbers your message will carry and it returns the bitmap in hex, setting bit 1 automatically when a field above 64 is used. This is useful when you write a test message by hand or compare a host's expected fields to what your terminal sends.

To decode a whole message, with the MTI and the bitmap together, use the ISO 8583 decoder. For field names, processing codes and response codes, see the ISO 8583 reference.

Frequently asked questions

What is a bitmap in ISO 8583?

The bitmap is a 64-bit field after the MTI in which each bit marks whether the matching data element is present in the message. A 1 means present and a 0 means absent.

How do I decode an ISO 8583 bitmap?

Convert the hex string to binary, then read the bits from left to right. Bit position 1 is field 1, position 2 is field 2, and so on. Every position that holds a 1 is a field that appears in the message.

What does the first bit of the bitmap mean?

Bit 1 says whether a secondary bitmap follows. When it is set, a second 64-bit bitmap covers fields 65 to 128, and the message carries 32 hex characters of bitmap instead of 16.

How long is an ISO 8583 bitmap?

The primary bitmap is 64 bits, which is 16 hex characters or 8 bytes. With a secondary bitmap it is 128 bits, which is 32 hex characters or 16 bytes.

Can I build a bitmap from a list of fields?

Yes. Enter the field numbers in the builder, for example 2, 3, 4, 11, 12, 41, and it returns the bitmap in hex.

Is the bitmap ever sent in binary?

Yes. Some implementations send the bitmap as 8 raw bytes, while others send it as 16 hex characters. A raw dump shows the same value in hex, so you can paste it here either way.

Going through EMV certification?

Host message formats and EMV data are part of every EMV Level 3 project. See our EMV Level 3 certification services →

Building a payment app that has to pass EMV Level 3?

Foundry is our reusable EMV Level 3 framework: one native core, cast once per processor, so you reuse certified work instead of starting over. See Foundry →

Running terminals or kiosks in the field?

Castum is our Android MDM for kiosks and payment devices. Enroll, lock down and update your fleet from $1.25 per device per month. See Castum →

lock Everything runs in your browser. Nothing you paste is transmitted to a server.