The order is the same everywhere
Every payout runs quote, then execute, then status. The quote holds a rate for a short window; executing inside that window is what locks it.1
Quote
Ask what a payout costs. Anonymous, no user needed - the price can be shown
before anyone commits.
2
Execute
Name the user, the destination, and the quote. We answer with a deposit
address and the exact amount to send.
3
Send the stablecoins
The user’s wallet sends the quoted amount to that address. Nothing is
custodial before this point and nothing is signed by us.
4
Status
Poll, or take the webhook. A payout moves through
pending, converting,
sent, then settled.Which one needs which permission
Payout endpoints are granted per product on your API key, like every other vertical - see Authentication. A key without the permission gets403 permission_denied rather than a quote.
Identity
A payout is a transfer to a named person, so it needs the same shared identity result as the incoming direction - see Rheon ID. A user you have already onboarded for deposits can be paid out without onboarding again; pass the sameaccountId.
Card payouts and bank payouts do not always share a verification tier. A user
cleared for one can be asked for more before the other completes - the status
carries requires_action with what is missing rather than failing outright.