3 Types of Chargebacks: True Fraud, Friendly Fraud & More
There are 3 types of chargebacks, true fraud, friendly fraud, and merchant error, and each one starts somewhere else. A stranger with a stolen card is true fraud. Your own customer disputing a real purchase is friendly fraud, and a slip on your side, like a double charge or a bad descriptor, is merchant error. The type you have decides whether you can prevent it, fight it, or fix it.
I've fought chargebacks on my own stores and lost the first ones, because I treated all three the same way. Sorting a dispute by type is what tells you which ones you can still stop.
Key takeaways
- Sort every dispute into true fraud, friendly fraud, or merchant error first.
- Skip fighting true fraud, because the real cardholder never authorized it.
- Fix merchant error at the source, since a refund beats any dispute response.
- Watch reason code 10.4, at 11.1% of our coded alerts.
- Friendly fraud tops the list, at 44% of merchant-reported chargebacks.
Catch the disputable ones early. Our chargeback alerts reach you before the bank does.
What are the 3 types of chargebacks?
The 3 types are true fraud, friendly fraud, and merchant error, and they split on who made the purchase. A stranger made it, your customer made it, or your own system got it wrong. Every dispute fits one of the three, and the category tells you what to do about it.
The card networks record a numeric reason code instead of these labels. The 3 categories are the standard industry grouping for what those codes have in common. Once you know the category, you know whether to prevent the cause, fight the claim, or fix your process. The chargeback reason codes answer a narrower question, which code the bank filed under.
Our reason code lookup tells you which category a specific code falls under.
The split matters because the three don't share a fix. Two of them start with your own customer, so you can reach that person before their bank does. The third starts with a stranger, and that one you can only stop at checkout.
Treat every dispute the same way and you spend evidence on cases you can't win.
A code alone can point at two categories at once. A "goods not received" code can be a real shipping failure, or friendly fraud dressed up as one. The category starts your triage. Your own records settle it. Check the delivery scan, the login history, and whether anyone from that account contacted support first.
Comparing the 3 types of chargebacks
The three types differ on who made the purchase and who can stop the dispute, so each one gets a different response. Here they are side by side:
- True fraud, where a stranger used the card and prevention happens at checkout.
- Friendly fraud, where your own customer filed and clarity is what stops it.
- Merchant error, where your process caused it and a fast refund closes it.
Each row is a rule of thumb, and the next three sections work through each type in turn. For the individual cardholder behaviours, read the specific reasons behind each type.
1. True fraud
True fraud is a purchase made by someone other than the cardholder, using a stolen card or card data. It's the type most merchants picture when they hear "fraud." It's also the one they see least.
Representment works by proving the cardholder got what they paid for. In true fraud, someone else did. So delivery evidence argues the wrong point, however complete it is. Your one chance came earlier, at the checkout that let the card through.
Say a fraudster buys electronics with a stolen card and ships them to their own address. The cardholder spots the charge weeks later and calls the bank. The money leaves your account with a fee.
You're out the stock too, so you lose more than the disputed amount.
Merchants surveyed by Aite-Novarica Group in 2022 reported stolen-card fraud as their smallest category by a wide margin. Across those merchants, most disputes came from purchases the cardholder made themselves.
2. Friendly fraud
Friendly fraud is a chargeback the real cardholder files on a purchase they made, usually over a charge they don't recognize. The name describes how the dispute reaches you.
Because the cardholder did buy from you, this is the category where you can still step in. You get two windows, one before they call their bank and one while the complaint sits there.
You can spend a dollar stopping these disputes or fighting them, and stopping them is cheaper.
Picture a customer who forgot they were still subscribed, and the renewal hits their card. The billing statement descriptor doesn't match the product name they remember, so they report the charge as unauthorized.
Some of it is deliberate, because a cardholder who knows exactly what they bought can dispute it anyway. Telling the halves apart is what friendly fraud prevention is for. Your own records usually say which one you have. A customer who logged in from their usual device and never contacted support looks confused. A repeat filer who disputes several orders and keeps using the account looks deliberate. That's the case worth evidence.
3. Merchant error
Merchant error is a chargeback your own process caused, like a double charge, a wrong item shipped, or a descriptor the cardholder can't place. The customer is disputing something that genuinely went wrong.
Everything here is inside your control, so you fix the process instead of the dispute. Each one traces back to a billing system, a shipping step, or a descriptor.
Match your payment log against your fulfilment log each week and the duplicates show up before the cardholder finds them.
Take a checkout glitch that bills a customer twice for one order. They see two identical charges, assume the second is a mistake nobody will own up to, and dispute it.
This is also the easiest category to undercount, because the disputes arrive labelled as something else. A duplicate charge often files under a fraud code. The cardholder tells the bank they didn't agree to the second charge, and bank intake maps that to fraud. So counting by reason code alone shows you fewer of these than you have. Count the duplicate charges in your billing log and compare that to your merchant-error chargebacks.
Almost never fight one of these. Refunding the customer before the dispute reaches the bank costs less than the fee and the ratio damage.
Fighting also spends staff time on a case where the chargeback process sides with the cardholder anyway.
Preventing each type of chargeback
Each type gets stopped somewhere different, and only friendly fraud can still be stopped after the sale. Three places to act:
- True fraud: require CVVs, switch on Address Verification Service to flag address mismatches, and enrol in 3D Secure.
- Merchant error: reconcile your payment log against your fulfilment log weekly, letting support refund up to your average order value without approval.
- Friendly fraud: put your recognizable trading name in the descriptor field, and add a pre-dispute alert through Ethoca or Verifi.
Most merchants skip that third one, the alerts.
An Ethoca alert reaches you while the cardholder's complaint is still open at their bank. That's your window to refund fast, or to confirm a charge they forgot.
Checkout fraud scoring can't help you here, because that decision is weeks old by then.
Verifi does the same job on the Visa side. In our dataset, fraud and card-absent disputes (reason code 10.4) make up about 11.1% of coded alerts. Cancelled-recurring disputes (13.2) take another 8.5%. An alert catches both.
What it won't catch depends on the card brand. Coverage is strong for Visa and Mastercard, thin for American Express, JCB, and Discover. A dispute on a thin brand may never alert you.
Worth reading how alerts work before you enrol.
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 what our platform processed.
We counted the total alerts in each reason-code category. Each figure is a share of the alerts that carried a code. We drop the unlabeled rows, and we name anything from outside our own data.
Two limits are worth stating plainly:
- A self-selected merchant mix. Our merchants signed up with us, which skews the sample toward Stripe and Shopify sellers.
- Thin coverage on some brands. The coverage gap named above means any brand-level share understates American Express, JCB, and Discover.
FAQ
What's the most common type of chargeback?
Friendly fraud tops the list, because disputes on the cardholder's own purchases outnumber stolen-card fraud. The Aite-Novarica survey split it into transaction confusion at 44% and first-party fraud at 29%, against 16% for third-party fraud.
What is a false chargeback?
"False chargeback" is an informal term for a dispute that lacks a legitimate basis, and it usually points at friendly fraud. The card networks carry no formal definition for it and classify by reason code instead.
Can you tell the chargeback type from the reason code?
The code narrows it but rarely settles it. Fraud codes point one way and cancelled-recurring codes the other, while service and delivery codes need your order record.
Is true fraud ever worth fighting?
Rarely, and only when you can show the real cardholder authorized or gained from the purchase. If the address, device, and account history all trace back to the cardholder, the case may be friendly fraud under a fraud code.
