Loading, please wait…
Payout Events provide visibility into payout activity throughout the payout lifecycle.
As a payout moves from creation through processing, delivery, completion, or exception handling, events communicate status changes to platforms, operational teams, reporting systems, and integrated applications.
Payout Events help platforms:
Events may occur before execution, during processing, and after payout completion.
These statuses occur before funds are released for processing.
| Status | Description |
|---|---|
| Created | Payout request has been received. |
| Pending | Waiting for processing to begin. |
| Scheduled | Waiting for a configured execution date or schedule. |
| Validating | Validation activities are in progress. |
| Approved | Validation requirements have been satisfied and the payout is ready for execution. |
| On Hold | Additional review or approval is required before processing can continue. |
These statuses occur while the payout is being prepared or processed.
| Status | Description |
|---|---|
| Funding | Funding availability is being confirmed. |
| Routed | Delivery route has been selected. |
| Submitted | Payout instruction has been submitted for processing. |
| Processing | Payout is actively being processed. |
| In Transit | Funds are moving through the selected payout path. |
| Awaiting Confirmation | Final confirmation is pending from the payout provider or destination. |
These statuses indicate successful payout completion.
| Status | Description |
|---|---|
| Completed | Payout was successfully processed. |
| Settled | Settlement activities have completed. |
| Credited | Recipient destination received the funds. |
| Success | Final successful outcome has been recorded. |
These statuses indicate that payout processing requires additional attention.
| Status | Description |
|---|---|
| Failed | Payout could not be completed. |
| Rejected | Payout was rejected before or during processing. |
| Returned | Funds were returned after execution. |
| Expired | Processing timed out before completion. |
| Compliance Hold | Additional compliance review is required. |
| Fraud Hold | Additional fraud or risk review is required. |
| Funding Hold | Funding requirements have not been satisfied. |
| Destination Reject | The selected payout destination cannot receive funds. |
| Routing Reject | No valid payout route is available. |
For detailed exception handling and recovery processes, see Payout Reversals and Exceptions.
Events may be used to notify systems, operational teams, and reporting processes when payout activity occurs.
Examples include:
The specific notification options available depend on the implemented solution and integration model.
Payout Events provide traceability across the payout lifecycle and support operational reporting and reconciliation activities.
Examples include:
This information can be used to investigate processing outcomes, support operational reporting, and reconcile payout activity.