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

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

PROGRESS
BREAK IT · CBPR+ CROSS-BORDER TRANSFER (PACS.008)

What happens when this goes wrong?

Every other page shows this payment working. Here you choose what breaks, and follow the damage — because a hold, a return or a missed cut-off is the system working as designed, and reading one calmly is the job.

CHOOSE WHAT GOES WRONG

Pick a failure above. Nothing here is invented — each one is a reason code this rail really uses, at the step where it really strikes.

EVERY FAILURE ON THIS RAIL

  • TRUNCStep 3: The pacs.008 leaves with a BAH and UETR — Address data arrives malformed from an upstream translation
  • HOLDStep 4: Meridian screens in the middle of the chain — A potential sanctions match stops the payment for review
  • RFIStep 7: Cassia validates the incoming payment — Details are insufficient to apply the credit — information is requested

One intermediary agent and a single settlement venue. The classic unable-to-apply repair dialogue is shown for teaching; investigation choreography varies by service, corridor and migration date. Every failure here is authored on CBPR+ cross-border transfer (pacs.008), with the sources that back it.