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 ...
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 where present), 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 not lossless. The free-text party blocks (name plus unstructured address) and the SWIFT X character set cannot be fully mapped onto the structured pacs fields. The tool carries the name, account and remittance as best it can; whatever cannot be derived in a structured way (such as a parsed postal address or intermediary-bank details) is lost in this conversion - that is a property of the format switch, not a fault of the tool.
| Input formats | MT103, TXT, FIN |
|---|---|
| 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 and IBAN/account, remittance (:70:) and the charges bearer (:71A: SHA/OUR/BEN). The MT-to-MX mapping is NOT lossless: the free-text party blocks and the SWIFT X character set do not fully map onto the structured pacs fields; intermediary-bank details and parsed addresses are not carried over. 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. Free-text party blocks and the SWIFT X charset do not fully map onto pacs.008; name, account and remittance are carried best-effort. 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.