Encyclopedia How the network works · Entry 182
Bitcoin payment batching: many recipients in one transaction
In this article
At a glance
Key facts
One funding decision, several destinations
A batch might pay 20,000, 30,000 and 40,000 satoshis to three recipients, create sender change and pay one miner fee. The output values total 90,000 satoshis before change. The transaction must fund all outputs and the fee together.
Core’s sendmany documentation supports a destination-and-amount collection. If selected recipients bear a deducted fee, their delivered amounts shrink; the payer should not silently substitute this for promised invoice amounts.
Compare complete transactions at one fee rate
Assume three separate illustrative transactions would each be 140 vB, while a suitable combined transaction would be 230 vB. At 5 sat/vB, separate fees total 2,100 satoshis and the batch costs 1,150, a 950-satoshi difference.
Those sizes are assumptions for the arithmetic. Different input scripts, additional funding inputs or a different change arrangement can alter the result. Batching is not a fixed percentage discount.
Batching links the outputs publicly
Anyone reading the chain can see that the outputs were created together. One recipient may be able to identify another output using outside information. A batch also couples timing: replacing or delaying the transaction affects the group.
Keep per-recipient records beside the shared transaction ID. A shared identifier alone does not distinguish which output paid a specific invoice.
Direct answers
Questions people ask
Does each recipient pay the full miner fee?
The chain records one fee for the entire transaction. A service can allocate costs under its own accounting policy, but there is no separate protocol fee attached to each recipient output.
Does batching make the payment private?
No. It may be efficient, but it visibly groups recipients in one transaction. The ledger does not name those people; external records can still connect an output to a customer or invoice.
Inspect the evidence
The answer and key facts have stable claim links. These records retain the scope and qualification when reused.
Bitcoin payment batching creates several recipient outputs in one transaction. It can reduce duplicated transaction overhead and input use compared with separate payments, but savings depend on the actual construction. Recipients share one transaction identifier and confirmation event, which also makes their outputs visibly related. Each amount, destination and fee-deduction rule still needs review.
Educational explanation. Product-specific behavior is scoped to the cited documentation, checked 2026-10-02.
Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T19:29:20.637Z.
Link to this claimStructure: One transaction can create many outputs
Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T19:29:20.637Z.
Link to this claimIdentifier: A sendmany batch returns one transaction ID
Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T19:29:20.637Z.
Link to this claimFee: Paid for the whole transaction, not independently per recipient
Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T19:29:20.637Z.
Link to this claimRevision history
- — First publication after primary-source research and separate automated verification.
Source register
Sources and references
Retrieval dates and locators are recorded individually.- TransactionsBitcoin developer documentation
Inputs, outputs, authorization, change, coinbase exceptions and fee accounting.
Locator: Introduction; Spending An Output; P2PKH Script Validation; Multisig; Transaction Fees And Change; Avoiding Key Reuse · Version / scope: Developer guide; historical implementation details require qualification · Retrieved: 2026-10-02T18:53:53.759ZOpen source - sendmany RPCBitcoin Core
Multiple recipient outputs and optional fee deduction behavior.
Locator: Arguments: amounts, subtractfeefrom · Version / scope: Bitcoin Core 29.0 RPC reference; not a recommendation to install an old release · Retrieved: 2026-10-02T18:53:54.997ZOpen source - Segregated WitnessBitcoin Improvement Proposals
Transaction identifiers, weight and virtual size definitions.
Locator: Transaction ID; Additional definitions; Transaction size calculations · Version / scope: Pinned BIPs revision · Retrieved: 2026-10-02T18:53:54.098ZOpen source
Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.
Editorial method and correctionsDegrees of Satoshi editorial project. “Bitcoin payment batching: many recipients in one transaction.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/bitcoin-payment-batching/