What happens when a payout fails?
“Failed” is a status. It is not a diagnosis. A payout can fail before submission, at the payment network, after submission, or inside your own application. Each case needs a different response.
1. Validation failed
The payment never reached the network.
Examples include missing recipient information, an invalid amount, or an incomplete destination.
Create payout
|
Validation
|
Failed
Money moved: noFix the data before sending another request.
2. The network rejected the payment
The instruction reached external payment infrastructure but could not proceed.
A useful record includes the reason and next action.
Status Failed Reason Destination unavailable Action Select another eligible method
3. The payment was returned
An ACH payment can be submitted and later returned with a standardized reason.
Submitted -> Processed -> Returned
Finance needs the ledger updated so the original obligation does not look satisfied when the money came back.
4. The request timed out
This is one of the easiest ways to create a duplicate.
Your application sends the request. The remote system processes it. The response never makes it back.
The application sees a timeout.
The correct conclusion is not “the payment failed.” The result is unknown until the existing payout is checked.
Request sent
|
No response
|
Check existing payout status
|
Decide whether another attempt is safe5. The preferred route is unavailable
A route failure does not always need to become a payout failure.
If RTP is unavailable but FedNow or ACH is eligible, the system may be able to choose another route according to program rules.
Four questions for every failure
- What happened?
- Did money move?
- Can the system retry safely?
- Who needs to act?
A useful failure state gives operations enough information to make the next decision without opening several tools.
See a failure handled well. We’ll fail a payout on purpose and show the reason, the ledger, and the retry.
Book a demo