A batch send disperses one balance to many recipients in a single on-chain transaction: a file of addresses and amounts, one confirmation, every wallet paid. Against the alternative, a hundred individual transfers, it saves fees, eliminates repetitive signing, and produces one auditable record instead of a hundred.
Batch sends are the settlement primitive behind payroll in crypto, marketplace payouts, affiliate runs, and airdrops: anywhere one treasury must reach many parties on a schedule.
Batch send moves one balance to many recipients in a controlled flow: a list of address and amount rows goes in, the platform validates it, presents a preview of every leg with its fee, and after one signature per network, the transfers go out. The input is typically a CSV or an API submission from the caller's own systems.
The validation layer is where batch tooling earns its keep. Address formats check per network at entry, so a Tron address in an Ethereum column fails before it can cost money. Amounts re-verify against the balance. Duplicates surface. The preview then shows the whole run: every leg, every network's gas, every fee, and the total, before anything is signed.
Execution settles per network: one signature covers all the payouts on that chain, and the report afterward carries every leg with its transaction identifier. The discipline that makes it safe is list hygiene, and the tooling exists so hygiene is checked by software rather than heroics.
A payroll run of two hundred rows pastes in, three malformed rows flag immediately at entry, the preview totals the payouts and gas per network, two signatures go out, and the report lands with a transaction ID per recipient for the ledger.
send.u.cash takes a CSV of addresses (or web3 names) and amounts, validates it before anything moves, and settles the batch non-custodial with one exportable record for the books.
Payroll, marketplace settlements, creator payouts, and refund runs are the standard shapes. The batch tool turns each into a list in, preview checked, signatures signed, report filed workflow, with nothing about the individual payments left manual. On file hygiene between runs: keep the source of truth for destinations in one system, export to CSV per run, and never edit the export by hand after validation. The perennial batch incident is a hand-edit after the preview, which is why the discipline is edit upstream, revalidate, preview again.
Every term behind the rails, the assets, and the settlement.