Messages & Fields
By Ohmyfin Organisation Editorial Team · Published 2026-03-24 · Updated 2026-05-22
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.
Payment Located
SWIFT GPI Network · Real-time status
Payment Not Found
No record found in SWIFT GPI or any correspondent banking data
Fraud Awareness Notice
If you received a payment document from a third party, verify directly with your own bank before releasing goods or funds. Fake MT103 / pacs.008 confirmations are widely used in advance-fee scams. See our fraud guide →
Monitor for 7 Days — Free
We re-check every few hours and notify you the instant this payment appears — no account, no spam.
Watching — we'll email you the moment it appears.
Not sure what to do next?
Ask SwiftMate, our SWIFT assistant, for guidance on payment delays, rejections, and next steps.
Payments can appear hours after initiation — try again later
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).
Key takeaways
pacs.008 = ISO 20022 XML successor to MT103.
Same payment, richer structured data, no free-text length limits.
UETR identical in both formats (field 121 ↔ GrpHdr/UETR).
MT retirement deadline: November 22, 2025.
Customer impact minimal — operations and compliance benefit most.
Frequently asked questions
Will my bank stop accepting MT103 after November 2025?
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.
Can Ohmyfin track pacs.008 payments?
Yes. The UETR is the same. Ohmyfin queries the GPI tracker which is format-agnostic.
Are there new charges with pacs.008?
No new SWIFT charges. Some banks charge an ISO 20022 readiness fee to corporate clients, but retail customers see no change.
Why is pacs.008 better for compliance?
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.
Payment Located
SWIFT GPI Network · Real-time status
Payment Not Found
No record found in SWIFT GPI or any correspondent banking data
Fraud Awareness Notice
If you received a payment document from a third party, verify directly with your own bank before releasing goods or funds. Fake MT103 / pacs.008 confirmations are widely used in advance-fee scams. See our fraud guide →
Monitor for 7 Days — Free
We re-check every few hours and notify you the instant this payment appears — no account, no spam.
Watching — we'll email you the moment it appears.
Not sure what to do next?
Ask SwiftMate, our SWIFT assistant, for guidance on payment delays, rejections, and next steps.
Payments can appear hours after initiation — try again later