Pay 1,000 people in 174 countries.One API call.
Bulk payouts to bank accounts, mobile money wallets, and self-custody crypto wallets. Per-recipient status. Individual retry. Idempotency keys that survive batch retries. The kind of payouts API engineers will actually agree to maintain.
One call, up to 1,000 recipients.
A single POST /v1/payouts/bulk call accepts up to 1,000 recipients. Each recipient has a destination type — bank account, mobile money, or crypto wallet — and the payload schema is the same regardless of country. The response returns a batch ID; per-recipient status surfaces through webhook events and the dashboard. Failed recipients show the reason and offer individual retry, so a single bad routing number doesn't fail the whole batch.
What the destinations look like.
Bank accounts in major markets. Mobile money wallets — MTN, Airtel, M-Pesa, GCash, and others — in emerging markets where mobile money is the actual rail. USDC on Stellar, Ethereum, or Base for recipients who already have crypto wallets. EURC and XLM on Stellar for the Stellar-native crowd. The destination is the recipient's choice, set on a per-recipient basis.
Three vendors collapsed into one.
- A separate vendor for cross-border bank payouts
- A separate vendor for mobile money corridors
- A separate vendor for crypto disbursements
One payout API. Every rail.
Read the API reference, run a test batch in the sandbox, and ship the integration before the next payout cycle.