Read the original transaction before choosing the refund amount.
A customer cancels a purchase paid in Bitcoin. The merchant opens the refund screen and sees several amount options. One returns the original Bitcoin quantity; another uses a currency value. The Bitcoin price has changed. The software offers choices, but it does not decide which choice fulfills the merchant’s obligation.
Consider a hypothetical $1,000 purchase paid with 0.01 BTC when the illustrative rate was $100,000 per BTC. By the time the refund is considered, an illustrative rate is $125,000 per BTC. The figures are invented to show the calculation. They do not represent current prices, an agreed policy, or a conclusion about what this customer is entitled to receive.
Retrieve the contract, checkout disclosure, invoice, payment evidence, and cancellation request. Identify whether the commercial price was expressed in dollars, Bitcoin, or another measure, and what the accepted terms say about refunds. The relevant merchant and customer rules need review. Settlement characteristics do not remove contractual duties or every source of dispute.
Confirm the reason and scope of the refund. Is the entire order canceled, only part of it, or is the merchant resolving another issue? Has any service already been delivered? Who has authority to approve the outcome? The calculation should follow an established decision about the obligation, rather than become the mechanism for deciding it.
Preserve the original record. A refund does not make the initial payment vanish, and changing an invoice to zero is not a complete audit trail. The business should be able to explain the original sale, the reason for the later adjustment, and the separately initiated outgoing payment. That matters to support, accounting, and any later review.
If the terms are unclear, escalate the question before choosing the most convenient software option. A price movement can make an ambiguity visible, but the ambiguity existed earlier. Use the case to improve future disclosures after the current customer has been handled under the appropriate obligations and authorized process.
Compare the calculation bases without declaring one universal rule.
Returning the original 0.01 BTC would transfer a quantity worth $1,250 at the later illustrative rate. Returning the original $1,000 value at that same rate would require 0.008 BTC. A policy using another specified conversion basis could produce another quantity. These are mathematical comparisons, not a menu of remedies the merchant may freely impose.
Write the approved basis in words before calculating. For example, the decision might refer to a specified currency amount converted using a defined rate source and time, if that is the appropriate reviewed obligation. Identify rounding, fees, and any permitted deductions explicitly. Do not hide a material deduction inside a net amount that the customer cannot reconstruct.
A rate source and a rate timestamp are separate inputs. Record both, together with the calculation and approver. If the refund is not processed promptly, decide under the applicable policy whether the quantity remains fixed or requires another calculation. The customer should not receive one explanation while the operator silently uses a different time basis.
Test the reverse price movement too. At an illustrative $80,000 per BTC, returning a $1,000 value would require 0.0125 BTC, while the original quantity remains 0.01 BTC. This shows why the policy must be clear before a dispute. A rule chosen only after seeing which direction benefited the business is difficult to explain credibly.
Keep partial refunds equally explicit. State the approved commercial amount or proportion, how it relates to the original order, and how the payment quantity is calculated. Do not infer that half of a service always means half of every fee or cost. The actual contract and reviewed remedy determine the calculation.
Give the accountant the calculation and its basis, rather than asking support to select a tax treatment. The accounting and tax consequences depend on the merchant’s facts and relevant jurisdiction. The refund worksheet should preserve the evidence needed for that work without presenting a hypothetical price change as a universal gain or loss result.
| Basis | At illustrative $125,000/BTC | At illustrative $80,000/BTC | Required decision |
|---|---|---|---|
| Original quantity: 0.01 BTC | 0.01 BTC | 0.01 BTC | Does the reviewed obligation use this quantity? |
| Original dollar value: $1,000 | 0.008 BTC | 0.0125 BTC | Which rate source and time apply? |
| Specified policy basis | Calculate from approved terms | Calculate from approved terms | Are the terms applicable and clearly disclosed? |
| Fees or deductions | Record separately | Record separately | Are they permitted and communicated? |
Confirm where the refund should go.
The original payment’s sending address may not be a usable refund destination. The customer may have paid through an exchange or another service, and the transaction can contain information that does not identify an address at which the customer can safely receive the refund. Do not automate a return based solely on the visible source of the original payment.
Use the merchant’s approved recipient-confirmation process. Identify the customer through the existing order and support relationship, then obtain receiving instructions through an appropriate secure method. Check the asset and network explicitly. A destination intended for a different network is not made correct by using the same asset label in a message.
The current BTCPay refund workflow uses a claim and payout process that allows the customer to supply a destination. That upstream capability is useful, but the merchant must verify its own configured methods, permissions, and review process. An available menu item is not proof that the deployment has tested the intended refund path.
Treat a change of destination as a material change. If new instructions arrive after approval, use the agreed verification procedure before processing. Record who supplied them, how the request was authenticated, and which version was approved. Avoid allowing a late email or chat message to override a verified destination without review.
Ask only for the information needed. Support does not need a customer’s seed phrase, private key, exchange password, or unrestricted account history. If the customer cannot provide an appropriate destination, keep the case open and explain the next review step. Do not promise recovery or compatibility that has not been established.
For a business customer, clarify who is authorized to provide instructions and whether the receiving arrangement matches the approved refund. The destination may belong to a business account, an individual, or another service. The relevant process should handle those facts rather than assuming that anyone who knows the invoice number can redirect the money.
Authorize the outgoing payment and track its actual state.
Separate the commercial refund approval from the technical payment approval. The first establishes what the business has agreed or is required to return. The second confirms that the proposed outgoing transaction matches that decision and the approved destination. Depending on the merchant’s controls, different people may perform these functions.
Record an approval limit and escalation route for unusual cases. A support agent authorized to explain the process may not be authorized to approve a large payout. The system should make that distinction visible before the outgoing payment is prepared.
The operator should check amount, asset, network, destination, and relevant fees against the approved record before signing or dispatching. Use the actual wallet and provider security process. This article is not an instruction to expose keys or bypass an approval because the original customer payment is already confirmed.
Record the stages honestly. Refund approved, claim created, customer details supplied, payout authorized, transaction broadcast, and payment completed are different milestones. BTCPay’s refund documentation itself distinguishes creating the refund from processing and confirming the payout. The customer message should reflect the current stage rather than announce completion at the first click.
Handle uncertain dispatch carefully. If the provider or wallet request times out, investigate whether the outgoing payment exists before sending again. A second refund can be as consequential as a second charge. Preserve the attempt reference and use the supported recovery process or authorized manual review to establish the outcome.
Link the completed payment to the original order and refund case. Keep transaction references and completion evidence in the record, with suitable protection for customer information. If a fee differs from the estimate, record the actual result and any required accounting review. Do not silently alter the approved customer amount to make the operator’s worksheet balance.
If the customer reports non-receipt, check the outgoing transaction and destination against the approved instructions. A confirmed transaction is relevant evidence, while a receiving service may have its own process for crediting the customer. Explain what the merchant can verify and what remains to be investigated without claiming certainty about a third-party account.
Build a refund file the next person can reconstruct.
The audit trail should begin with the original order and finish with the actual outcome. Include the customer request, relevant terms, approved remedy, calculation, rate evidence, destination confirmation, payment authorization, transaction reference, and final status. Each item answers a different question. The file should not rely on one support person’s memory.
Use a refund register that prevents duplicate action. A repeated customer message should reopen the existing case, not create another payable request by default. If several partial refunds are appropriate, the system should show their cumulative amount and relationship to the order. Staff need to see what has already been approved and completed before adding another action.
Reconcile the refund with the source records and accounts. Preserve the original gross payment and record the later movement separately under the accountant’s instructions. Distinguish network fees, provider charges, and any reviewed customer deduction. A wallet balance change alone cannot explain the commercial reason or the correct accounting treatment. For US federal tax records, the IRS says a business may use any system that clearly shows income and expenses, and must keep records as long as needed to prove the income or deductions on a return. That guidance does not decide what a Bitcoin refund must repay.
Test the process with synthetic or approved test evidence before relying on it for a new deployment. Include a changed destination, repeated request, lost payout response, and unclaimed refund. Confirm that the business can identify the state and responsible person in each case. Software capability is a starting point; observed behavior establishes whether the installed workflow supports the policy.
Review the customer-facing terms and checkout copy after the case. They should explain the actual refund basis and process accurately, subject to the applicable rules. Do not promise instant refunds if the process includes approval and confirmation, or claim that all payments are non-refundable merely because they use Bitcoin.
For BitSettle, confirm the merchant-specific scope, supported methods, and operational responsibilities in writing. A payment integration does not establish a universal refund service or an agreed response time. A useful implementation makes the refund decision, approval, and evidence manageable for the business while preserving the distinction between its obligations and the software used to carry them out.
The whole picture
The Bitcoin Lawyer take
Work out which amount the merchant owes before opening a new payment instruction. Show the customer the agreed currency, the calculation, and any rate used.
Verify the destination through the approved channel. Link the outgoing payment and its authorization to the original order so the bookkeeper can explain both sides.


