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

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

PROGRESS
BREAK IT · CORPORATE PAYMENT — LEGACY MT 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

  • RJCTStep 2: Bank Alfa validates the MT101 — The customer request cannot be executed
  • REJTStep 6: Meridian validates and screens the MT103 — Payment rejected before value is booked
  • RETNStep 10: Nordbank validates and matches the payment — Account closed after settlement
  • QUERYStep 10: Nordbank validates and matches the payment — More information is required
  • FREEStep 10: Nordbank validates and matches the payment — The bank uses a free-format investigation
  • CNCLStep 11: Nordbank credits the supplier — Bank Alfa asks for the paid funds back
  • RJCRStep 11: Nordbank credits the supplier — The cancellation request is refused

A legacy teaching composite, not a recommendation to start new MT implementations. It joins corporate initiation, serial correspondent settlement, investigations, returns, and two account-reporting perspectives; bilateral services and migration dates vary. Every failure here is authored on Corporate payment — legacy MT lifecycle, with the sources that back it.