Fraudulent disputes on Stripe: the complete guide
A fraudulent dispute means your customer's bank believes the charge was never authorized by the actual cardholder. This is the hardest category to win, and the most common: it accounts for over half of all disputes industry wide. Genuine fraud is usually a lost cause. The real value here is telling genuine fraud apart from friendly fraud, where a legitimate customer disputes a charge they actually made.
Quick facts
- Response window
- Same 7 to 21 days as any Stripe dispute
- Share of all disputes
- Over half, industry wide
- Recovra's general read
- Often not winnable when fraud is genuine; can be strongly winnable when it's friendly fraud with a real paper trail
What this reason code actually means
Stripe applies fraudulent when the customer's claim is that they didn't make or authorize the purchase at all. Not that they're unhappy with it, not that it never arrived: that the charge itself is illegitimate from their side.
Why this happens
- Genuine fraud. A stolen card was used, and the actual cardholder had nothing to do with the purchase.
- Friendly fraud. The cardholder made the purchase themselves, and either forgot, didn't recognize the billing descriptor, or is disputing deliberately to get a refund without going through you.
- Family or account sharing. Someone with access to the card or account made a purchase the primary cardholder didn't expect.
Evidence Stripe accepts for this reason code
- Customer purchase IP address and device data consistent with past orders and the billing address
- Address Verification System and CVC match results
- 3D Secure authentication, if it was used at checkout
- Prior order history showing a legitimate relationship with the same customer
- Customer communication referencing the purchase
For fraud disputes specifically, Stripe evaluates eligibility for Visa's Compelling Evidence 3.0 program automatically. If a case qualifies, Stripe notifies the merchant, and submitting evidence in that case has a meaningfully higher chance of success than a typical fraud dispute.
The mistakes that lose this type of case
- Fighting every fraud dispute by default. Genuine fraud usually isn't winnable, and treating every case the same wastes the response window on cases with no real chance.
- Skipping the IP and device data because it feels technical. This is often the single strongest signal available for telling fraud apart from a forgotten purchase.
- Not checking for prior order history. A customer with three prior legitimate orders disputing a fourth, identical purchase is a very different case than a first time buyer.
- Assuming 3D Secure was used without checking. If it wasn't, that's worth knowing before building the rest of the case.
An illustrative example
How Recovra handles fraudulent disputes
Recovra checks for the signals that separate genuine fraud from friendly fraud before recommending anything. If the pattern points to genuine fraud, we'll say so honestly rather than build a case with little chance of success. If the pattern points to friendly fraud with real supporting data, we build and submit that case before your deadline. You only pay if it's won.
Request your free dispute auditFrequently asked questions
Is every fraud dispute genuinely fraud?
No. A meaningful share are friendly fraud, where the actual cardholder made the purchase and is disputing it anyway.
What is Compelling Evidence 3.0?
A Visa program that lets a merchant show a customer's prior legitimate purchase history to counter a fraud claim. Stripe checks eligibility automatically and notifies the merchant if a case qualifies.
Should I always fight a fraudulent dispute?
No. If nothing points to friendly fraud, fighting rarely changes the outcome and just adds the dispute countered fee on a loss.
If a fraudulent dispute is sitting in your dashboard right now, the free audit will tell you honestly whether it's friendly fraud worth fighting or genuine fraud not worth the fee.
Request your free dispute audit