Pay 150 people with one signature
Crypto mass payouts: one approval, one fee, one audit trail
On Bitcoin-family chains a single Vaultody transaction carries up to 150 recipients — hard platform bound, enforced at five layers. On account chains, the batch endpoint fans one sender out to many destinations as one managed request.
Share the Trust, Guard the Keys
150 transfers means 150 approvals, 150 fees and 150 chances to fat-finger
Paying a list of people one transfer at a time is not just slow — it multiplies every risk in the process. Vaultody treats the list as one transaction request: one policy evaluation, one approval trail, and on Bitcoin-family chains one on-chain transaction carrying every recipient.
- One approval, whole runApprovers see the batch — recipients, totals, source accounts — and confirm once. Partial approval does not exist by design.
- One fee on UTXO chainsA single Bitcoin-family transaction carries up to 150 outputs, so the network fee is shared across the whole run instead of paid per person.
- Validated before anything signsAddresses and amounts are checked before the signing ceremony starts, so a typo fails cheap rather than on-chain.
A payout run, not 150 transfers
Build the run
Submit recipients and amounts in one request. On UTXO chains you can even pick the exact coins to spend (coin control) and draw inputs from several vault accounts in the same transaction.
- ✓Up to 150 recipients per UTXO transaction — BTC, LTC, BCH, DOGE, DASH, ZEC
- ✓Account chains: batch endpoint on 6 EVM chains + Solana
- ✓Amounts validated before anything signs
Approve once, under policy
The run is one transaction request: it clears your policy or it does not. Approvers see the whole batch — recipients, totals, source accounts — and confirm once on the mobile co-signer, or your server co-signer signs it hands-off within rules.
- ✓One approval trail for the entire run
- ✓One on-chain fee shared across recipients on UTXO chains
- ✓Payouts count toward included volume — no separate payout fee
Where it pays off
Weekly runs to hundreds of recipients with one approval flow and one audit line per run — not per person.
The run clears treasury policy like any transfer; recipients and amounts are validated before signing.
Batch user withdrawals on UTXO chains — the fee economics alone justify it at volume.
Batch mechanics
Where the batch is one transaction and where it is one request.
Runs that pay for the feature
Weekly runs to hundreds of recipients with one approval flow and one audit line per run, not per person.
The run clears treasury policy like any transfer; recipients and amounts are validated before signing.
Batching user withdrawals on UTXO chains — at volume the fee economics alone justify the integration.
Frequently asked questions
Get answers to commonly asked questions.
Is it really one transaction?
On Bitcoin-family chains, yes — up to 150 recipients in one on-chain transaction. On account chains the batch is one request that manages the individual sends for you.
Can a run be partially approved?
No — a run is one request; it clears policy or it does not. Edits happen before approval, which is exactly what your auditors want.
Can inputs come from several accounts?
Yes — UTXO transfers can spend from multiple vault accounts in the same transaction, with change handled per your configuration.
What does it cost?
Runs count toward your plan's included volume like any outgoing transfer. On TRON, fee optimization discounts stack on top.
