Batch payout
Also called: Bulk payout, Mass payout
Submitting many payouts in one request, as payroll, marketplace and affiliate platforms do, where each payment still has to succeed or fail cleanly on its own.
Platforms that pay sellers, creators or contractors send payouts in bulk: hundreds or thousands at a time from one wallet. Sending them one by one works, but a batch call saves round trips and keeps a run together.
The important design question is what happens when part of a batch fails. All-or-nothing sounds tidy but means one bad address blocks everyone. Most payout systems instead treat each payment separately and report which ones went through.
On Valtu
POST /v1/transfers/batch takes up to 100 payouts, each with its own required externalId. A batch isn't all-or-nothing: each payout is created or refused on its own, and the response says which. Sending the same batch again after a timeout returns the payouts already created, so the retry can't pay anyone twice. Payouts from one wallet on one network go out in order. If one waits for approval, that wallet's queue on that network waits while other wallets and networks carry on.
Related terms
Keep reading.
More in deposits and payouts: Deposit address · Payment link · Sweep · Reconciliation. The whole glossary.
Put it into practice.
Every workspace starts on testnets with free test coins: same dashboard, same API. Go live when your team is ready.