Convert a SWIFT MT103 payment to ISO 20022 pacs.008 - locally in the browser, with no upload; the payment data never leaves your device.
Running locally on your device ...
Running locally on your device ...
0%
Your files never left your device
No. Everything runs in your browser - your file never leaves your device. How this is verifiable
MT103 is the classic SWIFT FIN message for a single customer credit transfer: a line-based format with tags like :20: (reference), :32A: (value date, currency and amount), :50a: (ordering customer), :59a: (beneficiary), :70: (remittance) and :71A: (charges). Global payments are migrating to ISO 20022; the structured XML counterpart of an interbank transfer is pacs.008 (pacs.008.001.08, FIToFICustomerCreditTransfer).
Drop your MT103 file; the tool reads the tags and builds a pacs.008 XML with the amount and value date, ordering customer and beneficiary (name plus IBAN/account and address lines where present), the routing BICs of the banks involved (whenever the message carries them), remittance and the charges bearer (SHA/OUR/BEN -> SHAR/DEBT/CRED). You can drop several files at once, each becomes its own pacs.008. Everything runs entirely locally in the browser - pure JavaScript, no server, no foreign library from a foreign CDN.
Honest about the MT-to-MX switch: the mapping is still not lossless, but less is lost than before. The ordering customer and beneficiary now carry over with name, account, up to four address lines and - for a BIC-only party (Option A) - the bank's BIC instead of a wrong name; when :52A:/:53A:/:56A:/:57A: are present in the message, the routing BICs of the banks involved (ordering, intermediary and beneficiary bank) are carried over too. What is actually lost: more than four address lines per party, a structured split of the address into street, town and postcode (the address stays as free-text lines) and SWIFT X charset characters that do not map onto the pacs fields - that is a property of the format switch, not a fault of the tool.
| Input formats | MT103, TXT, FIN |
|---|---|
| Auto-conversion | PNG, JPG, WebP, GIF, BMP, TIFF, ICO, SVG, HEIC, PDF, MP3, WAV, DOCX, MIDI, DDS, HDR, PCX, WBMP |
| Output format | XML |
| Batch processing | Yes |
| Processing | Locally in your browser (JavaScript) |
| File upload | None |
Limitations: Converts a SWIFT MT103 single customer credit transfer to ISO 20022 pacs.008 (pacs.008.001.08, FIToFICustomerCreditTransfer): amount and currency (:32A:), value date, ordering customer (:50a:) and beneficiary (:59a:) with name, IBAN/account and up to four address lines (or a BIC for a BIC-only party), the routing BICs of the banks involved (:52A:/:53A:/:56A:/:57A:, where present), remittance (:70:) and the charges bearer (:71A: SHA/OUR/BEN). The MT-to-MX mapping is still NOT lossless: more than four address lines per party, a structured address split (street/town/postcode instead of free-text lines) and SWIFT X charset characters do not map onto the pacs fields. The value date (:32A:) uses a two-digit year (YYMMDD); following common SWIFT practice, 00-79 is read as 20xx and 80-99 as 19xx - for a legacy message with a value date before 1980 this can resolve to the wrong century. It is a format conversion for data exchange and not a payment trigger; verify the result against a bank-specific schema with your software.
No. Reading the MT103 and building the pacs.008 run entirely locally in the browser (pure JavaScript, no server); the payment never leaves your device.
ISO 20022 pacs.008.001.08 (FIToFICustomerCreditTransfer) with one credit-transfer transaction from the MT103.
No, but more survives than before: name, account, up to four address lines, BIC-only parties and - where present - the routing BICs of the banks involved are carried over. What is lost is any further address lines, a structured address split and SWIFT X charset characters. That is a property of the MT-to-MX switch.
No. It is purely a format conversion MT103 -> pacs.008 for data exchange; it does not trigger a payment.
Yes. Drop several MT103 files at once; each becomes its own pacs.008 XML.
Yes, whenever the MT103 message carries them: the ordering institution (:52A:), the sender's correspondent (:53A:), the intermediary institution (:56A:) and the beneficiary's account-with institution (:57A:) are carried into the pacs.008 as routing BICs (DbtrAgt/IntrmyAgt1/IntrmyAgt2/CdtrAgt).
MT940 to camt.053 · Bank statement to CSV · CSV to JSON · NF-e Viewer (Brazil)