Parse Validate Convert ISO20022 ISO15022 SWIFT MT MX messages

Validate Request/response SWIFT MT MX messages on ISO20022 ISO15022 with variable formats and convert to JSON.


VALIDATE SWIFT MT MX - ISO20022 ISO15022 message

Paste the message ASCII content and press the Validate button.

ISO20022 ISO15022 SWIFT MT MX ascii data:


To protect against spam bots, only Logged in users can use this functionality.

Register Sign in

Decoding the Legacy — ISO 15022 (SWIFT MT)

ISO 15022 is a tag-based text format used primarily for securities and cash transfers (MT 5xx and MT 1xx series). It is governed by "Blocks" and "Sequences."

1. The Architecture

An MT message consists of five blocks. Most business logic resides in Block 4, which is delimited by {4: and -}.

Tags: 3-character codes (e.g., 20C, 98A).

Qualifiers: Distinguish the purpose of a tag (e.g., ::PREP for preparation date).

Sequences: Enclosed between :16R: (Start) and :16S: (End).

The Modern XML Standard — ISO 20022 (SWIFT MX)

ISO 20022 is the successor to MT, utilizing XML (eXtensible Markup Language). It is more verbose but offers significantly better data granularity and global standardization.

1. The Architecture

Instead of tags, MX messages use nested elements.

Group Header (GrpHdr): Metadata about the sender, receiver, and message ID.

Payment Information (PmtInf): The core instruction logic.

Namespaces: Crucial for distinguishing between different message versions (e.g., pain.001.001.03 vs pain.001.001.09).

2. The Implementation Snippet

Using SimpleXMLElement and XPath allows you to "jump" to the data you need without traversing the whole tree.

Converted ISO20022 ISO15022 SWIFT MT MX messages

Frequently Asked Questions

Which format is more secure?

Neither is inherently "more secure" at the data level, as security is usually handled by the transport layer (SWIFTNet). However, ISO 20022 reduces operational risk because it is less ambiguous—there is less "guessing" what a tag means.

Can I convert MT to MX automatically? Mostly, but it’s tricky. ISO 20022 allows for much longer fields (e.g., names and addresses). Converting MX → MT often results in "data truncation," where long names are cut off to fit the legacy 35-character limit.

Why do I see {1:...} in some XML messages? That is a SWIFT Wrapper. Sometimes SWIFT wraps an ISO 20022 XML message inside a legacy MT-style header for routing through older systems. Your parser should check for the {4: block and then see if the content inside is XML.

How do I handle large files? For massive files (e.g., daily camt.053 statements), SimpleXML might consume too much memory. Use XMLReader in PHP for "streaming" the file line-by-line.

  Related

Recent Articles on Iso20022