What Is True Fraud? Definition and How Often It Happens
True fraud happens when someone other than the cardholder uses a stolen card to make a purchase the real cardholder never authorized. The purchase was never legitimate in the first place, so the merchant carries no blame for it.
I've fixed the billing descriptor on my own stores and cut my chargeback rate before I ever fought a single dispute. That work never touched true fraud.
A stolen card stays a stolen card, however clear your statement line reads.
Telling these disputes apart from the rest shows you which ones are worth your time.
Key takeaways
- Define true fraud as a stolen card used by someone other than your customer.
- Separate it from friendly fraud by asking who made the purchase.
- Watch reason code 10.4, at about 11.1% of our own alert mix.
- The next two codes, at 8.5% and 8.2%, signal friendly fraud instead.
- Expect to absorb the loss yourself unless 3D Secure authenticated the purchase.
Short on time? Catch disputes before they harden into chargebacks with Chargeback.io alerts.
What is true fraud?
True fraud is a stolen card, card number, or account credential used by someone who was never your customer and had no permission to buy. The real cardholder sees a charge a stranger made, and reports it.
With most disputes, your customer bought something and forgot, or didn't recognize the name on their statement. A clearer descriptor or a quick reply solves those. Here the buyer was a criminal, so there's no customer to remind and no charge to explain.
Your only real option is to screen the order before it ships, using 3D Secure and address verification at checkout.
Both tools check a card-absent purchase before you fulfill it, and 3D Secure also moves the loss to the issuer when it authenticates the buyer. No after-the-fact tool does either job.
Friendly fraud and chargeback fraud show up weeks later, on a sale that looked normal. That's when chargeback alerts can still reach a dispute.
How true fraud differs from friendly and chargeback fraud
Your customer never made a true fraud purchase, while friendly fraud and chargeback fraud both start with a real buyer disputing their own charge. All three end in a chargeback, so the three labels get mixed up often.
Friendly fraud is that customer disputing a purchase they don't recognize. Chargeback fraud is the same move made knowingly.
What separates both of them from true fraud is authorization.
A cardholder who forgot a renewal authorized the sale. So did a cardholder lying to keep the goods. Your delivery proof and your terms can win those disputes.
They win nothing in true fraud, since the victim authorized nothing, so issuers treat the claim differently from the first phone call.
Sorting a live dispute takes more than a definition, and our full comparison has the questions that do it.
Where true fraud shows up in the data
Fraud/card-absent (Visa reason code 10.4) is the largest single dispute reason in our own dataset, at about 11.1% of alerts with a recorded code. The next two codes are both subscription cancellations, and neither reaches 9%:
That top row sets the outside limit on true fraud rather than its true size. Code 10.4 covers unauthorized purchases in a card-absent sale, which is where true fraud lands. But plenty of friendly fraud and merchant errors get filed under the same code, because the cardholder's description sounds the same either way.
What the number shows is how often a buyer says "I didn't authorize this" when nobody swiped a card. Treat it as your upper bound and expect the real share to sit below it.
Two limits are worth naming:
- These alerts cover only the merchants on the Chargeback.io platform.
- Code 10.4 mixes criminal fraud with disputes the network hasn't separated yet.
Pull your own dispute's code through our reason code lookup before you decide what you're dealing with.
How we sourced our data
The reason-code shares here come from anonymized, aggregated alert data across merchants on Chargeback.io. We counted total alerts by reason code and report each as a share of that total.
These numbers describe our own merchants, not the whole payments industry.
FAQ
Who pays for a true fraud chargeback?
The issuing bank refunds the cardholder, but the merchant usually eats the cost through the chargeback and its fee. Liability shifts to the issuer when you authenticated the purchase with 3D Secure.
Can true fraud be prevented the same way as friendly fraud?
No, because the two categories close at different moments. Friendly fraud tactics keep working after the sale, while your defense against true fraud ends the second you approve the order.
Is true fraud the same thing as third-party fraud?
Mostly yes, since third-party fraud, criminal fraud, and malicious fraud all describe a stranger using someone else's card. Third-party fraud is the broader banking term and also covers account takeover and identity theft outside the dispute context.
