recipientId or an inline recipient.
The payout endpoints accept the same credentials as the rest of the API — pass your
x-api-key header (or a JWT from token exchange) on every call. Payouts are fully server-to-server, at parity with the Collections API; no dashboard interaction is required.Get a quote
Lock FX before confirming a payout.
Corridors & recipient shapes
Supported countries and required fields.
Flow overview
- (Optional) Create a recipient —
POST /v1/business/payouts/recipientswith bank or mobile-money details. Skip this step if you pass the recipient inline on confirm. Sanctions screening runs in both cases. - Request a quote —
POST /v1/business/payouts/quotewith rail, corridor, and eithersrcAmount(USDC) ordstAmount(local currency). - Confirm the payout —
POST /v1/business/payoutswithquoteToken, eitherrecipientIdor an inlinerecipient, andidempotencyKey, within the 60-second window. - Track status — poll
GET /v1/business/payouts/{id}or subscribe to payout webhooks.
SDK quick start
Collections (inbound local rails) are documented under Local rails — server-to-server. This section covers outbound payouts only.
