pacs.008 (FIToFICustomerCreditTransfer) is the ISO 20022 XML message replacing MT103 for cross-border credit transfers. The payment is the same; the wrapper changes from colon-prefixed FIN to structured XML. Here is what that means in practice.
Field 32A in MT103 (value date / currency / amount) becomes three structured elements in pacs.008: IntrBkSttlmDt, IntrBkSttlmAmt with Ccy attribute. Same data, more verbose, machine-parseable without ad-hoc regex.
Field 50K (ordering customer free text) becomes Dbtr / DbtrAcct with structured Nm, PstlAdr (postal address with country code, town, street). The 4×35 character free-text constraint disappears; addresses can be properly parsed.
Field 70 (remittance information) becomes RmtInf with a structured Strd block. You can now include invoice numbers, tax IDs, and reference codes as separate elements instead of one cramped free-text blob.
Field 121 (UETR) becomes UETR inside the GrpHdr. Same 36-character UUID, same semantics, just XML-wrapped.
The migration timeline: SWIFT began coexistence in March 2023. End of coexistence (MT cat 1/2/9 retirement) is November 22, 2025. From that date, cross-border payments are pacs.008 only on the SWIFT network — though many banks still translate to MT103 internally.
For senders the practical impact is minimal: your wire confirmation will look the same. The big winners are compliance teams (richer screening data), corporate ERPs (structured invoice references) and regulators (better reporting).
They will translate it. Most banks accept legacy MT103 from corporate ERPs and convert internally to pacs.008 for the SWIFT leg. The cross-border SWIFT message is pacs.008.
Yes. The UETR is the same. Ohmyfin queries the GPI tracker which is format-agnostic.
No new SWIFT charges. Some banks charge an ISO 20022 readiness fee to corporate clients, but retail customers see no change.
Structured address fields, structured remittance, and structured ultimate-debtor / ultimate-creditor elements let screening engines match against sanctions lists without false positives caused by free-text ambiguity.