GLOBAL PAYMENTS KNOWLEDGEISO 20022 / SWIFT / SEPA / MT / MX
PAYMENTSSIGNAL

The interactive academy for the standards, messages, and rails that move money.

GET IN TOUCH
FOLLOW THE PAYMENT

CBPR+ cross-border transfer (pacs.008)

A cross-border customer credit transfer in ISO 20022 under CBPR+ usage guidelines, tracked end to end by its UETR.

Reference card →
Your notes

Contributor Shubham Mathure

STEP 1 / 9MESSAGE

The debtor initiates the cross-border payment

Debtor (payer) → Bank Alfa (debtor agent) · pain.001

A corporate treasury sends a pain.001 with structured party and remittance data — the structure survives the whole journey because every hop speaks ISO 20022.

Step 1 of 9: The debtor initiates the cross-border payment

  1. 01Message
    The debtor initiates the cross-border paymentDebtor (payer) → Bank Alfa (debtor agent) · pain.001
  2. 02Processing
    Bank Alfa validates, screens, and debitsBank Alfa (debtor agent)
  3. 03Message
    The pacs.008 leaves with a BAH and UETRBank Alfa (debtor agent) → Meridian Bank (intermediary agent) · pacs.008
  4. 04Processing
    Meridian screens in the middle of the chainMeridian Bank (intermediary agent)
  5. 05Settlement
    The correspondent settles across its booksMeridian Bank (intermediary agent)
  6. 06Message
    The pacs.008 continues to the creditor agentMeridian Bank (intermediary agent) → Cassia Bank (creditor agent) · pacs.008
  7. 07Processing
    Cassia validates the incoming paymentCassia Bank (creditor agent)
  8. 08Posting
    The creditor is creditedCassia Bank (creditor agent)
  9. 09Message
    A confirmation closes the loopCassia Bank (creditor agent) → Bank Alfa (debtor agent) · pacs.002
MESSAGECLEARING OBLIGATIONSETTLEMENTPOSTING
Full step-by-step text (works without JavaScript)
  1. 01Message
    The debtor initiates the cross-border paymentDebtor (payer) → Bank Alfa (debtor agent) · pain.001

    A corporate treasury sends a pain.001 with structured party and remittance data — the structure survives the whole journey because every hop speaks ISO 20022.

  2. 02Processing
    Bank Alfa validates, screens, and debitsBank Alfa (debtor agent)

    Checks and screening run on rich, structured fields — one of ISO 20022's main gains. The customer account is debited on acceptance.

    • DR Debtor's account at Bank Alfa — USD 1,250,000.00

    Screening checkpoint: Outbound screening on structured data — Structured names and addresses screen more precisely than free-text lines, cutting false positives.

  3. 03Message
    The pacs.008 leaves with a BAH and UETRBank Alfa (debtor agent) → Meridian Bank (intermediary agent) · pacs.008

    The interbank message travels with a Business Application Header and a UETR — the end-to-end reference every bank keeps unchanged, making the payment trackable.

  4. 04Processing
    Meridian screens in the middle of the chainMeridian Bank (intermediary agent)

    The intermediary agent screens the structured parties and checks cover on Bank Alfa's account.

  5. 05Settlement
    The correspondent settles across its booksMeridian Bank (intermediary agent)

    Settlement is a book transfer between the two banks' USD accounts at Meridian — same mechanics as the MT world; the message standard changed, the money movement did not.

    • DR Bank Alfa's USD account at Meridian (vostro) — USD 1,250,000.00
    • CR Cassia's USD account at Meridian (vostro) — USD 1,250,000.00
  6. 06Message
    The pacs.008 continues to the creditor agentMeridian Bank (intermediary agent) → Cassia Bank (creditor agent) · pacs.008

    The same UETR arrives at Cassia; anyone with the reference can see where the payment is in the chain.

  7. 07Processing
    Cassia validates the incoming paymentCassia Bank (creditor agent)

    Inbound screening and account checks before the credit is applied.

  8. 08Posting
    The creditor is creditedCassia Bank (creditor agent)

    The structured remittance information lets the creditor reconcile the invoice automatically.

    • CR Creditor's account at Cassia — USD 1,250,000.00
  9. 09Message
    A confirmation closes the loopCassia Bank (creditor agent) → Bank Alfa (debtor agent) · pacs.002

    A status confirmation tells the debtor agent the payment completed — the debtor can be told with certainty rather than silence.

What this simplifies: One intermediary agent and a single settlement venue. Investigation messages are shown generically; specific case-management message choreography varies by corridor and era.

LEARN THE CONCEPTS BEHIND THIS FLOW

Sources for this flow3
  1. Official requirement

    Cross-Border Payments and Reporting Plus (CBPR+) usage guidelines ↗ — Swift (CBPR+ working group)

    Defines how ISO 20022 messages (including pacs.008, pacs.009, pacs.002, pacs.004, and camt investigation messages) are used and validated for cross-border payments on the Swift network. · Checked 2026-07-12

    Full guidelines require MyStandards access; content here relies on public summaries. MT-to-CBPR+ translation rules are published on Swift's translation portal.

  2. Market practice

    ISO 20022 Standards (Swift ISO 20022 adoption programme) ↗ — Swift

    Describes the Swift community's adoption of ISO 20022 for cross-border payments and reporting, including the CBPR+ migration and the end of MT-MX coexistence. · Checked 2026-07-12

    Programme milestones change over time; the coexistence period for in-scope cross-border payment instructions ended in November 2025. Check swift.com for the current timeline.

  3. Simplified educational illustration

    Payments Signal editorial teaching models — Payments Signal

    This site's own simplified teaching models. · Checked 2026-07-12

    What this simplifies: One intermediary; investigation exchanges are shown generically rather than as specific case-management message types.

    Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.