Payouts
Use payouts when you need to disburse funds from Radom as part of merchant settlement, treasury movement, customer operations, or downstream beneficiary payouts.
How payouts fit into Radom
Payouts usually sit at the end of a broader Radom flow:
- Funds come in through crypto payments, open banking, virtual accounts, or dedicated crypto deposits.
- Balances are reconciled and, where needed, converted into the asset or currency the business wants to hold.
- Funds are sent out as fiat or crypto disbursements to customers, vendors, treasury destinations, or internal operational accounts.
Funding model
Today, payout workflows are commonly funded from USDC or another supported stablecoin balance, with broader asset flexibility expanding through Convert. That lets merchants take in one asset, rebalance treasury, and disburse in the format that fits the beneficiary or operating corridor.
Destination types and corridors
Radom's public payout and external-account models support a mix of destination types, including:
- US bank accounts for USD payout flows.
- IBAN accounts for EUR payout flows.
- CLABE and Pix style local payout destinations where enabled.
- GB and SWIFT-style destination models in supported setups.
- Crypto payout destinations for on-chain disbursements.
Exact payout rails, settlement times, and approval controls depend on your organization setup, corridor, and enabled products. Public models also expose fiat payout pricing for currencies such as USD, EUR, GBP, MXN, and BRL, but you should still confirm your production coverage before launch.
Recommended operating model
- Decide which balance or source flow funds your payouts.
- Define whether payouts are one-off operations, recurring disbursements, or part of a batched workflow.
- Subscribe to webhooks so your systems can react to payout status changes without polling.
- Validate beneficiary and destination account data before initiating live operations.
- If you expect high volume, review Mass payouts alongside your standard payout flow.