Last reviewed: · Curated by Ohmyfin Organisation editorial.
pacs.008 (FIToFICustomerCreditTransfer) is the ISO 20022 XML message replacing the SWIFT MT103 for customer credit transfers worldwide. Draft a pacs.008 now → · Track by UETR free →
pacs.008 is defined under the ISO 20022 financial messaging standard and has the formal message name FIToFICustomerCreditTransfer. The XML schema is published by ISO TC68 and the SWIFT CBPR+ (Cross-Border Payments and Reporting Plus) working group publishes usage guidelines for international cross-border implementations. The main SWIFT CBPR+ pacs.008 schema is available at mystandards.swift.com.
Message structure: a pacs.008 document contains a GroupHeader block (GrpHdr) and one or more CreditTransferTransactionInformation blocks (CdtTrfTxInf). The GrpHdr holds the message ID, creation date-time, number of transactions, and the UETR. Each CdtTrfTxInf holds one payment instruction with the following key elements: PmtId (payment identification — InstrId assigned by the sender bank, and EndToEndId assigned by the originator), IntrBkSttlmAmt (settlement amount), IntrBkSttlmDt (settlement date), InstgAgt / InstdAgt (instructing and instructed agents — bank BICs), Dbtr (debtor — the sender), DbtrAcct (debtor account — IBAN or other account), DbtrAgt (debtor agent — sender's bank BIC), CdtrAgt (creditor agent — beneficiary bank BIC), Cdtr (creditor — the beneficiary), CdtrAcct (creditor account — IBAN or other account), RmtInf (remittance information — structured or unstructured).
UETR in pacs.008: the UETR appears in the GroupHeader block under the element path Document/FIToFICstmrCdtTrf/GrpHdr/PmtInstrXpryDtTm/../.. (specifically as UETRstring in the GrpHdr). It is a UUID v4 format (xxxxxxxx-xxxx-4xxx-xxxx-xxxxxxxxxxxx) — identical to the UETR in MT103 field 121. The same UETR is preserved through the full payment chain, and Ohmyfin tracks it regardless of whether the message is MT or MX.
Data richness vs MT103: pacs.008 structured remittance information (RmtInf/Strd) can contain Creditor Reference information (ISO 11649 structured creditor reference), invoice references, tax identification details and document dates. The unstructured remittance (RmtInf/Ustrd) allows a long free-text narrative. Addresses (postal address, PostalAddress) are fully structured with StreetName, BuildingNumber, PostCode, TownName, Country — far superior to the free-text field 59 on MT103. Purpose codes (Purp/Cd) from the ISO 20022 External Purpose Code list can indicate invoice, salary, intercompany loan, dividend, etc.
CBPR+ migration timeline: SWIFT began the CBPR+ migration from MT to ISO 20022 in March 2023. The original coexistence end date was November 2025, meaning that from that date all new cross-border SWIFT customer credit transfer originations should be in pacs.008. SWIFT's In-Flow Translation (IFT) service automatically translates messages between MT and MX formats during the coexistence period, so MT103-speaking banks can still receive pacs.008 and vice versa. After full migration, IFT will be discontinued.
Sanctions and compliance advantages: because pacs.008 carries structured names and addresses (not free-text like MT103), AML/sanctions-screening systems can run more precise name-matching. This reduces false positives — a major source of payment delays under MT103. Regulatory reporting fields in pacs.008 allow purpose codes and local-market identifiers to travel with the payment, eliminating the need for separate reporting messages in many jurisdictions.
Tracking pacs.008 on Ohmyfin: paste the UETR from your pacs.008 confirmation into the Ohmyfin tracker at ohmyfin.org. Ohmyfin queries the SWIFT GPI network and returns the live payment status (ACSP, ACCC, RJCT, etc.), the current holding bank, fees deducted, and the expected credit time — exactly the same as for MT103. The lookup is free for individuals.
Yes — Ohmyfin looks up payments by UETR regardless of whether the underlying message is MT103 or pacs.008. The UETR is identical in both formats and is the primary tracking key.
CBPR+ (Cross-Border Payments and Reporting Plus) is the SWIFT-managed programme to migrate international cross-border payments from the legacy MT message family (MT103, MT202, etc.) to ISO 20022 XML messages (pacs.008, pacs.009, camt.053, etc.). The migration ran from March 2023, with the coexistence period ending November 2025.
The UETR appears in the GroupHeader block (GrpHdr) of the pacs.008 message as a UETR element. It is a UUID v4 (xxxxxxxx-xxxx-4xxx-xxxx-xxxxxxxxxxxx) — the same format and value as the UETR in MT103 field 121. It travels unchanged through every bank in the chain.
pacs.008 adds: fully structured postal addresses (StreetName, BuildingNumber, PostCode, TownName, Country — separate XML fields); Legal Entity Identifier (LEI); ISO 20022 purpose codes (salary, dividend, invoice, etc.); ISO 11649 structured creditor reference; unlimited structured remittance information; ultimate debtor/creditor fields; and regulatory reporting identifiers for local market requirements.
Yes. pacs.008 structured fields allow AML/KYC systems to run precise name and address matching using dedicated fields, rather than fuzzy pattern-matching against free-text strings as required by MT103. This reduces false-positive compliance holds, speeds up STP rates, and makes it harder for bad actors to obscure identities through formatting tricks in free-text fields.
The SWIFT CBPR+ coexistence period ended November 2025. After that date, new cross-border SWIFT customer credit transfers must originate as pacs.008. SWIFT's In-Flow Translation service converted between formats during coexistence. Domestic market MT timelines vary by country (many national markets set their own later deadlines).
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 →