Recipients required. Before creating a payout, you must register the recipient via the Recipients API. The recipient record holds banking details and identity information needed to route the funds.
Object Fields
The unique identifier of the payout (UUID).Example:
po_3f4a5b6c-7d8e-9f01-2345-6789abcdef01Current payout status. Transitions depend on provider processing times and fund availability.Values:
PENDING, PROCESSING, SUCCEEDED, FAILED, CANCELLEDPENDING. Payout created but not yet submitted to the provider.PROCESSING. Submitted to the provider; awaiting confirmation.SUCCEEDED. Funds successfully disbursed to the recipient.FAILED. Provider rejected the payout (invalid account, insufficient funds, etc.).CANCELLED. Cancelled by the merchant before processing began.
SUCCEEDEDThe payout amount details.
The country where the payout is executed. ISO 3166-1 alpha-2 code. Determines which providers and banking rails are available.Example:
USID of the recipient receiving the funds. Links to the Recipient Object.Example:
rcp_a1b2c3d4-e5f6-7890-abcd-ef1234567890The merchant’s own reference identifier for this payout, used for reconciliation between your system and Yuno. Must be unique per merchant account.Example:
payout-seller-20260310-001Information about the provider that processed the payout.
A human-readable description of the payout purpose (MAX 255).Example:
Marketplace seller payout - March 2026ISO 8601 timestamp of when the payout was created.Example:
2026-03-10T16:00:00.000ZISO 8601 timestamp of the last payout update.Example:
2026-03-10T16:05:30.000ZExample
Related Endpoints
- Create Payout.
POST /v1/payouts - Get Payout.
GET /v1/payouts/{payout_id} - Get Payout by Merchant Reference.
GET /v1/payouts?merchant_reference={reference}
Related Concepts
- Payouts. How disbursements work in Yuno