Skip to main content
Your team can set approval policies so that some bank and crypto payouts, including the ones created through the API, wait for one or more approval steps before Ralio sends them. Payouts that no policy matches are sent as usual.
Approvals are always made by people, never by the API. A member of your team approves or rejects each step from the Ralio dashboard with two-factor authentication. Your integration only follows the result, through webhooks or the approval block.

​
Lifecycle

A payout that matches a policy stops in PENDING_APPROVAL (after the OTP, when one is required), with its funds reserved:
Once approved, it continues as a regular payout. If you fixed the amount the recipient receives, it is requoted on approval, so the final amounts can differ from the ones at creation.

​
The approval block

The create, validate OTP and order details responses (bank and crypto) include approval. It is null when the payout doesn’t need approval, and the order lists don’t include it. To list the payouts that are waiting, filter the order lists with state_eq=PENDING_APPROVAL.

​
Webhooks

Intermediate approvals don’t send a webhook.
state and data.status can return values your integration hasn’t seen before. Don’t treat an unknown value as an error: keep the payout open and wait for the next event.