JA Technology Solutions
SWIFT MT Explorer
Parse SWIFT MT financial messages (MT103, MT940, MT700). Block structure, field lookup, and transaction tables.
SWIFT MT Explorer
Parse SWIFT MT financial messages used in international banking. Supports MT103 (wire transfers), MT202 (financial institution transfers), MT940 (account statements), MT700 (letters of credit), and more. Messages are decoded by block — basic header, application header, user header, text body, and trailer — with each field shown by tag number, name, and value. MT type detection labels every field according to the type-specific SWIFT specification, and multi-line fields like beneficiary addresses and remittance info are formatted for readability. Export parsed fields to CSV or Excel for compliance review and payment reconciliation. Everything runs in your browser — your payment messages never leave your machine.
Learn more ↓
Loading interactive explorer...
What Are SWIFT MT Messages?
SWIFT (Society for Worldwide Interbank Financial Telecommunication) MT (Message Type) messages are the standard format for international financial messaging between banks. Each message is identified by a three-digit type number: the first digit indicates the category (1 = customer transfers, 2 = financial institution transfers, 7 = documentary credits, 9 = cash management), and the remaining digits specify the exact message type. Messages are structured into five blocks: Basic Header (Block 1), Application Header (Block 2), User Header (Block 3), Text Block (Block 4) containing the business content with tagged fields, and Trailer (Block 5) with authentication data.
Common SWIFT Message Types
The most frequently encountered types include MT103 (single customer credit transfer — the standard international wire), MT940 (customer statement, similar to BAI2 but for international banks), MT700 (issue of a documentary credit / letter of credit), MT202 (bank-to-bank transfer), and MT199/MT299 (free-format messages). Each type has specific required and optional fields identified by tags like :32A: (value date, currency, and amount), :50K: (ordering customer), and :59: (beneficiary). Reading raw SWIFT messages requires knowing which fields each message type expects — this tool parses the block structure and labels every field.
International Payment Integration
Organizations processing international payments need to parse, validate, and route SWIFT messages as part of their treasury and compliance workflows. I build integrations that ingest SWIFT messages from banking channels, extract transaction details, match against expected payments, flag compliance exceptions, and feed data into ERP and treasury management systems. For related financial message formats, see the ISO 8583 Explorer for card transaction messages and the OFX/QFX Explorer for bank statement files. Whether you are building a new payment processing pipeline or troubleshooting an existing SWIFT interface, learn about integration services or get in touch to discuss your requirements.
All tools run entirely in your browser. Your data never leaves your machine. Need help? Ask James.