Dispute vs. Chargeback: What's the Difference?
In a dispute vs. chargeback comparison, a dispute is a customer's complaint to their bank about a charge. A chargeback is what happens next, when the bank agrees and pulls the money back from the merchant.
I've fought both sides of that line enough times to know they're not the same problem. Every chargeback starts as a dispute, and most disputes stop before that.
The first time I fought a chargeback, I sent everything and still lost. I hadn't read what the reason code required. That taught me the two are different problems, with different responses.
By the end of this you'll know which stage a notice belongs to, and what to do there.
Key takeaways
- Treat a dispute as the complaint and a chargeback as the forced reversal.
- Visa renamed chargebacks to disputes in April 2018, so both words stuck.
- Check whether money has left your account to tell the two stages apart.
- File accurately as a cardholder, and read the reason code first as a merchant.
- Refund early, because a dispute stopped at stage 2 never becomes a chargeback.
- The April 2018 rename is why your dashboard and acquirer use different words.
Short on time? Get dispute alerts.
Are a dispute and a chargeback the same thing?
They are two stages of one process, where the dispute is the customer's complaint and the chargeback is the bank's reversal that can follow it. From the outside, the money and the paperwork feel like a single event, so people use the words interchangeably.
The bigger reason is that Visa changed its own words. In April 2018, Visa Claims Resolution renamed "chargeback" to "dispute" across its rulebook and systems. Banks, processors, and merchants picked up the new word at different speeds.
So your dashboard says dispute while your acquirer says chargeback about the same case.
What is a dispute?
A dispute is a customer's formal complaint to their card-issuing bank about one charge, filed before any money moves. The customer calls the bank or files in the banking app, names the charge, and says what went wrong.
The issuing bank gets that complaint and investigates it before it tells the merchant anything. That is why a merchant often misses a dispute until it has moved a stage or two. It also explains why the first notice they see already carries a reason code and a deadline.
The word covers more ground than most merchants expect. A cardholder questioning a charge, a bank opening a case file, and a processor flagging a transaction all get called disputes. Only some of them ever reach a chargeback.
A dispute always routes through the bank, which is what gives it a reason code, a clock, and a formal outcome. A refund request goes straight to the merchant, on whatever timeline that merchant sets.
Our chargeback vs. refund breakdown has the three-way comparison with reversals.
What is a chargeback?
A chargeback is the forced reversal an issuing bank runs against a merchant's account after it sides with the customer. The money leaves the merchant and a fee usually lands with it.
The merchant then gets a set number of days to respond.
That reversal is the part merchants feel, so it's worth knowing what a chargeback actually is before your first one arrives.
Dispute to chargeback: how the process moves
A dispute turns into a chargeback in three moves, where the customer files, the bank investigates, then the bank pulls the merchant's funds. Each row below names who acts and what changes hands:
Stage 2 confuses almost everyone. The customer often has their money back while the bank is still deciding. That is why "the chargeback already happened" and "I'm still disputing this" can both fit one case on one day.
Plenty of cases stop at stage 2. The bank can decide the record supports the merchant, or the merchant can refund while the review is open. Either way the file closes with nothing pulled.
Stage 2 does not stay open for long.
Once a chargeback issues, the case moves to representment and arbitration, and the full chargeback process walks those later stages.
How do banks process disputes?
The issuing bank gathers evidence from both sides, then checks whether the cardholder's claim fits the reason code on the case. It rules for whichever side the card network's rules support.
The cardholder says a charge was unauthorized or the goods never came. The bank then asks whether the transaction record backs that up.
So which evidence you send matters more than how much of it arrives.
Each reason code accepts a different proof:
Send the wrong one and you lose a case you could have won.
Banks also work to the card network's deadlines. If you miss the deadline, the bank treats it as though you never replied.
One more thing shapes the case before anyone reads your evidence. The bank often credits the cardholder early in the review, so it moves the money first and settles the question later.
Treat that early credit as the clock starting, and keep building your response.
What should you do: cardholder vs. merchant
A cardholder files accurately and answers the bank's evidence requests, while a merchant acts on the notice by its stage. The cardholder wants the money back and the merchant wants to keep it, so the same case asks two different things of them.
If you're the cardholder
Contact the merchant before you file, then file only if that goes nowhere. A direct refund fixes the problem faster than a dispute does, and it costs the merchant far less.
File accurately when you do file. Claiming you don't recognize a purchase you forgot counts as friendly fraud, and it can cost you the account relationship with your bank.
Keep your paperwork where you can find it:
- The order confirmation email
- The delivery or tracking notice
- Any support replies from the merchant
The bank will ask for them, and a claim with nothing behind it usually fails at review.
The case takes longer than you'd think. Your credit can arrive in days while the decision takes weeks, and the bank takes that credit back if it rules for the merchant.
If you're the merchant
Read the reason code first, then respond to what that specific code requires. Our reason code lookup tool shows which evidence the bank will accept, and matching it beats sending everything you have.
Check whether money has already moved. If it hasn't, a refund can still close the case before a reversal lands. Once the money is gone, you are into a formal response with a deadline.
Then fix what caused it. Set your billing descriptor to the name customers know on a statement, because a customer who can't place a charge calls the bank. Put a support email and live chat on the order confirmation too, so a confused customer reaches you first. Both cost less than the fee on one chargeback.
Watch the deadline as closely as the evidence. Each card network sets its own response deadline, counted from the day the notice issues rather than the day you read it. A late packet loses on procedure alone.
Put the due date in your calendar the day the notice lands.
I lowered my own chargeback rate more by fixing the descriptor than by winning any single dispute.
Dispute alerts work one stage earlier than any of that. An alert reaches you while the case is still a dispute, so a refund at that point usually closes it before a chargeback issues.
We cover Ethoca, RDR, and CDRN, so you hear about a dispute before it turns into a chargeback.
What counts as a valid reason for a dispute?
A dispute is valid when the charge was unauthorized, the goods never came, the item didn't match its description, or the amount was wrong. Those four cover nearly every legitimate filing, and a fifth category covers the rest:
- Fraud: someone used the card without the cardholder's permission.
- Item not received: the order never arrived.
- Not as described: what arrived didn't match what was sold.
- Processing error: a wrong amount, a duplicate charge, or a currency mistake.
- Friendly fraud: a real purchase the cardholder disputes anyway.
Each category maps to its own reason code, and the code sets the deadline and the proof the bank will accept.
The fifth is where merchants spend most of their dispute budget.
When it isn't a valid dispute (friendly fraud)
Friendly fraud is a dispute filed on a purchase the cardholder actually made and received. It looks identical to a fraud claim in the bank's queue, which is exactly why it works.
On my own stores it was nearly always a spouse's purchase, a forgotten renewal, or a statement line nobody knew.
The customer genuinely believes the charge is wrong, which is what makes friendly fraud so hard to argue against after the fact.
FAQ
Why do merchants hate chargebacks?
A chargeback takes the revenue and adds a fee, so the merchant loses more than the sale was worth. Enough of them also push a chargeback rate toward the thresholds that trigger processor monitoring.
Can I go to jail for a chargeback?
No, a legitimate dispute is a consumer right. Deliberately filing a false claim is fraud, and that can carry criminal charges.
Are chargebacks usually successful?
For cardholders, most disputes that reach a chargeback end in their favor. Merchants win a minority of the cases they contest, and the rate swings by industry and by evidence quality.
Can a chargeback follow a refund the merchant sent?
Yes, both can land when the dispute was already filed. Send your refund proof to your processor as soon as the notice arrives.
Where the two stages actually diverge
The dispute stage is the only one where a merchant can still settle the case cheaply, while a chargeback has to be fought or absorbed. So telling them apart decides what the notice on your desk is worth.
It also explains why two people describe one case differently. A cardholder who files today is in a dispute. The merchant reading the notice next week may be looking at a chargeback.
Ask what has happened to the money, and you have your stage.
Set your expectations for the fight with how often merchants actually win.
Our guide to chargeback prevention covers stopping disputes before either stage starts.
