MT ? MX
CBPR+ · ISO 20022
Engine ready — no data retained
SWIFT MT to ISO 20022 message conversion

MT to MX Converter

Convert SWIFT FIN (MT) messages to ISO 20022 (MX) and back, following CBPR+ mapping rules. Supports MT103 to pacs.008, MT202 to pacs.009, and MT192/292 to camt.056 — single message or batch file conversion.

Conversion direction
Source: MT103  ?  Target: pacs.008
Message pair
Processing mode
SWIFT release (DataPDU envelope)
saa:DataPDU envelope
? Single message conversion
Input — MT103
Output — pacs.008 (XML)
? Batch conversion
?
Drop your files here or click to browse
.txt · .mt · .fin · .mt103 · .xml — multiple files accepted

?? Files are deleted from the server immediately after conversion and download.

About the MT to MX Converter

This free online tool converts SWIFT MT financial messages to ISO 20022 MX format and back, following the CBPR+ (Cross-Border Payments and Reporting Plus) Usage Guidelines used during the SWIFT MT to MX migration. It supports the three most common message pairs used in cross-border payments: MT103 to pacs.008, MT202 to pacs.009, and MT192/292 to camt.056.

Whether you need to convert a single SWIFT MT103 message to a pacs.008.001.08 XML file for testing, validate a pacs.009 payment against its original MT202, or batch-convert dozens of legacy MT files ahead of a SWIFT CBPR+ migration deadline, this converter handles the field-by-field mapping — including postal addresses, charges (SHA/OUR/BEN), correspondent banks, and the SWIFT Alliance Access saa:DataPDU envelope for both SR2025 and SR2020 releases.

Frequently asked questions

How do I convert an MT103 message to ISO 20022 pacs.008?

Paste your MT103 SWIFT FIN message into the converter, select the MT103 ? pacs.008 pair and the MT ? MX direction, then click Transform. The tool maps every CBPR+ field — sender, receiver, amount, parties, charges — into the corresponding pacs.008.001.08 XML structure.

Can I convert ISO 20022 pacs.008 back to SWIFT MT103?

Yes. Select the MX ? MT direction and paste your pacs.008 XML, with or without the saa:DataPDU envelope. The converter rebuilds the MT103 fields, including postal addresses, charges, and the original Input/Output network direction when the SWIFT Alliance Access envelope is present.

What SWIFT MT to MX message pairs are supported?

MT103 ? pacs.008.001.08, MT202 ? pacs.009.001.08, and MT192/292 ? camt.056.001.08, in both directions, following CBPR+ Usage Guidelines.

Does the converter support SWIFT Alliance Access saa:DataPDU envelopes?

Yes. The tool can wrap generated MX messages in the saa:DataPDU envelope used by SWIFT Alliance Access, with correctly derived SenderReference, MessageIdentifier, DN, and RequestSubtype values for both SR2020 (swift.cbprplus.02) and SR2025 (swift.cbprplus.03) releases.

Is my data stored or shared?

No. Single-message conversions happen entirely in memory. For batch conversions, uploaded files are deleted from the server immediately after processing, and generated files are deleted right after download — nothing is retained.