Reasons Chargebacks Get Denied and What to Do Next
A credit card dispute gets denied when the evidence doesn't prove what the reason code requires, the deadline passed, or the transaction never qualified. A denial can mean you won or that your own response failed, depending on whose filing got denied.
When I worked chargeback support, most of the disputes merchants lost were winnable. They'd answered what they thought the customer meant, when the reason code asked something narrower. Read a denial correctly and you'll know whether the case is closed or coming back.
Why do chargebacks get denied?
A chargeback or dispute gets denied when the evidence fails to prove what the one reason code on the filing requires. Denials trace back to that code rather than to one shared cause. Two merchants can send equally thick packets and get opposite outcomes.
Every code asks its own narrow question, and the issuer weighs the case against that question alone. Evidence that wins under one code loses under another, whatever what a chargeback is suggests about the money at stake.
That's why the denial notice matters more than the dispute did. It names the code the issuer actually ruled on.
Can a chargeback be denied?
Yes, and it works both ways. An issuer can deny a cardholder's dispute, and an issuer can reject the response you file against a chargeback. Each denial means the other side wins that round.
A denial rarely closes the case for good.
Where it goes next depends on the network's rules and how much of the eligibility window is left. A second-cycle chargeback is the issuer's second attempt after your response. Pre-arbitration and arbitration follow when neither side accepts that outcome.
Some codes have no escalation stage after a denial. Certain fraud claims end there, and the case simply closes.
The full list of reasons a chargeback gets denied
Denials come from an evidence gap, a filing error, or a transaction that never qualified:
- Insufficient or missing evidence. The records the filer submitted didn't prove the one specific fact the reason code actually asked about.
- Wrong or mismatched reason code. The evidence answered a different question than the one the issuer actually tested against.
- Filed after the deadline. The case arrived outside the card network's filing window, so nobody ever read the evidence.
- Merchant already refunded the transaction. The money had already gone back to the cardholder before the dispute resolved.
- Dispute doesn't meet the reason code's conditions. The transaction itself never satisfied the qualifying requirements that code carries.
- Cardholder never contacted the merchant first. A required resolution step got skipped before the dispute was filed.
- Cardholder broke the issuer's own dispute rules. The filing skipped a procedure the cardholder's own bank requires.
- Suspected dispute abuse or repeat filing. The filing pattern looked like abuse rather than a genuine complaint.
The table below adds whose gap caused each one and which bucket it falls in:
The evidence failures come first.
1. Insufficient or missing evidence
A dispute fails on evidence when the records submitted don't prove the specific thing the code asks about.
This is the most common denial, and the easiest to misread, because a thick packet feels like strong evidence. The issuer checks whether one specific fact is documented, however many screenshots surround it.
Each record proves one thing and stays silent on the rest:
The gap is often a record nobody kept. Capture signed delivery on high-value orders now, because no amount of care later produces that proof.
2. Wrong or mismatched reason code
A mismatched code gets denied because the issuer only tests the case against the code on the filing, whatever the real story was. A dispute reason code, also called a chargeback reason code, is the network's label for what the cardholder claims went wrong.
Say a customer files a fraud code over a charge they made but didn't recognize. The real problem is your billing descriptor.
The issuer is now testing authorization, so your only winning evidence proves the cardholder authorized the charge. Quality-of-service records lose a case you could have won. Our guide to chargeback reason codes sets out what each family requires.
3. Filed after the deadline
A late filing gets denied on procedure before anyone reads the evidence. Every network sets a filing window from the transaction or delivery date, and a case submitted past it is rejected on those grounds alone.
The same rule cuts both ways. Your own response carries a deadline too, and missing it forfeits a case you would otherwise have won.
4. Merchant already refunded the transaction
A completed refund can give you grounds to challenge the dispute for the amount already returned. It doesn't automatically close the case. Submit the refund amount, date, and confirmation through your processor before the response deadline.
The refund did the job the dispute was filed to do, so no party here made a mistake.
Timing decides whether this closes cleanly. A refund issued before the chargeback posts usually stops the case. A refund that lands after the chargeback moved the funds can pay the customer twice, which our chargeback vs. refund breakdown covers as the double refund problem.
5. Dispute doesn't meet the code's conditions
Some codes carry qualifying conditions the transaction itself has to satisfy, and a case that fails them is denied whatever the evidence shows. A code may require a minimum amount, a specific transaction type, or a card-absent environment.
Pull the code's conditions from your acquirer or the network's rules. That costs a minute and settles whether a case is worth building at all.
6. Cardholder never contacted the merchant
Several codes require the cardholder to try resolving the problem with you first, and skipping that step is grounds for denial. The network treats a dispute as the escalation path that opens once you've had a chance to fix it.
So being easy to reach pays twice. Put a support email and phone number on the order confirmation and the billing descriptor page.
The issuer denies disputes that skipped you, and customers who do reach you often take the refund instead of filing.
7. Cardholder broke the issuer's own rules
Beyond network rules, each issuer runs its own filing procedure, and a cardholder who skips a required step gets denied by their own bank. Banks ask for a written statement, a signed affidavit, or a response by a stated date.
You never see this happen. The case closes at the issuer, and the outcome notice is the first you hear of it.
8. Suspected dispute abuse or repeat filing
An issuer denies a dispute when the cardholder's filing pattern looks like abuse rather than a genuine complaint. That pattern is friendly fraud, where a cardholder disputes a charge they made and received.
Visa puts friendly fraud at around 20% of fraudulent disputes globally, and up to 30% for high-volume online merchants. That share describes how common the behavior is, rather than how often issuers catch it.
Issuers do watch for the pattern, and a cardholder with repeat filings against several merchants starts losing the benefit of the doubt. Enforcement stays inconsistent, though, and behavior that gets caught at one bank clears at another.
Some merchants respond by banning repeat offenders outright.
Deliberate abuse can also cross into chargeback fraud, which carries legal exposure for the cardholder.
What to do when a dispute is denied: the 4-step sequence
Read the reason code, name the evidence gap, check the response window, then escalate or close. Each step needs the answer from the one before it, so the order holds:
- Read the reason code. Find what the code required.
- Audit the evidence gap. Name the one fact your packet never proved.
- Check the response window. Confirm with your processor whether time is left.
- Escalate or close. Weigh the recovery against the cost of arbitration.
Each step below names the action and the trap.
Step 1: Read exactly what the reason code required
Start at the code on the denial notice and write down the one question it asks, because that question is the whole case. Merchants skip this step more than any other, and it's the highest-leverage thing you can do after a denial.
The notice names a code. Confirm what it requires with our reason code lookup tool, or check it against your acquirer or the network's rules. Write it as one plain question, like whether the cardholder authorized this charge.
Everything in step 2 measures against that question.
Merchants get caught here by being sure they already know the answer. When you know what happened on the order, it feels obvious what to send, and that instinct is what produced the denial.
Step 2: Audit what evidence was missing or insufficient
Compare what you submitted against the code's one question and name the specific fact you never proved. The output of this step is a single sentence.
Work backward from the requirement. An authorization code answered with delivery scans leaves authorization unproven, and these are the records that carry it:
- AVS and CVV match results from the authorization
- 3DS authentication data, where the transaction used it
- Device fingerprint or IP history for the order
- Prior undisputed orders from the same cardholder
Sometimes the evidence turns out to exist nowhere. Finding that out closes the case faster than a resubmission would, and it names the record to add to your checkout or fulfillment flow.
Step 3: Check whether the response window is still open
Confirm the remaining deadline in your processor's dispute portal before you build anything. The window varies by network and by code. No single number covers every case, so read it off your notice or ask your acquirer.
Check it early, because the notice may have sat unread for days. An issuer's retrieval request routes through your acquirer, then waits up to 10 days for a response. Routing alone can drain that much of a window.
If the window has closed, stop.
Step 4 becomes a prevention decision instead of a dispute decision.
Step 4: Escalate to arbitration or close the case
Escalate only when the disputed amount clears the cost of arbitration, and close the case when it doesn't. Arbitration carries network filing and ruling fees, paid by the losing side. A small transaction can be worth less than the fight over it.
The transaction value, the evidence step 2 found, and whether that evidence answers the code decide this one. Two of the three pointing the wrong way is a close.
A closed case still pays you back. Add the record step 2 named to your order flow, and the next dispute on that code arrives with its proof already captured.
How chargebacks actually get handled and investigated
Both sides submit evidence inside defined windows, and the issuer reviews the response against the reason code's requirements. If a case reaches network arbitration, the card network decides financial liability. The review is procedural, which is why a code mismatch beats a strong story.
The stages each carry their own deadline:
- The cardholder files the dispute with their issuer.
- The issuer may credit the cardholder provisionally.
- Both sides get an evidence window.
- Unresolved cases go to network arbitration.
Our walkthrough of the chargeback process covers what happens at each stage and who holds the deadline.
Depth varies more than the stages do. A large issuer with automated dispute handling can resolve a simple case in days, while another takes the full window on the same facts.
How alerts prevent a dispute from ever reaching a denial
A dispute that never gets filed has no denial to read, so pre-dispute alerts stop more denials than a better evidence packet. Ethoca (Mastercard) and Verifi (Visa, which runs RDR and CDRN) send a notice while the complaint still sits at the bank.
The alert matches that pending complaint to the transaction in your payment processor. An auto-refund settles it before the issuer rules on evidence.
Denials come out of that ruling, so removing the ruling removes the denial.
We offer alerts across those networks. They prevent up to 91% of chargebacks for merchants on our platform, and our guide to chargeback alerts explains the setup.
Alerts don't cover everything. Some complaints skip straight to a chargeback, and some card brands have thin alert coverage. Those still land as disputes you answer with the sequence above.
Worth a look if you're answering disputes one at a time today. See how our alerts work.
FAQ
Does a denied dispute affect your credit score?
No. Disputes are settled between the cardholder and their issuer, so neither the filing nor the denial reaches a credit bureau.
Is it hard to win a chargeback dispute?
Merchants win a minority of the disputes they contest, because the evidence has to match the cited code exactly. According to Chargebacks911's Chargeback Field Report, the average win rate on represented chargebacks is around 45%.
Can you appeal a denied chargeback decision?
There's no separate appeals process. A denied case continues through the network's own escalation path, which runs to pre-arbitration and then arbitration.
What if my own merchant chargeback gets denied?
Your merchant agreement governs that claim, so the card network's dispute rules don't apply to it. Escalate through your processor's support and account management, and read your agreement's dispute clause for the terms you agreed to.
