Loading, please wait…
Most payouts are processed and completed successfully. However, situations may occur that prevent a payout from being completed as expected or require a previously initiated payout to be corrected.
Payout Reversals and Exceptions helps platforms identify, investigate, and resolve payout issues while maintaining visibility throughout the payout lifecycle.
Common scenarios include:
By identifying and resolving issues before or after payout execution, platforms can reduce operational risk while maintaining accurate reporting, reconciliation, and auditability.
Although often discussed together, exceptions and reversals address different situations.
| Type | Description |
|---|---|
| Exception | A payout cannot proceed or complete successfully because validation, funding, compliance, routing, destination, or processing requirements are not satisfied. |
| Reversal | A previously submitted or completed payout requires correction, recall, recovery, or adjustment. |
Payout exceptions can occur before execution, during execution, or after a payout has been submitted for processing.
| Failure Category | Description |
|---|---|
| Recipient Validation Failure | Recipient is not eligible to receive funds due to onboarding, eligibility, or validation issues. |
| Destination Validation Failure | The selected payout destination cannot receive funds due to missing, invalid, or unsupported information. |
| Funding Failure | Funds are unavailable or funding prerequisites have not been satisfied. |
| Compliance Failure or Hold | Regulatory, sanctions, or compliance requirements prevent payout release. |
| Risk or Fraud Failure | Fraud controls, risk rules, duplicate requests, or transaction limits prevent payout execution. |
| Routing Failure | No valid payout route, rail, provider, currency, or destination path is available. |
| Provider or Rail Rejection | The downstream provider or payout network rejects the transaction. |
| Return or Rejection After Execution | Funds are returned or rejected after a payout has been submitted. |
| Cross-Border Eligibility Failure | Country, currency, destination, or disbursement restrictions prevent execution. |
| Processing or Operational Error | Operational or processing issues require corrective action. |
When an exception occurs, platforms may follow a structured resolution process.
The required remediation depends on the cause of the exception and where the issue occurred in the payout lifecycle.
Depending on the issue, platforms may take one or more corrective actions.
| Remediation Action | Description |
|---|---|
| Update Recipient Information | Resolve recipient eligibility or profile issues. |
| Update Destination Information | Correct account, wallet, card, or payout destination information. |
| Resolve Funding Issues | Ensure sufficient funds are available for payout execution. |
| Complete Compliance Review | Satisfy regulatory, risk, or compliance requirements. |
| Retry Processing | Resubmit the payout after the underlying issue has been resolved. |
| Cancel the Payout | Stop processing before execution completes. |
| Initiate a Reversal | Correct a previously submitted or completed payout. |
A payout reversal is used when a previously submitted or completed payout requires correction.
Reversal availability depends on factors such as:
Examples may include:
Not all payouts can be reversed after submission. The ability to reverse a payout depends on the payout method and processing stage.
When supported, reversal requests follow a structured review and recovery process.
| Stage | Description |
|---|---|
| Payout Execution | The payout is processed and submitted to the selected payout provider or rail. |
| Outcome Received | The provider returns a processing result such as completed, failed, rejected, or returned. |
| Issue Identified | A return, rejection, correction request, or other exception is identified. |
| Reversal Assessment | The platform evaluates whether reversal or recovery is permitted. |
| Reversal or Recovery Processing | Recovery activities, reversals, or corrective actions are initiated. |
| Ledger and Balance Update | Returned or recovered funds are reflected in the appropriate balances and records. |
| Status and Notifications | Status updates and notifications are generated for operational visibility. |
| Reconciliation and Reporting | Results are reconciled and reflected in downstream reporting processes. |
| Closure or Review | The issue is closed or escalated for operational review if additional action is required. |
| Scenario | Description |
|---|---|
| Pre-submission cancellation | Payout is canceled before processing and funds remain available. |
| Returned payment | Funds are returned and balances are updated accordingly. |
| Full recovery | Funds are successfully recovered and credited back to the appropriate balance. |
| Partial recovery | Only a portion of the original funds can be recovered. |
| No funds returned | Recovery is not successful and operational review may be required. |
| Processing correction | A reversal or adjustment corrects a previously processed transaction. |
When designing exception and reversal handling processes, consider:
Clear operational procedures help improve payout reliability and reduce resolution times.