Batch Payments and Where They Are Supported

Paying five people separately costs five transaction fees. Paying them in one transaction costs one base fee plus a small increment per recipient.

The saving

On unspent-output chains, a batch transaction has one set of inputs and multiple outputs. Each additional output adds a small number of bytes. The saving against separate transactions is large and grows with the number of recipients.

On account-based chains, batching requires a contract that loops over recipients. The saving is smaller because each transfer still costs gas, and it is real because the base transaction cost is paid once.

Where it is supported

Wallets with a batch send feature. Several desktop and hardware wallet interfaces support this natively on unspent-output chains.

Payment processors and payroll tools. Built for exactly this.

Disperse-style contracts on account-based chains, which take a list of recipients and amounts.

Exchange withdrawal batching, which happens on the venue’s side. Several platforms batch customer withdrawals into single transactions, which is why their withdrawal fee can be below the cost of an individual transaction.

That last one is worth knowing: a venue with a low withdrawal fee may be achieving it through batching rather than through subsidy.

Who benefits

Anyone paying multiple recipients regularly. Contractors, contributors, distributions.

Projects distributing tokens.

Anyone consolidating or splitting holdings across their own addresses.

Who does not

A user making a single transfer occasionally. The feature is irrelevant.

The practical notes

Verify every recipient before signing. A batch transaction is atomic: all recipients or none. An error in one line means resubmitting the whole thing.

Check the destination addresses on a hardware wallet screen where the device supports displaying multiple outputs. Some do not display all of them clearly, which is a real limitation for this use case.

Test with small amounts on the first use of any batching tool.

Watch the gas limit on contract-based batching. A large batch can approach block limits, and a transaction that runs out of gas costs the full limit and delivers nothing.

The timing overlay

Batching and timing compound. A batch executed at the weekly fee low costs a fraction of the same batch at a peak.

Since batched payments are usually scheduled rather than urgent, the timing is free to optimise.

The adjacent optimisation

For withdrawals from a venue, the equivalent is frequency rather than batching: four withdrawals a year instead of twelve costs a quarter as much in fixed fees.

Venues publishing their per-network withdrawal charges, such as an exchange with a published withdrawal schedule, make it straightforward to calculate the right frequency for your contribution size.