Guide · Platforms, payroll, airdrops, marketplaces paying many wallets

How to batch-send crypto payouts

One payment is a signature. A hundred is a workflow: names slip, addresses transpose, networks get mismatched, and somewhere a spreadsheet is being reconciled by hand at midnight. Batch payout exists because that workflow deserves tooling, not heroics.

This guide covers the whole path - list in, preview, send, reconcile - for payroll runs, marketplace settlements, creator payouts, and the long tail of use-cases that all reduce to 'many wallets, one balance'.

You needA balance to pay from on each network you will useA payout list: address, amount, asset (CSV or API)The discipline to preview

Step by step

Every step, in order.

Step 01

Assemble the list

One row per payout: address, amount, asset. The batch tool takes pasted CSV or an API submission from your platform. Address formats are validated per network on entry - a Tron address in an Ethereum column fails before it can cost money.

Step 02

Preview every leg

The preview shows each payout with its network, fee, and total draw on your balance. This is the step that catches transposed digits and wrong-network rows. Read it; every batch tool in history exists because someone didn't.

Step 03

Fund and sign

Sign per network: one signature covers all payouts on that chain. Fees are the networks' own gas, shown per leg in the preview - no batching service fee hides in the middle.

Step 04

Watch confirmations

Each payout confirms independently on its network with the block explorer linked. Fast chains clear in seconds; Bitcoin follows its policy. The batch view rolls up the whole run's status.

Step 05

Export and reconcile

Download the settlement report - every leg with its transaction ID - and hand it to your ledger. The report is the reconciliation: what left, where it went, when it confirmed.

The part that matters

Where batches go wrong is never the cryptography; it is the list hygiene around it. The patterns that survive contact with real payroll runs: validate on entry, not on send (the network check catches cross-chain transposition for free); idempotency keys per run, so a retried API submission cannot double-pay (the API honors a key you supply); and amounts in the asset's own units, decided once at list-build time, not recomputed at send time when the price has moved. The payroll-shaped version of this connects to the payouts use-case page: amounts computed from your source of truth, exported as a batch, settled as a report. The airdrop-shaped version skews to thousands of small legs on one cheap network, where gas economics matter more than per-leg ceremony. Both are the same flow with different constants, which is the point of having one flow.

Go deeper

Payouts and payrollConfirmation policySettlement finalitySend app

FAQ

How many payouts can one batch hold?
Thousands - the practical limit is your list hygiene, not the tool. Each leg is an independent on-chain transfer; the batch groups them per network so you sign once per chain.
What fees do batches pay?
Each leg pays its network's gas, shown in the preview per payout and totaled per run. There is no batching premium - the platform's flat economics do not change because you send many.
Can I mix assets and networks in one batch?
Yes: group your list by asset and network, submit once, and sign once per network. The confirmation view tracks every leg independently.
What if one address in the list is wrong?
Format validation catches wrong-network addresses on entry. An address that is well-formed but wrong is why the preview exists - after signature, an on-chain transfer is final, which is the same truth as a wire and worth the same care.

Other guides

How to accept crypto payments

Accept Bitcoin, Ethereum, stablecoins and 53 more assets at checkout in minutes: connect…

How to swap across chains

Swap any asset for any other across 35 networks: connect a wallet, pick the pair, review…

How to buy UCASH

Three ways to get UCASH, the U.CASH network token: card or bank through the partner ramp,…

Keep going

How to batch-send crypto payouts, done right

Six guides, one platform, every rail non-custodial.