Last reviewed: · Curated by Ohmyfin Organisation editorial.
MT103 and pacs.008 carry the same thing — a single customer credit transfer — in two different formats. MT103 is the legacy fixed-field SWIFT MT message; pacs.008 is the ISO 20022 XML successor. Track either type free by UETR →
MT103 was designed in the 1990s for telex-era bank messaging: fixed positional fields, short character limits, and no structured data beyond a few mandatory codes. The remittance information in field 70 is limited to four lines of 35 characters (140 characters total) — barely enough for an invoice number. The beneficiary address in field 59 is free text with no structure. The ordering customer in field 50 has similar limitations.
pacs.008 (FIToFICustomerCreditTransfer, ISO 20022) was designed for the data needs of modern compliance, analytics and automation. Remittance information in pacs.008 can carry structured invoice references, tax IDs, payment purpose codes and URLs to actual invoice documents — with virtually no length limit on the unstructured narrative. Addresses are fully structured (street, building, city, postal code, country separately). Legal Entity Identifiers (LEI) can be included for corporate parties. Purpose-of-payment codes and regulatory reporting fields have dedicated XML elements.
Data depth practical impact: because pacs.008 carries structured beneficiary data, correspondent banks can automatically pass AML/KYC checks without manual intervention. This means fewer sanctions screening holds, faster STP (straight-through processing), and lower per-payment compliance costs for the bank chain. MT103's unstructured data means AML systems must perform fuzzy name-matching on free text, which generates more false positives and holds.
Migration timeline: SWIFT began the CBPR+ (Cross-Border Payments and Reporting Plus) migration from MT to ISO 20022 in March 2023. The full coexistence period ends November 2025, after which new cross-border SWIFT payments must be originated as pacs.008. During the coexistence period, SWIFT translates between MT and MX automatically so senders on MT can still reach receivers on pacs.008 and vice versa.
Tracking: both MT103 and pacs.008 carry the same 36-character UETR — in field 121 of the MT103 block 3, and in the UETR element of the pacs.008 GrpHdr block. Ohmyfin tracks both formats interchangeably via UETR. Whether your bank sent an MT103 or pacs.008 makes no difference to the tracking lookup at ohmyfin.org.
| MT103 | pacs.008 | |
|---|---|---|
| Standard | SWIFT MT (legacy) | ISO 20022 (modern) |
| Format | Fixed positional fields | Structured XML |
| Remittance info | Field 70: 4×35 chars | Up to 9,000 chars structured |
| Address data | Free text | Structured (street, city, country) |
| UETR | Field 121 (mandatory) | UETR element (mandatory) |
| Cut-over deadline | Phasing out by Nov 2025 | Mandatory after Nov 2025 |
| LEI support | No | Yes |
For SWIFT cross-border CBPR+ traffic, yes — November 2025 is the deadline after which new originations must be pacs.008. Domestic MT traffic (used within some local markets) continues on its own local migration timelines, which vary by country.
Security on both formats is managed by the SWIFT network and each bank's own controls. The key difference is data quality: pacs.008's structured fields give AML/sanctions systems more precise data, reducing false positives and making it harder for bad actors to hide behind ambiguous name spellings in free-text fields.
No — as an individual or business sender, you do not need to know. Your bank's online form is the same; the backend handles the format. What matters for you is the UETR (the 36-character tracking code), which works identically for both formats on Ohmyfin.
pacs.008 adds: structured postal addresses (street, city, postal code, country separately), Legal Entity Identifiers (LEI), purpose-of-payment codes, unlimited structured remittance information (ISO 11649 reference, invoice numbers, structured creditor references), ultimate debtor/creditor fields, and regulatory reporting elements. MT103 has none of these.
Ask your bank for the payment confirmation and check whether it shows an MT103 message structure (with field 20, 32A, 50, 57, 59, 70, 71A, 121) or an XML pacs.008 structure. For tracking purposes, it makes no difference — just paste the UETR into Ohmyfin.
No card needed. Free for ordinary users — completely free for individuals — no daily limit, no card required. Track any international wire across 11,000+ banks.
Track a payment now — completely free Or try the tracker now →