What Stripe Smart Disputes Covers, And What It Doesn't

Stripe Smart Disputes is a genuinely useful tool. It handles auto-submission, builds AI-tailored evidence packets, and requires zero setup work, making it a real asset for Stripe merchants managing chargebacks. But there's a gap most merchants only discover after losing a dispute they should have won, and it comes down to one simple thing: Stripe Smart Disputes can only work with data that lives inside Stripe.

A large portion of the chargebacks you'll face require evidence from outside the payment layer entirely. When that evidence isn't available inside Stripe, the dispute doesn't get auto-submitted. That's not a flaw in the product. It's the structural reality of how payment processors are built, and understanding where that boundary sits is the difference between recovering your revenue and writing it off.

Why Smart Disputes Can't Win Every Chargeback

Stripe's AI engine draws on payment-layer data: transaction records, IP addresses, AVS and CVC results, device fingerprints, and customer history. For fraud and duplicate-charge disputes, that's exactly what you need and the evidence is right there. The problem is that not all chargebacks are fraud disputes.

When a customer files a "product not received" claim, the issuer wants to see full carrier data, delivery confirmation, and signature capture. Stripe can surface basic tracking numbers, but it doesn't have access to the complete fulfillment records that actually win these cases. When a customer claims a subscription was cancelled but charges continued, the issuer wants cancellation logs, login records, ToS acceptance timestamps, and usage data, all of which live in your CRM, your helpdesk, or your own platform. Stripe's own documentation reflects this reality: dispute eligibility is determined in part by "evidence availability," meaning if the evidence isn't sitting inside Stripe, the dispute isn't auto-submitted.

The Stripe Smart Disputes Reason-Code Gap, Plainly

Here's how Stripe Smart Disputes chargeback coverage breaks down by dispute type:

Stripe wins the top rows and wins them well. The limited rows are where revenue quietly disappears, not because Stripe is doing something wrong, but because it simply doesn't have access to the evidence that wins. For physical goods merchants, more than half of disputes typically fall into these third-party-evidence categories, according to Chargeflow's 2024 Chargeback Report. For SaaS and subscription companies, the exposure sits mostly in subscription cancellation and services-not-provided disputes.

For a deeper breakdown of every reason code and what evidence each one requires, see Chargeflow's Chargeback Reason Codes guide.

What Winning These Disputes Actually Takes

Take a "product not received" dispute. To win it, you need full carrier tracking events, delivery confirmation, an AVS-to-shipping-address match, and a delivery timestamp compared against when the dispute was filed. 

For a cancelled-subscription dispute, you need the cancellation request log (or the absence of one), login records showing the customer used the service after the disputed charge, ToS acceptance logs, and support ticket history from wherever your team handles support. None of this evidence is hard to find. It just doesn't live in Stripe, which means Smart Disputes can't build the packet.

That's the gap. For merchants handling disputes manually, assembling this evidence before the deadline is time-consuming and easy to miss. For those relying solely on Smart Disputes, these cases go uncontested entirely.

The Case for Running Smart Disputes and Chargeflow Together

Chargeflow is a Stripe-native app that installs directly from the Stripe App Marketplace, runs inside the Stripe Dashboard, and holds official Stripe Partner status. The whole premise is to extend what Stripe already does, not replace it. Stripe Smart Disputes handles the disputes where Stripe's data is sufficient. Chargeflow handles the ones that require shipping carriers, 3PLs, helpdesks, CRMs, and your own platform data, pulling from 50+ data sources and assembling formatted evidence packets for Visa, Mastercard, Amex, and Discover automatically before the dispute deadline. There is no overlap, no double-submission, and no workflow conflict. Chargeflow detects which disputes are eligible for Stripe-side automation and only acts where it adds unique value.

On fees:" Both tools are success-based, so running them together doesn't add cost exposure on losses. From June 2025, Stripe charges a dispute counter fee on top of the standard receipt fee when you challenge a dispute, refunded if you win and kept if you lose, and this counter fee applies whether you’re disputing manually or using a third-party tool like Chargeflow. Smart Disputes users have the counter fee waived entirely, in exchange for a 30% success fee on recovered amounts. Fee amounts vary by region. For a full breakdown of the fee structure by country, see Stripe's new dispute fees explained. Either way, the number that matters is net revenue recovered across all reason codes, not the fee per case.

What Merchants Actually See

Merchants running Chargeflow alongside Stripe Smart Disputes recover 4x more chargebacks on average, see up to 90% fewer incoming disputes through pre-dispute deflection alerts, and save 20+ hours a month on manual evidence work. Wordtune (AI21 Labs) saw a 5.4x increase in chargebacks won after adding Chargeflow to their Stripe workflow, along with a 29.7% reduction in their overall dispute rate. Chargeflow is trusted by 20,000+ eCommerce, SaaS, and enterprise merchants worldwide.

The Bottom Line

Stripe Smart Disputes is excellent at what it was built to do, and if it's handling your fraud and duplicate disputes you should keep it running. But if you're also losing "item not received," "not as described," or "cancelled subscription" disputes, that's not a Stripe Smart Disputes failure. It's a data-scope gap, and it's one you can close without changing your processor, your workflow, or your team. Install Chargeflow from the Stripe App Marketplace in under 90 seconds. You only pay when it wins.

Install Chargeflow on Stripe →

Frequently Asked Questions

What does Stripe Smart Disputes cover? Stripe Smart Disputes covers chargebacks where the evidence lives inside Stripe, primarily fraudulent transactions, duplicate charges, and authorization-related disputes. It uses payment-layer data like IP addresses, AVS results, CVC checks, and device fingerprints to build evidence packets automatically.

Is Stripe Smart Disputes free? Not exactly. Stripe Smart Disputes waives the dispute counter fee introduced in June 2025, but charges a 30% success fee on any amount recovered. If you lose, you only pay the standard dispute receipt fee. Whether it's cost-effective depends on your dispute volume and average transaction value.

What chargebacks does Stripe Smart Disputes not cover? Stripe Smart Disputes has limited coverage for disputes that require third-party evidence,  product not received, not as described, cancelled subscription, credit not processed, and services not provided. These reason codes need shipping carrier data, fulfillment records, CRM history, or helpdesk data that Stripe doesn't have access to.

Can I use Chargeflow and Stripe Smart Disputes at the same time? Yes. Chargeflow detects which disputes are eligible for Stripe-side automation and only acts on the ones that need third-party evidence. There's no overlap, no double-submission, and no conflict in your Stripe workflow.

How does Chargeflow work with Stripe Smart Disputes? Chargeflow installs from the Stripe App Marketplace and runs inside the Stripe Dashboard. Smart Disputes handles fraud and payment-layer disputes using Stripe's data. Chargeflow handles the rest, pulling evidence from 50+ sources including shipping carriers, 3PLs, helpdesks, and CRMs, and submits formatted evidence packets automatically before the dispute deadline.