Chargeback Reasons: Why They Happen and What's Preventable
Chargebacks happen for three kinds of reasons. The cardholder didn't recognize the charge, didn't get what they paid for, or is disputing a purchase they made.
I've watched my own customers file chargebacks on orders I know they received. It reframed the whole problem for me. Most of what merchants call fraud is just a customer who forgot.
Which reason you're facing decides whether an alert could have stopped the dispute.
Key takeaways
- Sort every dispute into one of three reasons before you respond.
- Read the reason code, because it overrides what the customer said.
- Watch code 10.4 first, at 11.1% of our coded alerts.
- Code 13.2, forgotten subscriptions, runs 8.5% of our coded alerts.
- Refund the catchable reasons early, since alerts reach them pre-dispute.
- Fix product complaints at the source, because no alert intercepts them.
Know which of your reasons were preventable. Our chargeback alerts reach the catchable ones first.
What are the most common chargeback reasons?
Customers file chargebacks when they don't recognize the charge, didn't get what they paid for, or are disputing a purchase they made. That third one is friendly fraud, and those three cover almost everything you'll see.
Each reason gets a numbered dispute reason code. An alert catches only some of those codes before they turn into a chargeback.
The code is the part that matters to you. Card networks make the issuing bank put a numeric code on every dispute. That code decides which evidence the network will accept.
Our full breakdown of chargeback reason codes lists every code by network.
The stated reason and the assigned code often disagree.
A customer tells their bank "I never got it" and you still get a fraud code. Banks sort complaints by their own rules. Answer the code you received.
That gap has a practical cost. The evidence that wins a fraud code is proof the cardholder authorized the purchase, while the evidence that wins a delivery code is proof the parcel arrived. Send the second when you were given the first and you lose a case you had the records to win.
You'll see the code before you have to respond. It arrives with the dispute notice from your processor, alongside the amount and your response deadline. Run it through our reason code lookup to confirm what it means before you draft a response.
The 9 reasons chargebacks happen (and which you can prevent)
Damaged goods, unauthorized charges, and forgotten subscriptions cause most disputes, and each of the nine reasons has its own fix. The full set:
- Damaged or defective goods: The item arrived broken or unusable.
- Unauthorized transaction: The cardholder says they never approved it.
- Free-item abuse: The customer disputes to keep the goods and the money.
- Household purchase: Someone in the cardholder's home used the card.
- Wrong amount charged: The bill didn't match what the customer agreed to.
- Affiliate or referral fraud: A partner sold with a claim you never made.
- Never delivered: The customer paid and nothing arrived.
- Misleading description: The item didn't match the listing.
- Forgotten subscription: A renewal charged before the customer cancelled.
Each reason has a different fix.
1. Goods arrived damaged or defective
The customer got the product and it was broken, faulty, or unusable. They argue the item didn't match what they paid for. The bank treats that as a product complaint.
Photograph every outbound order at the packing station and file the image under the order ID. When a customer claims damage, you either see it in your own photo, or you hold dated proof the item left whole.
Your photo can't settle damage in transit. The item left you intact and arrived broken, so your evidence and the customer's are both honest.
File the courier claim and refund the same day, because the dispute costs you more than the parcel did.
An alert won't save you here. The customer wants the item fixed or replaced, so refunding the charge leaves the complaint standing.
2. A transaction the cardholder didn't authorize
The cardholder says someone made this purchase without their permission. This code covers stolen-card fraud, and it covers a customer who genuinely doesn't remember buying from you.
Turn on 3D Secure for card-not-present orders and run AVS and CVV checks at authorization.
On approved transactions, 3D Secure moves the fraud liability to the issuer, which takes the chargeback off you entirely.
This reason tops our own alert data. In our dataset, Visa code 10.4, fraud in a card-absent environment, is the biggest specific code at 11.1% of alerts with a recorded code. Our Visa coverage runs deeper than our coverage of other brands.
An alert catches this one on orders that skipped 3D Secure. The cardholder wants the charge gone, and a refund gives them that before the bank files.
3. The customer wanted a free item
The customer disputes a charge for an order they received, hoping to keep the goods and get the money back. They usually file it as "never arrived" or "not as described," because those claims are the hardest for you to disprove.
Ask for a signature on delivery above a set order value. Pull your average dispute cost from last quarter's chargeback fees, then set the threshold where that cost passes your courier's signature surcharge.
A signed delivery record answers a "never received" claim head on.
For digital goods, build the delivery trail yourself. Log the download or login timestamp, the IP, and the account email against the order. Networks accept that set as proof of delivery.
Whether an alert catches this depends on how the customer filed. An unrecognized-charge claim reaches you early, and an undelivered-goods claim goes straight to the bank.
4. A friend or family member made the purchase
Someone in the cardholder's household used the card, and the cardholder disputed the charge without recognizing it. This one is friendly fraud, meaning the purchase was real and the account holder is the one filing.
Refund a first-time case and move on. The sale was real, so the dispute looks winnable, but winning it means proving who held a card inside someone else's home.
A repeat filer is worth fighting. A second or third dispute from the same cardholder stops looking like a household mix-up.
Answer with the prior order records for that cardholder, including dates, shipping addresses, and device or IP if you capture them. A pattern of delivered orders to the same address answers the household claim.
An alert catches this one reliably. The cardholder files it as a charge they don't recognize, which is the exact complaint a refund closes.
5. The wrong amount was charged
The customer was billed an amount they never agreed to. A duplicate charge, a tip added twice, or a surprise currency conversion all produce this claim.
Check your settlement file against your order file daily and refund the mismatches before the customer finds them. Most duplicate charges show up on your side days before they reach a statement.
Authorization holds produce this claim through no fault of yours. A pending hold sits beside the settled charge and reads as a double bill, even though only one will ever clear.
Flag that on the order confirmation and you stop the call before it reaches the bank.
An alert catches this one. The customer wants the amount corrected, and a refund of the difference does exactly that.
6. Affiliate or referral fraud
An affiliate drove the sale using a claim you never made, and the customer disputed once the product didn't match the pitch. The complaint is about the promise, but the chargeback still lands on your merchant account.
Read your top affiliates' actual landing pages once a month, and cut any partner running a claim your product doesn't support.
Watch for a sudden volume spike from one affiliate, since that pattern usually shows up before the disputes do.
Hold commission until the refund window closes. An affiliate who's already been paid stops caring what happens next. A 30-day clawback means a bad sale costs them too.
An alert won't help much here. The customer is disputing what they were promised, so the argument survives the refund.
7. Goods or services were never provided
The customer paid and nothing arrived. Sometimes that's a real delivery failure, and sometimes it's friendly fraud dressed up as one.
Send tracking on dispatch and again on delivery. A customer who can see where their order is rarely calls their bank first.
Delivered-but-missing is the version you answer with the scan alone. The parcel scanned as delivered and the customer says it never arrived, which happens with apartment blocks and parcel theft.
Send the tracking record anyway, because networks accept a delivery scan to the cardholder's address as evidence.
An alert won't reach this one in time. A delivery dispute needs your evidence, and a refund window doesn't supply it.
8. The product was misleadingly described
What the customer got didn't match what your listing promised. Color, size, materials, and compatibility cause most of these.
Photograph the exact variant you ship rather than a manufacturer render, and put the measurements in the listing body. When the listing and the parcel agree, the customer has no claim.
Suppliers change specifications without telling you. A component swap turns an accurate listing into a wrong one overnight.
Check the listing against a real unit whenever you reorder.
An alert won't stop this one either. The customer is arguing about the product, and paying them back doesn't settle that.
9. The customer forgot to cancel a subscription
The subscription renewed, the customer hadn't planned on it, and they disputed the renewal charge instead of cancelling. This is the most preventable reason on the list, and it maps to Visa code 13.2, cancelled recurring transaction.
Email a renewal reminder three days before each charge and put a working cancel link in it. The customers who dispute a renewal are almost always the ones who didn't see it coming.
Put your brand name on the renewal descriptor, not your legal entity name.
An alert catches this one, and it's the cleanest case of the nine. The customer wants the renewal undone, which is what a refund does.
A customer who knows your brand at checkout may not know it twelve months later on a statement line. An unrecognized renewal gets filed as fraud instead of a cancellation.
Our guide to billing statement descriptors covers what to put in yours.
Which of these reasons can a chargeback alert actually stop?
An alert stops the reasons about a charge the customer wants undone, and misses the ones about the product itself.
Alerts work off the reason code. Ethoca and Verifi hand you the issuer's complaint early, under the code the issuer would file. A refund closes the ones that are only about the money:
The catchable reasons are also the common ones. In our dataset, Visa code 13.2 is about 8.5% of coded alerts.
Coverage is where alerts fall short. They run deep on Visa and Mastercard and thin on Amex, JCB, and Discover.
A catchable reason on an Amex card can still reach you as a chargeback.
Turn alerts on for the reasons marked yes, then set auto-refund to clear them early.
Chargeback alerts are the first thing to switch on.
These fall under 3 kinds of chargebacks
The three categories are friendly fraud, true fraud, and merchant error. Each one sets how hard you should push:
- Friendly fraud. Worth a rebuttal, because the sale was real and you can prove it.
- True fraud. Rarely worth fighting, since the cardholder genuinely didn't buy anything.
- Merchant error. Costs you twice if you fight it, once in the dispute and once in the process you left broken.
Telling the first two apart is the hard part, and our comparison of friendly fraud vs. true fraud sets out the signals.
A "goods not received" claim can be a real delivery failure or friendly fraud wearing one. You often can't tell until you pull the tracking.
Our guide to the three types of chargebacks goes deeper on each one.
Treat the category as your starting frame for triage.
The split matters most when you're deciding where to spend time. Merchant error is the only category you can drive to zero, because you control the double-billing, the descriptor, and the delivery promise. Friendly fraud you can only ever reduce, since the customer's behavior sits outside your process.
That's the case for sorting disputes by category monthly rather than fighting them one by one. A month where merchant error climbs points at something you broke. A month where friendly fraud climbs points at a gap between what customers expect at checkout and what lands on the statement.
How we sourced our data
The reason-code figures in this article come from anonymized, aggregated dispute-alert data across merchants on the Chargeback.io platform. They describe our own alert volume rather than the payments industry.
We counted total alerts in each reason-code group. Each share above is measured against the alerts that had a recorded code.
Our Visa and Mastercard coverage runs deeper than our coverage of other card brands. These shares over-represent both.
FAQ
Who usually wins chargeback disputes?
According to Chargebacks911's Chargeback Field Report, the average merchant win rate is around 45% of disputes represented. Merchants get the money back in about 18% of cases, so a win and a recovery are two different outcomes.
Is a weak-looking chargeback still worth fighting?
Yes, when the reason code you received is one your evidence directly answers. A weak-sounding customer story still gets sorted into a code, and the code decides whether your evidence qualifies.
Do credit and debit cards have different reasons?
Credit card disputes cover more reasons, including billing errors and credits never issued, because the Truth in Lending Act protects those cardholders further. Most debit disputes are about a charge the cardholder didn't authorize.
Can I prevent a chargeback after it's been disputed?
No, once the issuer files the chargeback, prevention is over and your only route is a dispute response. Alerts work in the window before filing, which is why the reason and its code decide what's still possible.
