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+ CORPORATE PAYMENT — FULL MX LIFECYCLE

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

  • AC01Step 2: Bank Alfa validates the instruction — Invalid account data — customer instruction rejected
  • RJCTStep 7: Meridian validates and screens the payment — Interbank instruction rejected before settlement
  • AC04Step 10: Nordbank validates the incoming payment — Supplier account is closed after settlement
  • RFIStep 10: Nordbank validates the incoming payment — More payment information is needed
  • CUSTStep 11: Nordbank credits the supplier — Asha later asks Bank Alfa to recover the payment
  • RJCRStep 11: Nordbank credits the supplier — The supplier refuses a recovery request

A teaching composite across customer initiation, CBPR+ execution, Case Management, and bank-to-customer reporting. Not every bank sends every status or report, and mutually exclusive reject, return, and recall outcomes are shown as branches. Every failure here is authored on CBPR+ corporate payment — full MX lifecycle, with the sources that back it.