Pay hundreds of people from one list. In one token on one network, each batch pays everyone in it or nobody.

Different people, different networks, different tokens. Up to 12 recipients in one cross‑chain transaction, 8 with a swap in one network. Payroll, contributor rewards, grants, DAO distributions.

Create a payout Put it in your product

How it works

Four steps, one signature to send.

Build the list

Type it, import a CSV, or pull people out of your contacts. Rows are checked as they arrive: a bad address, a missing amount or a duplicate is flagged on the row, with the reason.

Check it once, properly

Before signing you see every address in full, with its amount and network beside it. Not a truncated preview of the first three.

Sign once

Between 60 and 900 recipients in one signature when the batch stays inside a single network. The ceiling is that network’s own block limit rather than a rule of ours, so it differs per chain and is higher for a token than for the native coin. The app shows the exact number for your batch before you sign. A cross‑chain batch takes up to 12 recipients in one signature, each on the network they want to be paid on.

Watch each payment land

Per‑recipient status while it runs. With a swap in one network, a payment that fails is refunded in the same transaction and does not hold back the others. Across networks, the transaction you sign sends every payment or none; after that each travels on its own, and one that fails does not hold back the others. Refunds go to the wallet that paid; if a payment stops in our contract, we deliver it or refund it ourselves.

What you get

The parts you won’t find stitched together anywhere else.

One signature, many people, many chains

This is the part nobody else sells. An aggregator moves one route at a time; a batch here is one transaction that reaches every recipient in it.

A second person can be required

Set a threshold, and a batch above it waits for someone else to approve, with roles and per‑person limits. Ordinary in company banking, missing everywhere in crypto.

Schedules

A list that repeats on a period, with the same approval rules as a one‑off.

A CSV that tells you what’s wrong

Row‑level reasons, duplicate merging, and an errors file you can fix and re‑import.

Non‑custodial

You send from your own wallet, not from a balance we hold.

On your own

Sign and it’s done

If you’re one person, you build the list, sign, and it’s done. Nothing asks you to invite anybody.

With a team

Someone else confirms

If there are several of you, the same account carries roles: who may prepare a batch, who must approve it above a threshold, and what each person may release. Signing in is not the same as the right to sign a payment.

Who it’s for

Built for the teams enterprise gateways won’t talk to.

No volume floor

Enterprise payout providers open the conversation at hundreds of thousands a month and months of processing history. Here the first batch can be three people, today.

No sales call

The price is on the page, 0.10% within one network, and the account is self-serve. Nobody quotes you a number based on how big you sounded on a call.

Nothing of yours to custody

Payouts go out from your own wallet, so there is no balance to onboard and no waiting to get it back out.

0.10%

within one network, in one tokenAcross networks: 0.30% for one recipient · 0.70% for 2 to 12With a swap in one network: 0.30% to 0.90%, by how many recipientsBatches across networks or with a swap: the rate above, or the network gas × 1.5 if that’s higher.

How pricing works

Pay many at once.

Create a payout Documentation

Don’t have their addresses yet? Use Claims.Money coming the other way is Payments.

Compare with what you’re using: Disperse·Multisender·Safe CSV Airdrop