Exception Handling in Processing

Processing Phase

Card 34 explained receiving-side processing. It showed that a payment does not end when the sending bank sends it or when clearing and settlement have progressed. The receiving-side institution must still receive the instruction, validate it, check the beneficiary account, decide whether to credit, hold, return or reject, notify the beneficiary correctly and preserve evidence. Card 35 now moves into exception handling. This is the part of processing where the expected journey is interrupted and the bank must control what happens next.

An exception is not simply an error screen. In payment operations, an exception is any condition that prevents the payment from continuing through its expected straight-through path. The payment may stop, wait, hold, reject, return, retry, go to repair, go to investigation, or require manual review. Some exceptions are caused by the customer’s data. Some are caused by account or funding conditions. Some are caused by fraud or compliance controls. Some come from route unavailability, external system issues, cut-off misses, duplicate detection or downstream rejection. A mature bank does not treat all interruptions as the same generic failure.

Exception handling is one of the strongest tests of real payment quality. Happy-path processing proves that the system can move clean payments. Exception handling proves whether the bank can control real-world complexity. In real banks, payments fail, pause, timeout, duplicate, reject, return, mismatch, miss cut-off, get held, require repair and need investigation. If the bank cannot manage exceptions clearly, customers lose trust, operations teams become overloaded, reconciliation breaks increase, and financial risk grows.

This card must be read carefully with Card 36. Card 35 focuses on understanding and classifying exceptions during processing. Card 36 will go deeper into repair and intervention: what humans or controlled tools do after an exception is identified. In other words, Card 35 explains why the payment was interrupted and what the controlled state should be. Card 36 explains how the bank may correct, release, reroute, return or cancel where allowed.

Explore the complete Payment Life Cycle