A failed payment did not complete through its intended route. The label alone does not say whether funds were debited, returned or never moved.
Invalid Bank details, insufficient funds, expired authorization, unsupported routing, transaction limits and an institution’s review can all stop a payment. The recorded reason should determine whether finance corrects, retries or investigates it.
Failure, rejection and return
| Term | Typical point | Next question |
|---|---|---|
| Validation failure | Before routing | Which field is missing or invalid? |
| Rejection | Institution refuses the instruction | Can the issue be corrected? |
| Return | Funds or instruction move back after acceptance | Were fees or FX differences applied? |
| Cancellation | Instruction is stopped before completion | Was cancellation confirmed? |
| Recall request | Sender asks to recover a sent payment | Did the receiving chain agree? |
Before retrying
- Read the failure code and provider explanation.
- Confirm whether funds were debited or returned.
- Verify the Recipient and Bank details independently.
- Check currency, amount, purpose and route eligibility.
- Prevent duplicate payment if the original status is uncertain.
How should finance record it?
Keep the original instruction, failure reason, return amount, fees, exchange-rate impact and replacement-payment reference. A returned cross-currency payment can create a gain or loss if conversion happens again.
Do not create a replacement solely because Quotable Payments or another provider shows Failed. First establish where the original funds are, then attach the failure evidence and replacement reference to the same business record.
