Chargeback Fraud: Accidental vs. Deliberate, and the Fix
Chargeback fraud happens when a customer takes a real purchase to their bank as a dispute. The request goes to the issuer, so the money leaves before you hear about it. You lose the sale, the product, and a fee on top.
I've had customers dispute orders I could see were delivered. Sorting those disputes into two buckets changed how I handled them. Some had genuinely forgotten. Others knew exactly what they bought. Tell the two apart and you'll know which fix to reach for.
Key takeaways
- Chargeback fraud means taking a real purchase to the bank as a dispute.
- Sort your disputes into accidental and deliberate before choosing a fix.
- Fix accidental disputes with a billing descriptor customers recognize.
- One provider's merchants won 43.82% of the friendly fraud disputes they fought.
- Software and SaaS average a 0.66% chargeback rate, below retail.
What is chargeback fraud?
Chargeback fraud is when a customer takes a legitimate charge to their card issuer as a dispute, instead of asking the merchant for a refund. The purchase was real, so the dispute itself is what makes it fraud. It splits into two categories, accidental and deliberate, and each one needs a different fix, covered in the section below.
Sorting a dispute into the right bucket comes before you respond to it.
The dispute route exists to protect cardholders from charges they never authorized. A customer can file through that same route for a charge they did authorize. From the outside, the two filings look identical, so a real purchase gets processed as fraud.
Plenty of chargebacks are honest. A wrong item, damaged goods, or a missing order all move through the same dispute mechanism.
Those are the disputes the system was built for.
How does chargeback fraud work?
The customer goes to their card issuer, the issuer reverses the charge, and you either send evidence or lose the money. The funds leave your account before anyone reviews the claim.
Going to the bank first is faster than asking a merchant for a refund. Two taps in a banking app beats a support email and a wait. That speed is why customers use the route for ordinary billing confusion.
Your response window is short. It runs 20 to 45 days depending on the network and the chargeback reasons behind the filing.
Miss the window and the dispute defaults to the customer.
Accidental vs. deliberate chargeback fraud
Accidental means the customer didn't recognize a charge, and deliberate means they disputed one they clearly remember. Deliberate cases are what merchants usually mean by friendly fraud vs. true fraud.
The two categories need different fixes because their root causes differ.
Accidental fraud is a recognition problem, born in the two seconds a customer spends reading a statement line. Deliberate fraud is a behavior problem, and the customer has already decided the dispute is worth filing.
Most of what merchants call fraud is a customer who forgot.
The recognition fix is cheap. The behavior fix costs real money, so sort your disputes before you spend on either.
The line between the two blurs from your side. A vague descriptor generates disputes that look deliberate and are honest confusion. Clear the statement line before you judge intent.
Types of chargeback fraud
Chargeback fraud takes a recognizable shape depending on what the customer bought.
Digital-goods chargebacks, subscription fraud, and return fraud are the three patterns you'll actually see:
- Digital-goods chargebacks: no physical delivery to point at.
- Subscription fraud: a renewal the customer stopped tracking.
- Return fraud: a refund collected twice, through two systems.
Take them in order.
1. Digital-goods chargebacks
A customer downloads a digital product, disputes the charge, and your only delivery proof is a server log. That record holds a timestamp, a file name, and an IP address.
Card networks treat these disputes differently for that reason. A download log carries less weight than a courier's signature. Digital goods have their own reason codes, searchable in our reason code lookup tool, and a lower typical win rate.
Say you sell a $15 e-book. A customer buys it, downloads it that afternoon, then disputes the charge claiming it never arrived.
Your whole case is that server log. It proves the file moved, and authorization stays a separate question the log can't answer.
Digital goods sold through an app store work differently. The platform holds the account records and the delivery proof, so part of the evidence burden sits with them.
2. Subscription fraud
A customer starts cancelling, stops halfway, then disputes the next charge as unauthorized.
In their memory the account was already closed.
These disputes cluster around renewal dates and free-trial conversions. That's when the gap is widest between what the customer remembers doing and what your billing system recorded. A charge landing against that belief reads as unauthorized to them.
A hard-to-find cancellation flow produces this pattern on its own, independent of your descriptor. That's a cancellation problem rather than a fraud problem, and no detection tool fixes it.
3. Return fraud
A customer returns an item through your normal return process and separately disputes the original charge. They get paid twice, because the two systems keep separate records.
Your returns desk and the customer's card issuer each hold one half of the story. The issuer's record shows a disputed charge. Your returns log shows a completed return.
The double payout goes through unremarked.
Imagine a customer returns a $200 item for store credit. Three weeks later they file a chargeback on the original card charge, keeping the credit and the money.
Logging every return confirmation against its original transaction ID closes most of this gap. Without that link, catching a double refund takes a manual cross-check most teams never run.
How to prevent chargeback fraud
A recognizable billing descriptor and dispute alerts prevent most chargeback fraud. Each handles one category, and both act before a chargeback exists.
When customers recognize the name on their statement, they stop calling the bank about it. Alerts handle the deliberate ones. Ethoca, RDR, and CDRN each tell you a dispute was filed. Each then gives you a window to refund it first.
Run these four in order, because each depends on the one above it:
- Audit your billing descriptor. Check that a real statement shows the brand name customers know, plus a support number.
- Send a receipt within minutes of the charge. Include the product, the amount, the last four digits, and the descriptor string.
- Turn on dispute alerts after steps 1 and 2. Connect Ethoca, RDR, and CDRN, then auto-refund any alert worth less than your dispute fee.
- Put cancellation two clicks from the account page. Send a renewal reminder three days ahead with a working cancel link inside.
The ordering matters. Alert a customer who still can't place the charge and you've handed them a refund they never asked for.
I lowered my own chargeback rate before I ever touched a dispute, by fixing the descriptor and deploying alerts.
The cheapest chargeback is the one nobody files.
Tokenized wallets complicate step 3. Worldpay found digital wallets in 40% of US e-commerce transactions. Those are harder for an alert network to match to the order.
How to detect chargeback fraud (red flags)
Provable delivery, a repeat disputer, and a reason that contradicts your records each mark a dispute as probably deliberate:
- Delivery or usage you can prove. A signed delivery receipt or a login dated after the charge.
- The same customer, more than once. Two or more disputes across separate orders from one account.
- A reason that contradicts the record. An "unauthorized" claim on an account with four prior orders.
Each signal finds a case where your own records contradict the dispute reason. That contradiction is what a response packet needs.
Match the evidence to the claim. Delivery confirmation answers "item not received." A login timestamp answers "services not provided." Order history answers "I never authorized this."
A dispute that trips none of the three belongs in the accidental pile, where the descriptor fix applies.
Patterns beat single cases. In Chargeback.io's Dropship.io case study, the merchant sorted honest cancellation confusion from the rest. That let them aim alerts at one group.
One caution on the tooling. In our dataset, about 9.9% of alerts involved a 3D Secure transaction. Most disputes you investigate will have no authentication data, so build your evidence around delivery and usage logs.
Red flags tell you where to look. They stop short of telling you what happened, because a repeat disputer might be a repeat victim of card theft. Intent stays a judgment call.
Turn on chargeback alerts and you'll see disputes while a refund can still stop them.
Chargeback fraud vs. chargeback rate: what merchants see
Win rate measures how often you beat a dispute, chargeback rate measures how often you get one, and the two move independently:
Two of those rows deserve reading closely. The true fraud figure is low because a criminal used a stolen card. The purchase belongs to the thief, and the issuer rules for the cardholder whatever you submit.
The ticket-size split runs the opposite way to most expectations. You win small disputes more often than large ones. A high-value dispute likely draws more scrutiny and a more determined cardholder. The report gives numbers here, and the causes stay a guess.
All four win rates come from one provider's book of business. Read them as direction, not as a target.
Chargeback rate is a different number from win rate. Swipesum puts the average chargeback rate for software and SaaS at 0.66%, below retail.
Subscription billing still generates the renewal disputes described above. SaaS lands low because those disputes spread across many small recurring charges.
How we sourced our data
The 3D Secure figure here comes from anonymized, aggregated alert data across merchants on the Chargeback.io platform. We counted alerts in each category and report them as shares of the labeled total. These numbers describe the alerts our own platform processed across enrolled merchants.
FAQ
Is chargeback fraud illegal?
Yes, knowingly disputing a charge you know is legitimate meets the legal definition of fraud in most places. Prosecution of individual cardholders is rare, so the practical outcome is usually a closed account.
What's the difference between chargebacks and refunds?
A refund is money you send back voluntarily, while a chargeback is a reversal the bank forces on you. The chargeback also costs a fee and counts against your dispute rate.
What happens if you commit chargeback fraud?
The merchant can close the account, blacklist the card, and refer the case for collection. Card issuers also cancel accounts for repeat disputing.
What counts as a valid reason for a chargeback?
A charge nobody authorized, an order that never came, a duplicate charge, or an item unlike its description all qualify. The test is whether the customer tried the merchant first.
Do banks or card networks investigate chargeback fraud?
The issuing bank reviews the cardholder's claim and any evidence you submit, then rules on that record alone. Card networks set the rules and arbitrate escalations, but neither investigates the customer the way a fraud examiner would.
