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

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

PROGRESS
BREAK IT · SEPA SCT THROUGH AN INDIRECT PARTICIPANT

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

  • FILEStep 5: Sponsor Bank validates the sponsored submission — Envelope, signature, count or control sum fails
  • CUTOFFStep 5: Sponsor Bank validates the sponsored submission — The valid file misses the sponsor's submission cut-off
  • AC04Step 9: Nordbank receives its input credit file — One beneficiary account is closed after settlement

The sponsor owns one direct connection and settlement account. Input credit file is explicitly a local interface label around pacs.008 transactions, not a universal SEPA message name. Every failure here is authored on SEPA SCT through an indirect participant, with the sources that back it.