Cashless Nomad

If you’ve ever worked with payment processing, you’ve probably encountered ISO-8583. It’s the standard used by financial institutions for electronic transactions, and understanding it is key to working on POS systems, ATMs, and payment gateways.

One of the trickiest parts? BITMAPS. If you’ve ever stared at a HEX dump of an ISO-8583 message, wondering what those bits mean, you’re not alone. I’ve been there. So let’s break it down in a way that actually makes sense.

What is a BITMAP in ISO-8583?

A BITMAP is a 64-bit (or sometimes 128-bit) field that indicates which data elements (DEs) are present in a message. It acts like a checklist: a bit set to 1 means that a corresponding data element is included in the message, while a bit set to 0 means it’s not.

Imagine you’re at a restaurant, and the waiter gives you a menu. Instead of writing down the full names of the items you want, you just mark checkboxes next to them. That’s what a BITMAP does.

Example: A Simple ISO-8583 Message

Let’s take a basic financial transaction request (DE 0 = 0200) and break it down:

0200 723A00010AC08012 0000000000001234 123456789012345

• 0200 → Message Type Indicator (MTI)
• 723A00010AC08012 → Primary BITMAP (we’ll decode this next)
• 0000000000001234 → Data Element 4 (Transaction Amount: 12.34)
• 123456789012345 → Data Element 2 (Primary Account Number / Card Number)

Now, let’s focus on the BITMAP: 723A00010AC08012

Breaking Down a BITMAP

Step 1: Convert HEX to Binary

BITMAPs are stored in HEX format, but we need them in binary to understand which DEs are included.

723A00010AC08012 → 0111001000111010000000000000000100001010110000001000000000000001

Step 2: Read Each Bit (1 = Present, 0 = Absent)

Each bit corresponds to a Data Element:

So from this BITMAP, Data Elements 1, 2, 4, and 64 are included in the message.

Decoding BITMAP in Code

Let’s write some simple C# code to decode an ISO-8583 BITMAP.

using System;

class Program
{
    static void Main()
    {
        string hexBitmap = "723A00010AC08012";
        string binaryBitmap = HexToBinary(hexBitmap);
        
        Console.WriteLine("Binary Representation: " + binaryBitmap);
        
        for (int i = 0; i < binaryBitmap.Length; i++)
        {
            if (binaryBitmap[i] == '1')
            {
                Console.WriteLine("Data Element " + (i + 1) + " is present.");
            }
        }
    }

    static string HexToBinary(string hex)
    {
        return string.Join("", hex.Select(c => Convert.ToString(Convert.ToInt32(c.ToString(), 16), 2).PadLeft(4, '0')));
    }
}

Output:

Binary Representation: 0111001000111010000000000000000100001010110000001000000000000001
Data Element 1 is present.
Data Element 2 is present.
Data Element 4 is present.
Data Element 64 is present.

This small script helps you quickly determine which Data Elements are part of an ISO-8583 message.

64-bit vs 128-bit BITMAPS

• 64-bit BITMAP: Standard ISO-8583 messages use a single BITMAP (8 bytes).
• 128-bit BITMAP: If the first bit of the first BITMAP is 1, it means there’s a second BITMAP (extended fields, DE 65–128).

Example of a 128-bit BITMAP

F23A00010AC08012 A000000000000000

• First BITMAP starts with F (binary 1111) → Indicates presence of a second BITMAP.
• Second BITMAP follows, defining DEs from 65 to 128.

Real-World Application

In one of my projects, we were integrating with multiple acquiring banks, each with its own ISO-8583 implementation. Some banks used proprietary extensions, meaning their BITMAPs didn’t always conform to the standard.

One of the biggest headaches? Debugging failed transactions.

1. We received an ISO-8583 response but weren’t sure why our parser failed.
2. After checking the BITMAP, we realized the acquirer sent a 128-bit BITMAP but our system only expected 64-bit.
3. The quick fix? Modify our parsing logic to detect a secondary BITMAP dynamically.

Lesson learned: Always check the first bit of the BITMAP before assuming it’s just 64 bits.

BITMAPs might seem intimidating, but once you break them down, they’re just binary flags indicating which fields are included in an ISO-8583 message.

• Convert HEX to Binary to analyze the BITMAP.
• Each bit corresponds to a Data Element.
• The first bit of the BITMAP tells you if there’s a second BITMAP.
• Automate BITMAP parsing to avoid headaches when integrating with different payment processors.

Understanding BITMAPs is crucial for troubleshooting, debugging, and designing better payment applications. Next time you look at an ISO-8583 message, you’ll know exactly how to decipher what’s inside.