Chargeback vs Refund: Cost, Control & Your Tax Records

A customer you never heard a single complaint from disputes their $149 subscription renewal with their bank. You find out when the money is already gone. There is a chargeback fee attached, a response window measured in days, and nobody asked your opinion.

That is a chargeback, and it is not the same thing as a refund. Both send money back to the customer. Only one of them leaves you in control.

This guide is written for the merchant, not the cardholder. Most comparisons of chargebacks and refunds cover the payments side and stop there. This one keeps going into the part that outlives the chargeback itself: what a reversal does to the invoice you already issued and the VAT or GST you may have already filed.

Chargeback vs refund: the key differences

The customer ends up in the same place either way. You do not.

Aspect	Refund	Chargeback
Who initiates it	You	The cardholder, through their bank
Who decides the outcome	You	The issuing bank
Typical time to resolve	3 to 5 business days	Weeks to several months
Dispute fee	None	Yes, and often not returned even if you win
Counts toward a monitoring ratio	No	Yes
Effect on the original invoice	Voided in whole or in part	Voided in whole or in part
Document that corrects your records	Credit note	Credit note

Those last two rows are where most guides stop short, and they are the reason a reversal keeps costing you attention after the money has moved. More on that below.

What is a refund, and what is a chargeback?

The refund: you decide

A refund is a reversal you initiate and settle directly with your customer. The money typically lands back on their credit card in three to five business days, your processor charges no chargeback fee for it, and no card network counts it against you.

That makes the refund the cheap outcome, and a clear refund policy is how you steer unhappy customers toward it.

The chargeback: the issuing bank decides

A chargeback starts when the customer skips you entirely and goes to the bank that issued their credit card. The chargeback process pulls in four parties:

• The cardholder files a dispute with their issuing bank.
• The issuing bank reviews the claim, usually gives the cardholder a provisional credit straight away, and notifies the card network.
• The card network routes the dispute to your acquiring bank, which is your payment processor.
• Your acquiring bank pulls the funds from your account and sends you the chargeback notice.

The system is built to favor the cardholder. That is its purpose: consumer protection laws and card network rules both assume the person holding the card is the one who needs defending. Knowing the bias exists is what keeps your decision to fight or fold a commercial one rather than an emotional one.

Every chargeback arrives with a reason code attached, and the code tells you what the customer actually claimed. Most of what a digital business sees falls into three families:

• Outright fraud.
• "I never received it."
• A cancelled or unrecognized recurring charge.

Which family you are in determines what evidence is worth gathering.

How long does each one take?

A refund is over when you say it is: three to five business days and the customer has their money.

The chargeback process runs on the banks' clock, not yours. The notice reaches you within a few days of the customer filing. Your window to respond is set by your payment processor rather than the card network, commonly somewhere between 7 and 30 days. If you contest the case and the issuing bank still finds for the cardholder, it can escalate into pre-arbitration and drag on for months.

Here is the part that matters most for a subscription business: your money sits with the cardholder that whole time, whoever eventually wins. A disputed renewal is a cash-flow event first and an accounting problem second.

What chargebacks and refunds actually cost

A refund costs you the transaction value, and often the payment-processing fee on the original sale, which many processors keep.

A chargeback costs considerably more, in three layers:

1. The dispute fee. Charged by your processor, per case. Fees vary widely, so check your own pricing, and check whether you get the fee back when you win, because plenty of processors keep it either way.
2. The product itself. For digital goods and SaaS there is nothing to recover, no returned parcel to put back into stock.
3. Your own time. Gathering evidence and tracking an outcome you do not control.

Then there is the cost that builds up quietly. Card networks monitor how many of your transactions turn into chargebacks, and they act when the number gets too high.

Visa consolidated its Dispute Monitoring Program and Fraud Monitoring Program into a single Visa Acquirer Monitoring Program, which measures fraud plus disputes against your settled card-not-present transactions. For a merchant in the US, Canada, the EU or Asia-Pacific:

Trigger	Threshold
Flagged as excessive	220 basis points
Flagged as excessive, from 1 April 2026	150 basis points
Minimum events in a month to be enrolled	1,500 fraud and dispute events

That event floor means the program targets real volume rather than the occasional unlucky case. Mastercard runs an equivalent program combining a chargeback count with a ratio, and your acquirer can tell you where you sit against it.

For a subscription business, a climbing ratio is usually a customer experience problem wearing a fraud costume. People who cannot work out how to cancel file a chargeback instead.

Double refund chargebacks

Sometimes the money leaves twice. You refund a customer, and the customer wins a chargeback for the same transaction anyway. You are out the sale twice over, plus the fee.

It happens more often than it should, and rarely in bad faith. A customer files with their bank before your refund has settled, or forgets they already asked you, or the refund and the bank's provisional credit simply cross in the post.

Answer the chargeback anyway, even though you know you already refunded. An unanswered case is a lost one, so submit the refund confirmation as your evidence and let the record show the customer was made whole.

There is an accounting trap here that no other guide seems to mention.

The duplicate payment is a separate amount to recover, not a second reason to adjust the tax on that invoice.

What a chargeback does to your accounting records

Your payment processor marks the case closed and moves on. Your books do not. They still show a completed sale, against an invoice you issued, carrying tax you may have already reported and paid.

Nothing about the reversal corrects that on its own. You issued an invoice, you charged VAT or GST on it, and if the reversal lands in the quarter after the sale, you have already filed a return based on a transaction that no longer exists.

The correcting document is a credit note. Under Article 219 of the EU VAT Directive, "any document or message that amends and refers specifically and unambiguously to the initial invoice shall be treated as an invoice", which is precisely what gives a credit note its standing. It cancels the original invoice in whole or in part and leaves an audit trail tying the reversal to the sale it undoes.

Your entitlement to claw back the tax comes from Article 90 of the same directive: "in the case of cancellation, refusal or total or partial non-payment, or where the price is reduced after the supply takes place, the taxable amount shall be reduced accordingly under conditions which shall be determined by the Member States."

Read that last clause carefully, because it is where a lot of confident advice goes wrong.

Article 90 also lets member states derogate from the reduction where a reversal counts as non-payment rather than cancellation. So the honest version is not "every merchant must issue a credit note and reduce their output tax", it is that the entitlement is settled and the mechanism belongs to each country you sell into.

Timing works the same way. Whether the adjustment sits in the period of the original sale or the period of the reversal is a local rule, and getting it wrong understates one return and overstates the next.

For the mechanics of the document itself, see our guide to what a credit note is and when you need one, and the broader picture on refunds for what reversals mean across your tax obligations.

Doing this by hand for every reversal is where small errors compound. Quaderno issues a credit note against the original invoice whenever a refund or chargeback is processed, so the tax position corrects itself and the audit trail exists whether or not anyone remembered to build it.

When one chargeback covers several invoices

A subscription dispute rarely arrives as a single charge. A customer who decides in August that they never meant to keep paying you calls their card issuer about every renewal still visible on their statement, and the case lands on your desk covering six months at once.

The payments side shows you one dispute. Your records hold six invoices.

That distinction decides how many correcting documents you owe. One credit note per invoice reversed, not one per chargeback. Six reversed renewals means six credit notes, each referring specifically to the invoice it cancels, which is precisely what gives each one its standing under Article 219. The warning further up this guide is about issuing two correcting documents against the same invoice, and it still holds.

Then there are the periods. Each renewal carried its own invoice date, so if the disputed months straddle a filing boundary, one case produces adjustments in two different returns. The chargeback has a single date. The corrections do not.

That gap between one payment event and several records is the same problem payment reconciliation solves at the payout level, where a single deposit routinely covers dozens of invoices.

Where the tax adjustment lands when you sell cross-border

Which return the correction belongs on is decided by how you reported the original sale, not by how the dispute ended.

How you reported the sale	Where the correction goes	Timing
Through the EU One Stop Shop	A later OSS return, set off against what you owe that member state	Within three years of the original return's deadline
Registered locally in the country of sale	That country's own return	Set nationally, under the Article 90 conditions
A US state sales tax return	A deduction from gross sales, with no correcting document involved	The period the refund or credit was issued

For anything reported through the One Stop Shop, you do not reopen the original return. The European Commission is explicit that your member state of identification allows corrections "within three years of the date on which the initial return had to be submitted", and the amount is set off against the VAT you owe that same country in the current period. Our guide to how OSS and IOSS actually work covers which scheme applies to which sale.

US state returns work on a different instrument entirely. Virginia's returned goods rule shows the shape of it: a dealer "may deduct from gross sales any portion of the sales price of tangible personal property returned by a customer provided that such amount has been refunded", claimed on the return for the period the refund went out. Note the wording. That rule is written for physical goods, so what carries across to a digital sale is the mechanism rather than the scope: a deduction on the current return, no correcting document, no amendment, and a different form of words in every state.

One chargeback, two correction systems, if your customers are split across both.

Should you refund or contest the chargeback?

Default to refunding. When a customer is unhappy and the amount is ordinary, a refund costs less than a chargeback, ends in days, and leaves your monitoring ratio alone.

Once a chargeback has landed, you have two real options.

• Accept it when the fee plus your staff time is worth more than the transaction, or when the customer's complaint is fair. Contesting a legitimate claim costs you the fee regardless of outcome, and it wastes hours you could spend on the reason it happened.
• Contest it when the customer received the service and the claim is factually wrong.

For a digital business, the evidence that carries weight is the record of use:

• Login timestamps
• Feature usage logs
• The IP address at signup
• Email receipts
• Your support history with that customer

Notice what is missing there. Shipping confirmation is the first thing most chargeback guides tell a merchant to submit, and a SaaS product has none.

Keep the rebuttal short. Name the reason code, state what you are submitting, and let the records speak. If the issuing bank still finds against you, pre-arbitration exists, but the cost climbs steeply enough to only make sense on high-value transactions.

If chargebacks are structural rather than fixable, moving the liability off your books entirely is an option worth pricing. Our breakdown of the pros and cons of a merchant of record walks through the trade-off.

How to prevent chargebacks

Every chargeback you prevent is one you never have to make that call on. In rough order of how much they pay back:

• Fix your billing descriptor first. The name on the customer's statement has to match the brand they think they bought from. "ACME SOFTWARE" is fine. "SP*BILL8821" is a chargeback waiting to be filed by somebody who genuinely does not recognize it.
• Send an itemized receipt immediately. A surprising share of chargebacks begin as "I don't know what this charge is", and a receipt in the inbox answers that before the bank ever hears about it.
• Publish a refund policy people can actually act on. Make your refund path easier to find than their bank's dispute form, and your customer service easier to reach than their card issuer. Customers who know they can get their money from you generally do not go looking for another way.
• Remind subscribers before you charge them. A renewal notice a few days ahead of the billing date turns a surprise into an expected one. This is the highest-value item on the list for a subscription business. The most common chargeback a merchant like you receives is not a stolen card, it is friendly fraud: somebody who forgot they were still paying you and finds the bank easier to call than your support team.
• Make cancellation self-serve and immediate. Anyone who can cancel in thirty seconds has no reason to involve their bank. A retention flow that traps people generates chargebacks, and the card networks count those against you.
• Keep your transaction records as a habit. The usage logs and timestamps you would need as evidence are only there later if you were already collecting them.
• Use 3D Secure, and understand its limits. When a transaction is successfully authenticated through 3DS, liability for a later fraud chargeback shifts from you to the card issuer. That is worth having, but the shift applies to fraud reason codes only. It does nothing for "I never received it" or for a disputed subscription renewal, which is where most subscription businesses actually lose money.

---

A reversed sale still needs a corrected invoice. When a refund or chargeback comes through Stripe, PayPal or whichever gateway you sell on, Quaderno raises the correcting credit note automatically and adjusts the tax you reported with it. See how Quaderno handles tax-compliant invoicing.