Workflow
For every implementation, we recommend taking the payoutstatus as the main reference for the payout’s state. A payout could have different transactions associated with it. Therefore, by focusing on the payout status, you can have the latest state regardless of how many transactions were made, giving you a clear input for decision making. The image below presents the payout state machine.

Payout status
The following table presents allstatus and response_code you will find when handling payouts with the Yuno system. In addition, you will find the relation of status/response_code with the transaction status of the payout process.
| Status | Response code | Description |
|---|---|---|
CREATED | CREATED | Initial state when a payout is created. It is an internal state. |
PENDING | PENDING_PROVIDER_CONFIRMATION | The payout has been delivered to the provider and is being analyzed. |
PENDING | AUTHORIZED | The payout has been delivered to the provider, its authorized and its waiting merchant’s confirmation to release the transaction. Only available for certain providers that support it. |
SUCCEEDED | SUCCEEDED | The payout was successfully completed. |
REJECTED | REJECTED | Payout rejected by Yuno. Please review the request fields. |
DECLINED | DECLINED | The provider declined the payout. |
ERROR | ERROR | Error. |