Chargeback vs. Refund vs. Reversal: The Real Differences
A chargeback is one your customer's bank makes without your approval, while a refund is one you choose to issue. A reversal is the general term for either.
Across the two Shopify stores I ran, I cut my own chargeback rate before I ever touched a dispute, by fixing the billing descriptor and turning on alerts.
Mixing up the two is the most common mistake I see merchants make, and it costs them the chance to stop the dispute while they still can.
Key takeaways
- Expect a $15 to $50 processor dispute fee on top of the lost sale.
- Budget $600 for a Visa arbitration case-file ruling as of April 2025.
- Refund the same day a complaint lands, before the bank rules.
- Check your reason code against 4 valid groups and 1 abuse pattern.
- Watch who starts the reversal, because that decides who rules on it.
The cheapest dispute is the one a bank never files. See how alerts work.
Chargeback, refund, or reversal: what's the difference?
A chargeback is a reversal the customer's bank forces on you, a refund is a reversal you issue yourself, and a reversal is the umbrella word for both. All three end the same way, with money back in the customer's hands.
With a chargeback, the customer goes to their issuing bank, and the bank pulls the funds and rules on the outcome. A refund brings the customer to you instead, so you decide.
Because of that, a refund costs you less, lands sooner, and leaves the decision in your hands.
Timing turns one into the other. Ignore a refund request for a week and the same money still leaves your account, but now there's a fee attached.
Chargeback vs. refund vs. reversal, compared
A chargeback, a refund, and an authorization reversal differ on who starts them, who controls them, what they cost you, and how fast they land.
Every one of those differences comes down to how much of the outcome you still control:
Who started it, and who's in control
A chargeback starts with your customer's bank and the bank keeps control, while a refund starts with you and you keep control from beginning to end. Every cost difference follows from that.
When a customer disputes a charge, the issuing bank takes your money first and asks questions second, so you find out after the funds are gone.
Your only move is a dispute response, and even then the bank decides whether your evidence is enough.
With a refund, you press the button, the money moves, and nobody rules on anything.
How serious each one is for the customer relationship
A chargeback usually ends the customer relationship, a refund often survives it, and a reversal is over before the customer thinks much of it. How bad it gets depends on which party ended up ruling on the complaint.
A customer who files a chargeback has already taken the complaint to their bank.
In my experience working merchant support, that decision is rarely reversible, because they've written you off before you hear about it.
A refund means the customer still trusted you to fix it. Reversals barely register, since most cancel a pending charge the customer never saw settle.
The exception is worth knowing. Plenty of chargebacks come from customers who read an unfamiliar name on their statement and assumed fraud.
They're still your customers. Set the descriptor to the store name they saw at checkout, add a support number, and most of them recognize the charge instead of disputing it.
Who pays? Cost and loss by party
You pay for a refund and for a chargeback, and in arbitration the losing side pays. Every escalation stage hands the case to someone new who has to rule on it, and you pay for their time.
A refund stays between you and your customer, so nobody bills anyone. A chargeback brings in your processor and the card network, and both handle paperwork and a ruling.
BigCommerce puts processor dispute fees at $15 to $50. Push a dispute all the way to arbitration, and Visa's case-file ruling fee rose from $500 to $600 in April 2025. The losing side pays it.
Our chargeback fee guide breaks the amount down by processor:
A dispute closed before it becomes a chargeback carries none of these fees.
A pre-dispute alert from Ethoca, RDR, or CDRN reaches you while the complaint sits with the bank, early enough to refund and close it.
Our ROI calculator turns your dispute volume into a dollar figure.
What a chargeback does to your account
A chargeback counts against the dispute ratio your card network monitors, and a refund counts for nothing. Fees show up on an invoice. The ratio decides whether you keep your processing.
Card networks track disputes as a share of your transactions and act once that share crosses a published line. Visa tightened that line in April 2026, and our guide to the average chargeback rate carries the current thresholds by network.
Cross one and the pricing changes shape. Visa charges enrolled merchants $8 per transaction once flagged as fraudulent or disputed, so you stop paying per dispute and start paying on volume.
A first breach in any rolling twelve months comes with a three-month grace period. Treat it as the window to fix whatever is driving the disputes.
Refunds sit outside all of it. Refund a customer and the money leaves, but no ratio moves and no threshold gets closer.
How many parties each one involves
A refund runs between two parties, you and your customer, while a chargeback pulls in four. The four are the customer, their issuing bank, you, and your acquiring bank.
Each added party is one more party that can say no, and that is why the timelines differ. A refund needs one decision from one party, so it clears on your processor's normal settlement schedule.
A chargeback needs the issuing bank to rule and your acquirer to pass that ruling along. You respond inside a deadline none of them set around your calendar. A formal chargeback can run for months.
Your leverage differs too. In a two-party reversal you are one of the two deciders, and in a four-party dispute you are the only one whose money is already gone.
What is a chargeback?
A chargeback is a transaction reversal your customer's issuing bank forces onto your account after the customer disputes the charge. The money leaves before you've said a word.
The bank runs the decision. It reads the cardholder's claim, takes the funds, and only then gives you a window to respond with evidence.
That response is a dispute response, sometimes called representment, and it asks the same bank to change its own mind. Our fuller guide covers what a chargeback is end to end.
A dispute and a chargeback are two different stages of the same event.
Chargeback vs. dispute: what's the difference
A dispute is the customer's complaint to their bank, while a chargeback is the action the bank takes because of that complaint. One is a question, the other is a withdrawal.
The sequence runs in that order. Your customer calls their issuer and disputes a charge, the issuer looks into it, and if it sides with the cardholder, it takes your money.
Most disputes die at the question stage, before any money moves.
Prevention tools act during that pause, and we break the two terms apart under dispute vs. chargeback.
What are double refund chargebacks?
A double refund chargeback is when you refund a customer and their bank also charges the order back, so the same money leaves your account twice. The customer ends up paid twice for one purchase.
Your processor and the card network don't tell each other what they've done. Your refund moves on your processor's timeline, while the bank's dispute runs on the card network's clock.
The bank often finishes its ruling without knowing you already paid. By then you've sent the purchase amount once and had it taken again, with the dispute fee on top.
Three steps stop it, and all three have to happen before the bank rules:
- Refund the same day the complaint arrives: A refund that lands after the ruling causes the double debit instead of preventing it.
- Send a dated confirmation naming the amount: Include the descriptor the credit will show, so the customer can match it on their statement.
- Keep that confirmation: If the customer already called their bank, the dated receipt is the evidence that closes the dispute.
Waiting three days to send a refund you already agreed to is how merchants pay twice.
What is a refund?
A refund is a reversal you start and finish yourself, returning your customer's money with no bank dispute involved. You are the only decision-maker in it.
Because you run it, a refund settles on your processor's normal timeline, and nobody charges you to rule on anything. Your processor's settlement window is the only clock, and the cost is the sale itself.
Partial refunds are the version merchants forget they have. Return the shipping, the difference on a damaged item, or one line of a multi-item order. A customer who accepts a partial refund has stopped being a dispute risk on that order.
A refund only gets expensive when the customer can't see it coming.
Agree to one, take days to send it, and the customer reads your silence as a refusal. Their next call goes to the bank.
One limit is worth knowing before you lean on refunds as your whole strategy. Refunding after the bank has already opened a dispute doesn't withdraw the dispute, so you need the dispute closed as well, which is the double-refund trap above.
What is a reversal?
A reversal is any transaction that gets undone, with the funds returned to the customer. You may have issued it, a bank may have forced it, or an authorization may have been cancelled before it settled.
It matters because your processor and your bank both use the word that way. A settlement report will say a transaction was reversed without telling you which path it took.
That vagueness costs you when you reconcile. A month of "reversals" in one column mixes refunds you chose with chargebacks forced on you. Only one of those two is a problem you can fix, so split them before you read the number.
One kind of reversal costs almost nothing.
An authorization reversal cancels a hold before the charge ever settles, so the hold drops off and the transaction never reaches the card network.
The window for that closes at settlement. Once the charge captures and settles, the cheap path is gone and a refund becomes your only way to return the money.
How to tell which one you're looking at
Check who contacted you first, because that single fact separates all three. A message from the customer is a refund request, a notice from your processor is a chargeback, and a hold that vanishes on its own was an authorization reversal.
Four signals settle it in the order you'll meet them:
- The sender. Refund requests come from the customer, while chargebacks come from your processor or acquirer.
- The money. A refund moves nothing until you act, but a chargeback has already taken the funds.
- The reason code. Only a chargeback carries a numbered code, which means a bank has already ruled.
- The deadline. A chargeback notice states a response date, while a refund request carries none.
Your dashboard tells you the same thing faster. Refunds appear under payments or orders as an action you took, while chargebacks land in a disputes section your processor controls.
One case looks like both at once. A customer emails you for a refund and files with their bank the same week, so you hold both notices for one order. That is the setup that ends in paying twice.
Valid reasons for a chargeback
A chargeback is legitimate when the cardholder didn't cause the failure behind it. Card networks sort those failures into four groups:
- Fraud. Someone used the card without the cardholder's permission.
- Product or service not received. The order was paid for and never arrived.
- Not as described. What showed up was materially different from what was sold.
- Processing error. Wrong amount, duplicate charge, or a charge after a cancellation.
Friendly fraud is the fifth pattern you'll meet, and card networks treat it as an invalid claim.
Each network turns its groups into numbered codes, and the code you get decides what evidence your dispute response needs. Our guide to chargeback reason codes has the full list.
When a chargeback isn't valid
Friendly fraud is a cardholder disputing a purchase they made and received, while the four groups above all start with a failure on someone else's side. The paperwork looks the same from your side, which is exactly the problem.
Buyer's remorse is the everyday version. The customer wants out and calls the bank because they expect a better answer there than from you.
Plenty of it is honest confusion, though. A spouse's purchase, a forgotten trial, or a statement line nobody recognizes all get filed as fraud in good faith.
What you do next depends on which one you've got. For a genuine failure on your side, refund it and keep the customer. Friendly fraud leaves you only the dispute response, which needs three things tied to your reason code:
- Delivery confirmation showing the customer received the order
- The terms they accepted at checkout, with the timestamp
- Your support messages about the order, in date order
Put your checkout brand name in the descriptor and email a receipt within the hour, and a chunk of the accidental cases stop happening. Our guide to prevent chargebacks before they happen covers the rest.
FAQ
Why did I get a chargeback instead of a refund?
A refund is the reversal you would have issued, while a chargeback is the one their bank issued for you, so it costs a fee. Customers usually skip you when they don't recognize the charge, or when a refund request goes unanswered.
Is it illegal to keep a double refund?
Knowingly keeping both a merchant refund and a chargeback for one purchase is unjust enrichment. Banks reverse the duplicate credit once they spot it.
Can I file a chargeback over a refused refund?
Yes, a refused or ignored refund request is grounds for a dispute with your card issuer. Keep your written requests and the merchant's replies, since the issuer will ask what you tried first.
Does a chargeback hurt my credit score?
No. Issuers settle card disputes with the card network and never report the outcome to the credit bureaus.
