Last reviewed: · Curated by Ohmyfin Organisation editorial.
pacs.008 (FIToFICustomerCreditTransfer) is the ISO 20022 XML message used to instruct a customer credit transfer between two banks. It is the modern replacement for the legacy SWIFT MT103. Draft a pacs.008 now → · Translate MT103 → pacs.008 →
pacs.008 carries far more structured data than an MT103. Where the MT103 uses free-format field 50K for the ordering customer (up to 4 lines × 35 characters), pacs.008 carries a fully structured Dbtr (Debtor) element with separate child elements for legal name, structured postal address (building number, street, post code, city, country), LEI (Legal Entity Identifier), and national registration code. This structured data enables straight-through sanctions screening and automated compliance — no human interpretation required. The same richness applies to the beneficiary, ultimate debtor, ultimate creditor, and every correspondent in the chain.
The pacs.008 message structure follows the ISO 20022 XML envelope. The Business Application Header (AppHdr / BAH) identifies the sender and receiver BICs, the message name (e.g. pacs.008.001.09), creation date-time and business message identifier. The core payload FIToFICstmrCdtTrf contains: GrpHdr (GroupHeader) with message ID, creation date-time, number of transactions, settlement date, interbank settlement amount, and settlement method; and one or more CdtTrfTxInf (CreditTransferTransactionInformation) elements carrying the UETR, end-to-end ID, instruction ID, interbank settlement amount, charge bearer, ordering customer, ordering institution, intermediary agents, creditor agent, creditor, and rich remittance information.
On the SWIFT network, ISO 20022 pacs.008 and MT103 coexisted under the SWIFT CBPR+ (Cross-Border Payments and Reporting Plus) programme from March 2023 to November 2025. During that period SWIFT's in-network translation service automatically converted MT103 to pacs.008 and vice versa, so banks that had not yet migrated could still exchange payments with fully ISO 20022-native banks. After November 2025, all new cross-border SWIFT customer credit transfers must originate as pacs.008.
A pacs.008 message contains the same UETR as the equivalent MT103 in the UETR sub-element of CdtTrfTxInf. Ohmyfin tracks both message types interchangeably by UETR — if your payment started as an MT103 and was translated to pacs.008 mid-chain, the UETR remains constant throughout and Ohmyfin returns the live GPI status regardless of which format the current-holding bank uses.
The ISO 20022 remittance information block in pacs.008 is dramatically richer than MT103 field 70. The RmtInf element supports both unstructured text (up to 140 characters) and a fully structured variant with creditor reference type, reference number, debtor reference, and even a URL pointing to an invoice document. This enables fully automated invoice reconciliation at the beneficiary's accounting system without manual matching. SEPA Credit Transfer (SCT) and SEPA Instant Credit Transfer (SCT Inst) are both implemented as pacs.008-derived messages in the EPC scheme rulebooks.
Yes. Ohmyfin tracks payments by UETR regardless of whether the underlying message is MT103 or pacs.008. If the UETR is the same in both messages (which it always is), Ohmyfin returns the unified tracking status.
pacs.008 is an XML message (ISO 20022 standard) with fully structured data elements — separate XML fields for every piece of sender and receiver information. MT103 is a fixed-format text message (SWIFT MT standard) with numbered fields and mostly free-format text. pacs.008 carries much richer data, enabling straight-through automation and better compliance screening.
The SWIFT CBPR+ migration required all new cross-border customer credit transfers to be originated as pacs.008 from November 2025. The coexistence period (March 2023 to November 2025) allowed MT103 and pacs.008 to run in parallel with automatic in-network translation.
CBPR+ stands for Cross-Border Payments and Reporting Plus — the SWIFT programme name for the mandatory migration of correspondent banking message traffic from MT to ISO 20022 (pacs.008, pacs.009, pacs.002, camt.053, etc.).
They are closely related. SEPA Credit Transfer (SCT) and SEPA Instant Credit Transfer (SCT Inst) use a SEPA-flavoured subset of pacs.008, defined in the EPC's scheme rulebooks. The message structure is the same ISO 20022 pacs.008 schema, but with EPC-specific validations and mandatory elements.
Yes — use the Ohmyfin pacs.008 drafter at /draft/pacs008. You can also translate an existing MT103 to a valid pacs.008 at /draft/mt-to-mx.
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 →