# Bitcoin refunds: why returning a payment requires a new transaction

An ordinary Bitcoin refund is a new transaction authorized by the party returning funds. It does not erase or reverse the original payment. Agree on the refund amount and obtain a suitable destination from the customer. Do not automatically send money to an address inferred from the original transaction’s inputs; a custodial service may not credit that return to the customer.

Evidence: [Payment Processing](https://developer.bitcoin.org/devguide/payment_processing.html); [Refunds](https://docs.btcpayserver.org/Refund/); [Some things you need to know](https://bitcoin.org/en/you-need-to-know)

Canonical: https://degreesofsatoshi.com/encyclopedia/bitcoin-payment-refunds/
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

- **Ledger effect:** Original payment remains in history ([Transactions](https://developer.bitcoin.org/devguide/transactions.html))
- **Destination:** Use a confirmed refund destination ([Payment Processing](https://developer.bitcoin.org/devguide/payment_processing.html))
- **Costs:** The refund has its own transaction fee ([Transactions](https://developer.bitcoin.org/devguide/transactions.html))

## Establish the amount being returned

A refund policy needs a unit of account. Returning the original bitcoin quantity, its original fiat value, or an amount calculated at a later exchange rate can produce different results. The cited BTCPay documentation offers these choices explicitly; the software cannot choose the commercial agreement for both parties.

For example, a 100,000-satoshi purchase followed by an agreed 25% bitcoin-denominated refund means 25,000 satoshis before any separately agreed fee deduction.

Evidence: [Invoices](https://docs.btcpayserver.org/Users/invoices/)

## The input address is not a return label

An exchange can combine several customers’ withdrawals in one transaction or spend from addresses it manages centrally. Sending back to one of those source addresses may fail to identify the customer’s account. The developer guide describes this exact refund hazard.

BTCPay’s documented flow lets the customer claim a refund with a payout destination, which the merchant then reviews and processes. Confirm the destination through the customer relationship, not through an unsolicited message.

Evidence: [Payment Processing](https://developer.bitcoin.org/devguide/payment_processing.html); [Refunds](https://docs.btcpayserver.org/Refund/)

## Approve, send and reconcile the new transaction

The merchant signs and broadcasts a separate payout. Record its transaction identifier with the original invoice and confirm the recipient amount. If fee subtraction is used, the amount delivered can be lower than the entered amount.

Do not call the refund complete merely because a claim link was generated. The documented on-chain flow distinguishes a requested payout, a signed transaction awaiting confirmation and a completed payout.

Evidence: [Refunds](https://docs.btcpayserver.org/Refund/); [sendtoaddress RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/wallet/sendtoaddress/)

## Questions

### Can the Bitcoin network force a merchant to refund me?

The ordinary protocol has no merchant-refund authority or chargeback command. Returning funds requires an authorized new spend; any contractual or legal remedy is separate from that transaction mechanism.

Evidence: [Some things you need to know](https://bitcoin.org/en/you-need-to-know); [Transactions](https://developer.bitcoin.org/devguide/transactions.html)

### Can I reuse the sender address as the refund address?

Do not assume it is suitable. Transaction inputs can belong to a shared custodial system, and the customer may need a different deposit destination. Obtain and verify a current refund address from the customer.

Evidence: [Payment Processing](https://developer.bitcoin.org/devguide/payment_processing.html)

## Claims and scope

### bitcoin-payment-refunds-quick-answer

An ordinary Bitcoin refund is a new transaction authorized by the party returning funds. It does not erase or reverse the original payment. Agree on the refund amount and obtain a suitable destination from the customer. Do not automatically send money to an address inferred from the original transaction’s inputs; a custodial service may not credit that return to the customer.

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-refunds-fact-ledger-effect

Ledger effect: Original payment remains in history

Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null}

### bitcoin-payment-refunds-fact-destination

Destination: Use a confirmed refund destination

Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null}

### bitcoin-payment-refunds-fact-costs

Costs: The refund has its own transaction fee

Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null}

## Sources

- [Payment Processing](https://developer.bitcoin.org/devguide/payment_processing.html) — Bitcoin developer documentation. Payment request interpretation, confirmation checks and refund destination risks; historical protocol sections are dated. Locator: Requesting Payments; Verifying Payment; Issuing Refunds. Retrieved: 2026-10-02T18:53:53.958Z.
- [Refunds](https://docs.btcpayserver.org/Refund/) — BTCPay Server. A refund creates a separate payout and requires a usable destination rather than reversing history. Locator: Create a refund; Processing refund. Retrieved: 2026-10-02T18:53:56.900Z.
- [Some things you need to know](https://bitcoin.org/en/you-need-to-know) — Bitcoin.org. Payment reversibility, confirmation risk and visible transaction records. Locator: Bitcoin payments are irreversible; Unconfirmed transactions aren't secure; You are your own bank; Bitcoin is not anonymous. Retrieved: 2026-10-02T18:53:53.609Z.
- [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.
- [Invoices](https://docs.btcpayserver.org/Users/invoices/) — BTCPay Server. Checkout states, paid-late/over/partial exceptions and confirmations as distinct events. Locator: Invoice statuses; Invoice details; Refunding an invoice; Archiving invoices. Retrieved: 2026-10-02T18:53:56.741Z.
- [sendtoaddress RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/wallet/sendtoaddress/) — Bitcoin Core. Fee subtraction changes recipient output; comments remain local metadata. Locator: Description; Arguments: amount, comment, comment_to, subtractfeefromamount, fee_rate; Result. Retrieved: 2026-10-02T18:53:55.005Z.

## Revision history

- 2026-10-02: First publication after primary-source research and separate automated verification.

## Cite this entry

Degrees of Satoshi editorial project. “Bitcoin refunds: why returning a payment requires a new transaction.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/bitcoin-payment-refunds/