Payment message reference
Understand the message.
Read the bytes.
An independent ISO 8583 reference to message types and field formats used in open source implementations.
MTIMessage purposeBitmapFields presentDataEncoded values- 150
Message types
Read the version, purpose, function and origin of a message type listed in Moov’s implementation reference.
- 97
Data fields
Compare field containers in the pyiso8583 default and default_ascii starter profiles, including encoding, length prefixes and bitmap positions.
- Read
Bytes and encoding
Understand the difference between a value, its encoded bytes and the length prefix used to frame it.
Start with the connection profile
A message type describes an exchange. A field profile describes how to read its bytes. Neither tells you every value a particular processor accepts.
Use the source and profile shown on each page. This collection does not reproduce the ISO 2023 code tables or assign meanings to unsupported response and reason codes.
Source scope and interpretation
The prose mentions 2007 where its version table and examples use 2003. This reference uses the explicit example column and does not label it as the 2023 edition.
Some usage descriptions conflict with the digits. For example, the source labels 0320 as a request, while its function digit 2 denotes advice. Several response rows also describe a direction that conflicts with the request exchange. This reference explains the components and does not reuse those usage sentences or assert a universal direction of travel.
These are configurable starter profiles. Field labels, containers and lengths describe the selected profile, not a universal network contract or a complete code list.