TL;DR
- A refund is you returning the money. A chargeback is the customer's bank taking it back.
- A refund costs the sale. A chargeback costs the sale, a $15 fee, and one permanent count on your dispute ratio.
- The ratio is what closes merchant accounts, and winning a chargeback later does not remove the count.
- Refunds usually take two or three days to land. A dispute takes one tap. That gap is where most subscription chargebacks are born.
Who this helps: you refund customers all day and still get chargebacks, and you want to know why the difference matters more than the money.
It has never been easier for a customer to dispute a charge. In most banking apps, it takes one tap. A refund, meanwhile, takes two or three days to reach the customer's account. That gap explains most subscription chargebacks, and closing it starts with understanding what actually separates the two.
What is the difference between a chargeback and a refund?
A refund is you returning the money. A chargeback is the customer's bank taking it back. Both end with the customer holding the same $29, which is why they get confused, and why the confusion is expensive.
A refund involves two parties: the customer asks, you send the money, and the matter is closed. A chargeback involves four: the customer disputes the charge with their bank, their bank pulls the money from your bank, and a case file opens with a deadline for you to answer. There is a third mechanism worth knowing: an authorization reversal cancels a payment before it settles, so the charge disappears with no refund, no dispute, and no record.
| Refund | Chargeback | Auth reversal | |
|---|---|---|---|
| Who starts it | You | The customer's bank | You or your processor |
| Parties involved | Two | Four | Two |
| What it costs | The sale | The sale, plus a fee | Nothing, the charge never settled |
| Counts toward your ratio | Never | Always, win or lose | Never |
| When it can happen | Any time after settlement | Usually 120 days, sometimes longer | Before settlement only |
What does a chargeback cost that a refund does not?
Three things, in increasing order of importance.
First, the fee. Stripe charges $15 the moment a dispute is filed, and it is not returned even if you win. Fighting adds a second $15, returned only on a win. Some processors charge $50 or more.
Second, the process. A refund is finished the day you send it. A chargeback is a case with evidence requirements and a decision that takes weeks, and every case consumes support time whether you win or lose.
Last, and largest, the count. The card networks count a chargeback against your account the day it files. A refund is counted nowhere. That single asymmetry is why the rest of this guide exists.
Why does the ratio matter more than the money?
Because the money is bounded and the ratio is not. Visa sums every merchant's disputes and fraud reports into one ratio, and under VAMP, 1.5% of transactions is where it starts treating you as a problem. Cross the line and you enter a monitoring program. Stay over it and the merchant account itself is at risk, and that account processes every future payment from every customer you have. A chargeback costs you $44 once. The count it leaves behind is working against a threshold forever.
The count is also unforgiving in a way the money is not. Win the dispute months later and your $29 comes back, but the count stays, because the networks measure how often your customers dispute, not how often they were right.
Why is this a race for subscription businesses?
Because for a subscription business, most disputes and most refunds start from the same event: a customer surprised by a rebill. From that moment, the refund and the dispute are racing, and the dispute is faster.
One example makes the timing concrete. Maya is surprised by a $29 rebill and emails support on Monday. Your team agrees to refund her the same day, and the refund enters a queue that takes two or three days to land. On Tuesday night, Maya checks her banking app. The $29 is still there, and next to it is a dispute button that takes one tap. Nobody in that story did anything wrong. The refund was simply slower than the dispute, and the label on the $29 was decided by hours.
How do you stop disputes from becoming chargebacks?
Three moves, in order of how much they save you:
- Refund the same day, and say when the money lands. A written arrival date is what keeps a customer's finger off the dispute button while the refund is in transit. Most lost races are refunds that sat in a queue, the exact failure our guide to 13.6, credit not processed, covers.
- Let alerts cover the customers who never email you. Many go straight to the bank. Chargeback alerts catch the dispute there: RDR and CDRN let you refund before a chargeback files, and disputes resolved that way stay out of the VAMP dispute count. An alert is machinery for turning chargebacks into refunds.
- Shrink the number of surprised customers. A cancellation flow that works instantly and a statement line customers recognize mean fewer people ever open the banking app angry.
A chargeback counts toward Visa's monitoring thresholds the day it is filed, and winning it later does not remove the count. A refund, including one issued through an alert before the chargeback files, never counts at all. That asymmetry is the entire strategy.
FAQ
Is a chargeback the same as a refund?
No. Both return money to the customer, but a refund is initiated by you and settled between the two of you, while a chargeback is forced by the customer's bank and arrives with a $15 fee and a case file. The lasting difference: refunds never count against your dispute ratio, and chargebacks always do.
Does a refund prevent a chargeback?
Usually, if it arrives in time. A customer who already has their money back rarely calls the bank. But a refund that is still in the processing queue when the customer disputes does not undo the dispute, which is why refund speed matters more than refund policy.
Can a customer file a chargeback after being refunded?
Yes, usually because the refund and the dispute crossed in transit. When that happens, your refund becomes your evidence: showing the credit was already processed typically closes the case quickly, and banks catch many of these double requests on their own.
What is the difference between a chargeback and a reversal?
A reversal is the umbrella term. It covers authorization reversals, which cancel a payment before it settles, refunds, which you initiate after settlement, and chargebacks, which the bank forces. Of the three, only chargebacks count toward the ratios card networks monitor.
Do chargebacks cost more than refunds?
Always. A refund costs the sale, and processors generally keep the original processing fee. A chargeback costs the sale, a $15 fee at Stripe and more at some processors, a second $15 at Stripe if you fight it, returned only if you win, and a permanent mark on your dispute ratio, which is the expensive part no invoice shows.
Facts checked against Visa's dispute rules and Stripe's published fees. Last reviewed September 1, 2026.
