ISO 8583 Message Parser

ISO 8583 is the international standard for financial transaction messages. Every time you tap a card at a POS terminal, withdraw cash from an ATM, or pay online, an ISO 8583 message travels between the terminal, the acquirer, the network, and the issuer. Understanding this format is essential for payment switch engineers, QA engineers testing payment systems, and anyone debugging transaction failures in a production payment infrastructure.

Message structure

An ISO 8583 message has three parts:

1. **MTI (Message Type Indicator)**: 4 digits that identify the message version, class, function, and originator. Example: 0200 = financial transaction request (0 = 1987 version, 2 = financial message, 0 = request, 0 = acquirer-initiated). 2. **Bitmap**: 8 bytes (primary) or 16 bytes (primary + secondary). Each bit corresponds to a data element (DE). A set bit means that DE is present. 3. **Data elements**: The actual fields — card number (DE 2), processing code (DE 3), amount (DE 4), datetime (DE 7), etc.

DE encoding types

ISO 8583 uses several encoding types for DEs: - `a` (alphabetic), `n` (numeric), `an` (alphanumeric), `ans` (any printable character) - Fixed length (`LL`) or variable length (`LLVAR`, `LLLVAR`) where the prefix encodes the value length

Version differences

The three ISO 8583 versions differ in DE definitions and encoding for some fields. Version 1993 extended the original 1987 standard with additional fields. Version 2003 introduced a significantly different structure. This tool supports all three — select the version matching your spec before parsing.

Practical use

Paste a hex-encoded message to see each DE decoded with its field number, name, length, and value. This is invaluable when comparing request/response pairs, debugging missing fields that cause decline codes, or onboarding a new payment switch integration.