Stripe dispute rate vs activity, and the 0.75%
Stripe shows you two dispute metrics. They are usually different, and if you are watching the wrong one you will find out from an email rather than a dashboard.
The two calculations
From Stripe's documentation, checked August 19, 2026:
Dispute activity is "the percentage of disputes on successful payments by dispute date." Disputes land in the month they arrive.
Dispute rate is "the percentage of disputes on successful payments by charge date." Disputes are attributed back to the month the payment happened.
Stripe's own worked example makes the gap concrete. Process 1,000 payments in a week and receive 10 disputes that same week, but only 3 of those disputes relate to the 1,000 payments just processed. The other 7 came from older charges.
| Metric | Calculation | Result |
|---|---|---|
| Dispute activity | 10 disputes on 1,000 payments | 1.0% |
| Dispute rate | 3 disputes on 1,000 payments | 0.3% |
Same week, same business, one number more than three times the other.
Which one matters
Activity, and it is not close.
Stripe is explicit: "The card networks' dispute and card fraud monitoring programs use the dispute activity calculation." If activity exceeds network thresholds for a prolonged period, "usually multiple months," you may face fines.
Dispute rate is the more analytically useful number. Because it attributes disputes back to the charges that caused them, it tells you which cohort, campaign or product actually generated the problem. Stripe describes it as "a more accurate representation of fraud and disputes for your business" and it lives on the Radar page rather than in Analytics.
So the split is clean. Activity is the compliance number. Rate is the diagnostic number. Watching rate because it is lower and more flattering is how merchants get surprised.
One consequence of the charge-date attribution: because cardholders can dispute up to 120 days after payment and sometimes longer, Stripe notes the dispute rate "might change for dates more recent than 120 days old." Recent months look better than they will turn out to be. Do not read a healthy recent rate as a healthy business.
The threshold, and what triggers review early
Stripe puts the line at "dispute activity above 0.75%" as the industry standard for excessive.
The more useful part of its guidance is what happens before you reach it: "a sudden spike or steep upward trend can trigger placement in a monitoring program before dispute activity reaches the 0.75% threshold." Stripe also says it will proactively reach out if it sees higher activity or a significant increase in potentially fraudulent behaviour, and that its models sometimes predict future excessive activity and alert on that.
So the operative threshold is not a single number, it is a number and a trajectory. A business at 0.4% and climbing steeply is in a worse position than one flat at 0.6%.
Why winning does not help
This is the part that changes strategy, and Stripe says it more directly than most vendors will.
"All disputes, whether they're won or lost, count towards your dispute rate, so the best strategy to avoid monitoring programs is dispute prevention."
A dispute enters the count when it is filed. Representment recovers the money and leaves the count exactly where it was. That means a strong win rate protects revenue and does nothing for your standing, which is the single most misunderstood thing in this category and the reason merchants with excellent win rates still get account reviews.
Worth noting alongside this: Stripe's early fraud warnings are not disputes, but they are not neutral either. Stripe notes that Visa "counts these fraud warnings toward identification in their VAMP monitoring program," so an EFW can affect your standing without ever becoming a dispute.
Reclaim handles representment for Stripe, PayPal and Shopify Payments free, with no success fee. It protects the revenue. It does not touch either number on this page, and I would rather say that than let the two get conflated. Only resolving a dispute before it is filed keeps it out of the count, which is a different product and a different argument.
What to actually do
Watch activity monthly, in Analytics. That is the compliance number and the one the networks read.
Use rate, in Radar, to find the cause. Attributing disputes back to charge date is what lets you see which product, promotion or traffic source produced them.
Treat the trend as seriously as the level. A steep climb below 0.75% is a real risk, on Stripe's own account.
Fix the causes upstream. Descriptor clarity, delivery expectations and subscription messaging move the count. Representment does not, though it is still worth doing for the money, and the fee arithmetic favours contesting more than most merchants assume.
The honest part
The 0.75% figure is Stripe describing an industry standard, not a Stripe-specific rule, and the card networks run their own programs with their own thresholds and their own definitions. Visa's VAMP and Mastercard's monitoring do not calculate identically to each other or to Stripe's dashboard. Treat 0.75% as an orientation point, then check your acquirer's stated limit, which can be stricter.
Stripe also does not publish the exact thresholds at which it personally intervenes, only that it does. So the practical answer to "how close am I" involves asking your account contact rather than reading a page.
And nothing here means representment is not worth doing. It is worth doing for the money. It is simply the wrong tool for a monitoring problem, and buying it to solve one is a mistake this industry encourages.
Frequently asked questions
What is the difference between Stripe dispute rate and dispute activity?
Dispute activity counts disputes in the month they arrive, by dispute date. Dispute rate counts them against the payments that generated them, by charge date. The card networks' monitoring programs use dispute activity, so that is the compliance number; dispute rate is more useful for diagnosing which charges caused the problem.
What dispute rate is too high on Stripe?
Stripe describes the industry standard as dispute activity above 0.75% being excessive, and warns that a sudden spike or steep upward trend can trigger a monitoring program before you reach it. Your acquirer may hold you to a stricter limit than the network floor.
Does winning a dispute lower my Stripe dispute rate?
No. Stripe states that all disputes count towards your dispute rate whether won or lost. A dispute enters the count when it is filed, so representment recovers the money and leaves your standing unchanged. Only preventing or resolving disputes before filing affects the number.
Why did my Stripe dispute rate change for a past month?
Because disputes are attributed back to the charge date, and cardholders can dispute up to 120 days after payment and sometimes longer. Stripe notes the rate might change for dates more recent than 120 days old, so recent months look better than they will eventually be.
The check to run this month: open Analytics, find dispute activity, and plot it across the last six months rather than reading the current figure. If the line is rising steadily you have a problem to solve now, even at half the threshold, because Stripe has told you the trajectory counts.