# Bitcoin payment batching: many recipients in one transaction 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. Evidence: [Transactions](https://developer.bitcoin.org/devguide/transactions.html); [sendmany RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/wallet/sendmany/); [Segregated Witness](https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0141.mediawiki) Canonical: https://degreesofsatoshi.com/encyclopedia/bitcoin-payment-batching/ Published: 2026-10-02 Substantively modified: 2026-10-02 Independently verified by an automated reviewer: 2026-10-02T19:29:20.637Z Data current through: 2026-10-02 AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied. ## Key facts - **Structure:** One transaction can create many outputs ([Transactions](https://developer.bitcoin.org/devguide/transactions.html)) - **Identifier:** A sendmany batch returns one transaction ID ([sendmany RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/wallet/sendmany/)) - **Fee:** Paid for the whole transaction, not independently per recipient ([Transactions](https://developer.bitcoin.org/devguide/transactions.html)) ## 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. Evidence: [sendmany RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/wallet/sendmany/); [Transactions](https://developer.bitcoin.org/devguide/transactions.html) ## 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. Evidence: [Segregated Witness](https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0141.mediawiki); [Transactions](https://developer.bitcoin.org/devguide/transactions.html) ## 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. Evidence: [Transactions](https://developer.bitcoin.org/devguide/transactions.html); [sendmany RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/wallet/sendmany/) ## Questions ### 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. Evidence: [Transactions](https://developer.bitcoin.org/devguide/transactions.html); [sendmany RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/wallet/sendmany/) ### 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. Evidence: [Transactions](https://developer.bitcoin.org/devguide/transactions.html) ## Claims and scope ### bitcoin-payment-batching-quick-answer 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: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null} ### bitcoin-payment-batching-fact-structure Structure: One transaction can create many outputs Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null} ### bitcoin-payment-batching-fact-identifier Identifier: A sendmany batch returns one transaction ID Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null} ### bitcoin-payment-batching-fact-fee Fee: Paid for the whole transaction, not independently per recipient Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null} ## Sources - [Transactions](https://developer.bitcoin.org/devguide/transactions.html) — Bitcoin 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. Retrieved: 2026-10-02T18:53:53.759Z. - [sendmany RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/wallet/sendmany/) — Bitcoin Core. Multiple recipient outputs and optional fee deduction behavior. Locator: Arguments: amounts, subtractfeefrom. Retrieved: 2026-10-02T18:53:54.997Z. - [Segregated Witness](https://raw.githubusercontent.com/bitcoin/bips/927b6de9915c9262615a6399de51b200f81e5aa4/bip-0141.mediawiki) — Bitcoin Improvement Proposals. Transaction identifiers, weight and virtual size definitions. Locator: Transaction ID; Additional definitions; Transaction size calculations. Retrieved: 2026-10-02T18:53:54.098Z. ## Revision history - 2026-10-02: First publication after primary-source research and separate automated verification. ## Cite this entry Degrees 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/