Stopped for screening: a sanctions hold at the intermediary
Trigger: Meridian Bank's transaction screening flags a party name in the pacs.008 as a potential sanctions-list match.
What operations sees first: The payment goes quiet mid-route: tracking shows it reached the intermediary, but no onward leg and no confirmation follow.
WHERE IS THE MONEY?
Debited from the debtor at the start; suspended at the intermediary while the alert was open; with the creditor after release.
DID SETTLEMENT HAPPEN?
Paused mid-chain: no value moved beyond the intermediary until the hold was released, after which the remaining legs settled normally.
WHO ACTS NEXT?
Meridian Bank (intermediary agent) Bank Alfa notes the false-positive pattern; complete, structured party data in the pacs.008 — full names, addresses, identifiers — reduces repeat alerts on the same customer.
PLAY THE EXCEPTION
Trigger: Meridian's screening flags a potential name match against a sanctions list. The payment stops until an analyst decides.
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 10: The debtor initiates the cross-border payment
- 02ProcessingBank Alfa validates, screens, and debitsBank Alfa (debtor agent)
- 04ProcessingMeridian screens in the middle of the chainMeridian Bank (intermediary agent)
- 05 · EXCEPTION PATHProcessingThe payment is held in the screening queueMeridian Bank (intermediary agent)
- 08 · EXCEPTION PATHProcessingThe analyst clears the alert as a false positiveMeridian Bank (intermediary agent)
- 09 · EXCEPTION PATHSettlementThe payment resumes and settlesMeridian Bank (intermediary agent)
- OUTCOME
- Funds
- Delivered to the creditor after the screening delay.
- Settlement
- Settled after release from the sanctions review.
- Who acts next
- Meridian Bank (intermediary agent) — Nothing to fix in the payment; the alert, evidence, and disposition are retained for audit. Repeated false positives on this name feed tuning reviews.
Full step-by-step text (works without JavaScript)
- 02ProcessingBank 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.
- 04ProcessingMeridian 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.
- 05 · EXCEPTION PATHProcessingThe payment is held in the screening queueMeridian Bank (intermediary agent)
An alert is generated and the funds do not move. Every hour of hold time is visible to customers on both ends — but releasing a true match is far worse.
- 08 · EXCEPTION PATHProcessingThe analyst clears the alert as a false positiveMeridian Bank (intermediary agent)
Secondary identifiers do not match the listed person. The disposition, evidence, and analyst are recorded for audit.
- 09 · EXCEPTION PATHSettlementThe payment resumes and settlesMeridian Bank (intermediary agent)
Released from the queue, the transfer completes normally — later than planned.
- 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
- OUTCOME
- Funds
- Delivered to the creditor after the screening delay.
- Settlement
- Settled after release from the sanctions review.
- Who acts next
- Meridian Bank (intermediary agent) — Nothing to fix in the payment; the alert, evidence, and disposition are retained for audit. Repeated false positives on this name feed tuning reviews.
THE TIMELINE
- 01Bank AlfaSends the CBPR+ payment toward the creditor agent via its intermediary, Meridian Bank.pacs.008
- 02Meridian BankScreening flags a close similarity between a party in the message and a sanctions-list entry; the payment is held in a review queue.
Holding pending review is standard practice: releasing a true match could be a sanctions breach.
- 03Meridian BankRequests more information from Bank Alfa about the flagged party — full name, address, and date of birth or registration details.
- 04Bank AlfaPasses verified customer details back to Meridian.
- 05Meridian BankAn analyst compares the message party against the list entry's identifiers and dispositions the alert as a false positive — the details do not line up.
- 06Meridian BankReleases the payment and forwards it to Cassia Bank.pacs.008
- 07Cassia BankCredits the creditor and sends the status confirmation back along the chain.pacs.002
Resolution: The alert is dispositioned as a false positive and the payment completes late rather than never. A true match would have ended very differently: frozen or rejected funds and a report to the competent authority — not a quiet release.
Sources for this scenario3
- Official requirement
Cross-Border Payments and Reporting Plus (CBPR+) usage guidelines ↗ — Swift (CBPR+ working group)
Full guidelines require MyStandards access; content here relies on public summaries. MT-to-CBPR+ translation rules are published on Swift's translation portal.
- Market practice
Wolfsberg Group Sanctions Screening Guidance ↗ — The Wolfsberg Group
Wolfsberg guidance is industry market practice, not law; institutions vary in how they apply it.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
What this simplifies: Single-intermediary chain; institution-specific handling varies.
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.