Skip to content

Send to Many, Without Sending One at a Time

If you're paying out to multiple addresses — a team, a community distribution, recurring transfers — doing it one transaction at a time doesn't scale. Batch send does.

  • ✓One transaction, many recipients
  • ✓Reusable templates
  • ✓Same non-custodial security

Built for Repeat Payouts

Sending QUBIC to the same group of addresses over and over — payroll, contributor payments, distributing rewards — is tedious to do manually, one transaction at a time, and easy to make a mistake on when you're rushing through a long list. Batch send handles the whole list in one confirmed transaction, and lets you save the recipient list as a template so next time takes seconds, not minutes. This is the kind of feature that matters more the more seriously you're using Qubic — occasional, single-recipient sends never really needed it, but anyone managing a recurring group of payments feels the difference immediately.

Batch Sending in Four Steps

  1. 01

    Open Batch Send and add recipient addresses

    Build the full list before entering amounts.
  2. 02

    Enter an amount for each recipient

    Amounts can differ per recipient.
  3. 03

    Review the full list and total before confirming

    Catch a mistake before it's sent, not after.
  4. 04

    Confirm

    All recipients are paid in a single transaction.

Why This Matters Beyond Convenience

It's tempting to think of batch sending purely as a time-saver, but there's a security dimension too: every individual transaction is a fresh opportunity for a copy-paste error, an address mixed up between two similarly-named recipients, or a transposed digit in an amount. Consolidating a repeated set of transfers into one reviewed batch doesn't just save time — it reduces the total number of moments where a mistake could happen, since you're reviewing one consolidated list instead of trusting yourself to get each of several separate transactions right in a row.

Who Actually Uses This Feature

Batch send tends to matter most to a specific set of users: small teams or DAOs paying contributors, community organizers distributing rewards or airdrops, and individuals managing funds across several of their own accounts. If you're sending QUBIC to one or two people occasionally, a standard single-recipient send covers that fine. The moment your recipient list grows past a handful of addresses, or repeats on any kind of schedule, batch send stops being a nice-to-have and starts being the obviously better tool for the job.

A Feature Built From Real Feedback

Batch send-to-many wasn't a speculative addition — it came directly from users describing exactly this repetitive, error-prone workflow before the feature existed. That's the general pattern for how features get prioritized here: real, repeated friction gets addressed, rather than features added because a competitor has them.

Scaling With You

Whether you're sending to three recipients or thirty, the same workflow applies — build the list, review it, confirm once. The feature doesn't get more complicated as your recipient count grows, which is exactly the point: complexity should scale with what you're actually managing, not with the tool you're using to manage it.

Common Batch Send Scenarios

ScenarioRecipients / Template Worth Saving?
Monthly team payroll
5-20 recipients — Yes, worth saving a template
One-time community airdrop
50+ recipients — Only if repeated
Splitting funds across your own wallets
2-5 recipients — Yes, if recurring
Quarterly contributor bonus
5-15 recipients — Yes, worth saving a template

The Time Saved Adds Up

A single batch transaction replacing even five individual sends saves more than just the minutes typing each one out — it saves five separate moments of address verification, five separate confirmations, five separate chances for something to go slightly wrong. Multiply that across a year of recurring payouts and the difference between doing it one at a time versus batching becomes substantial.

See It Step by Step

A full walkthrough of setting up and sending your first batch transaction, including saving a template for next time.

Read the batch send guide →