Batch Send
Pay many addresses from a CSV — one atomic signature when the wallet can batch, otherwise sequential.
You sign, we never can
About batch send
Pay many addresses from one list — payroll, grants, contributor splits, an airdrop. Where the wallet supports atomic batching every transfer goes in a single transaction, so it is one signature, one fee, and either all of them land or none do. Where it does not, each transfer is separate and the counter tells you exactly how far through you are, because a payroll that stops halfway is worse than one that never started. Malformed lines are refused up front rather than skipped silently. Site fee is always zero; each network fee on the batch or on each sequential send is never free.
Common questions
What is a batch crypto payment?
Paying many addresses from one list — payroll, grants, contributor splits, an airdrop — instead of signing a separate send for each recipient. This page takes a CSV (or one address and amount per line), checks every row up front, and then sends from the connected wallet. Site fee is zero; the network still charges for whatever transactions actually go out.
Is a batch send atomic or one transfer at a time?
It depends on the wallet. Where EIP-5792 atomic batching is supported, every transfer goes in a single transaction — one signature, one network fee, and either all of them land or none do. Where it is not, each transfer is sequential: its own signature, its own fee, and a counter that shows exactly how far through the list you are. A payroll that stops halfway is worse than one that never started, so the page says which path it is on before you sign.
How much does batch send cost?
Our cut is zero. The network fee is never free: one fee for an atomic batch, or one fee per recipient when the wallet falls back to sequential sends. The fee depends on the network and the token being moved, not on how large each payment is, and it is shown by the wallet before you confirm.