The 0.75% threshold is not a random Stripe policy. It is the credit-card industry's shorthand for "this merchant is generating too many disputes," and Stripe monitors you against it because the card networks hold Stripe responsible for your behavior. If you sell on Shopify with Stripe (or use Stripe directly), this one number quietly governs whether your payment processing stays on. This guide breaks down exactly what the threshold measures, how it is calculated, and the profit math nobody else shows you.
What is the 0.75% Stripe dispute rate threshold?
A dispute (chargeback) happens when a cardholder asks their bank to reverse a charge. Stripe tracks the share of your payments that turn into disputes and compares it against network limits. Per Stripe's documentation, "the credit card processing industry standard recognizes dispute activity above 0.75% as excessive."
That 0.75% is a warning line, not a hard cutoff. Stripe notes that a sudden spike or a steep upward trend can land you in a monitoring program before you ever reach 0.75%. In other words, the trajectory matters as much as the raw number.
It is worth being precise about who owns the threshold. Stripe does not invent its own limit; it enforces the thresholds set by Visa and Mastercard. So "the Stripe dispute rate threshold" is really the network standard that Stripe passes through to you.
Dispute activity vs. dispute rate: the number Stripe actually watches
Stripe shows you two different figures, and confusing them is the most common mistake. According to Stripe's disputes docs, dispute activity counts disputes by the date the dispute is filed, while dispute rate counts them by the date the original charge was made.
Stripe's own worked example makes it concrete. Say you process 1,000 payments in a week and receive 10 disputes that week, but only 3 of those disputes trace back to the 1,000 recent payments — the other 7 are from older orders. Your dispute activity is 1% (10 ÷ 1,000), while your dispute rate is 0.3% (3 ÷ 1,000).
Here is the part that matters: the card networks' monitoring programs use dispute activity, not dispute rate (Stripe). Dispute rate is the cleaner diagnostic for spotting a bad product or a fraud pattern, but activity is what gets you fined. Watch the activity number in your Stripe Analytics section.
The threshold ladder: where 0.75% sits
Different sources map the danger zone slightly differently, but the shape is consistent. One widely cited breakdown from Chargebacks911 lays out the tiers:
| Dispute rate | Status |
|---|---|
| Under 0.5% | Not at risk |
| 0.75% | Early warning |
| 0.9%–1% | At risk |
| Over 1% | Excessive |
(Source: Chargebacks911 — Stripe chargeback limit.)
The takeaway is that 0.75% is the "get your attention" line and 1% is where formal network programs bite. The narrow band between roughly 0.65% and 0.75% is your window to fix the underlying cause before you tip over. Treat 0.75% as a ceiling to stay well below, not a target to bump against.
For context on what "normal" looks like, the average general chargeback rate sits around 0.26% per a Sift benchmark cited by Chargeflow. A healthy store runs at roughly a third of the excessive line — which tells you the threshold leaves real room, but not a lot.
How to calculate your dispute rate (worked example)
The formula is simple: disputed transactions ÷ total transactions over a rolling monthly window. The scary implication for small stores is how few disputes it takes to cross 0.75%.
Say you ship 900 orders in a month. The 0.75% line is 900 × 0.0075 = 6.75, so 7 disputes in that month would push you over. A store doing 900 orders might feel established, yet a single bad week — a shipping delay, a fraud ring, a confusing billing descriptor — can generate seven disputes fast.
One mitigating detail: the networks require a minimum dispute volume before enforcement triggers, so a very small merchant can technically show a high percentage without immediate action (Chargeback.io). Don't lean on that. A rising rate still flags your account for review, and the fix is the same either way.
If you're new to how these reversals differ from a simple refund, our explainer on what a chargeback is on Shopify walks through the mechanics before the money leaves your account.
Why winning a dispute doesn't save your rate
This is the rule that catches everyone. Per Stripe, "all disputes, whether they're won or lost, count towards your dispute rate." Fighting and winning gets your money back — it does not erase the ding on your account health.
So representment (contesting disputes) protects your revenue but does nothing for your threshold math. The only lever that moves your rate is stopping disputes from being filed in the first place. That reframes the whole problem: prevention beats defense, every time.
It also means a store can win most of its disputes and still get its Stripe account restricted. If your win rate is great but your filing rate is climbing toward 0.75%, you have a volume problem, not an evidence problem.
What crossing 0.75% actually costs you
Most articles stop at "your account could be restricted." The real cost has three layers, and the third one — the per-order profit hit — is the one that quietly kills margins.
Layer one: the per-dispute fee. In the US, Stripe charges $15 per dispute, and losing adds a further counter fee for a total near $30 on a lost dispute, on top of the clawed-back sale amount (Chargeback.io). Our breakdown of the chargeback and retrieval fees you'll actually pay covers how these stack up.
Layer two: reserves. Once you're classified high-risk, Stripe can hold back a slice of your payouts as collateral — one report puts the range at roughly 10%–25% of revenue held back (Chargebacks911). That's cash flow frozen precisely when you can least afford it.
Layer three: the true per-order loss. A lost dispute typically costs 2x–2.5x the order value once you add unrecoverable product cost, shipping, ad spend, and time, per Chargeback.io. For print-on-demand that multiplier is worse, because the item was printed to order and can never be restocked.
A print-on-demand worked example
Say you sell a $40 shirt fulfilled through Printify. Your production cost plus supplier shipping is $22, and it took roughly $9 of Meta ad spend to acquire that customer.
| Line item | Amount |
|---|---|
| Sale amount clawed back | $40.00 |
| Stripe dispute fee | $15.00 |
| Printify cost already paid (can't restock a printed shirt) | $22.00 |
| Ad spend to acquire the customer | $9.00 |
| Out of pocket on one lost dispute | $86.00 |
That's $86 gone on a $40 sale — about 2.15x the order value, before you count the time spent gathering evidence. Now stack it: to hit the 0.75% ceiling you needed only 7 disputes on 900 orders, and if those go against you, you're staring at roughly $600 in losses plus a reserve hold. The threshold isn't just an account-health metric; it's a direct line into your profit.
This is exactly why margin-sensitive POD sellers need to know their real per-order economics before a dispute wave hits — the ground rules are covered in our guide to ecommerce ops economics for small Shopify and POD stores.
How to stay under the 0.75% threshold
Because winning doesn't help your rate, everything worth doing is preventive:
- Ship with tracking and delivery confirmation on every order. Delivery evidence is the strongest defense against "item not received," the most common dispute trigger.
- Use a clear billing descriptor so customers recognize the charge on their statement instead of disputing an unfamiliar line.
- Send proactive shipping and delay updates. POD's production-plus-shipping timeline runs long, and silence during that gap is where "where's my order?" disputes are born.
- Screen and verify high-risk orders before you fulfill — for POD especially, once the item prints, the cost is sunk even if the order was fraud.
- Publish a plain-language refund policy and honor refunds quickly; a refund carries no dispute fee and no threshold hit, so it's almost always cheaper than the alternative.
The strategic point is that your dispute rate is downstream of operations you already control: shipping speed, communication, and product accuracy. Fix those and the number takes care of itself.
Know your real per-order profit before disputes eat it
You can't manage what you can't see. When a dispute hits, the damage is spread across your sale price, Stripe fees, supplier costs, and the ad spend that acquired the customer — and most sellers never total it up per order.
That's where PodVector fits in. It connects your Shopify, Meta Ads, Google Ads, Printify, and Printful accounts and computes your true per-order profit, so you can see which products and channels actually clear a margin once fees and fulfillment are counted. Victor, its AI employee, analyzes that live data and proposes moves — with your approval on any Shopify-side action — instead of leaving you to reconcile spreadsheets. Victor isn't a dashboard and doesn't touch your ad account; he reads the data and hands you the decision.
If you're consolidating from a marketplace to your own store as part of tightening operations, our walkthrough on importing your Etsy reviews into Shopify helps you carry your social proof across.
FAQs
Is 0.75% Stripe's rule or the card networks' rule?
It's the card networks' industry standard, which Stripe enforces on their behalf. Stripe describes dispute activity above 0.75% as the point the industry considers excessive (Stripe). Because Visa and Mastercard hold Stripe accountable for merchant behavior, Stripe monitors you against that line and reaches out before the networks levy fines.
Do disputes I win still count against my dispute rate?
Yes. Stripe is explicit that all disputes count toward your rate whether you win or lose them (Stripe). Winning representment returns your money and can recover the fee, but it does not remove the dispute from your ratio. That's why prevention, not defense, is what actually protects your account.
What's a good dispute rate to aim for?
Well under the 0.75% line — ideally closer to the roughly 0.26% average general rate cited from Sift by Chargeflow. Treat anything above about 0.5% as a signal to investigate the cause immediately, since the band between 0.65% and 0.75% is a narrow window to correct course.
Will one bad month push me over and close my account?
Usually not instantly. Network monitoring programs generally require elevated dispute activity sustained over multiple months before fines apply, and they require a minimum dispute volume (Stripe). But a sharp spike still flags your account for documentation requests and possible reserves, so a single bad month is a warning to act, not a moment to relax.
Why is a lost dispute so much more expensive for print-on-demand sellers?
Because a printed item can't be returned to inventory, so the production cost is gone on top of the refund, the dispute fee, and the ad spend. Industry figures put a lost dispute at 2x–2.5x the order value on average (Chargeback.io), and POD sits at the high end of that range because there's no restock to recover. That's what makes staying under 0.75% a margin issue, not just an account-health one.
How is dispute activity different from dispute rate on my Stripe dashboard?
Dispute activity counts disputes by their filing date; dispute rate counts them by the original charge date (Stripe). Networks judge you on activity, so that's the number to watch for account safety. Dispute rate is the better tool for diagnosing which specific products or time periods produced the disputes.