Stripe Chargeback Threshold Guide¶

Use this page when you still need the broad explanation of how dispute pressure turns into monitoring, reserves, review, or termination risk.

This is the main explanatory guide for chargeback-threshold logic.

If your dispute ratio is already high enough to create an active state problem, use Stripe Chargeback Threshold Reached first.

What This Guide Covers¶

Use this page when you are asking:

what Stripe actually monitors when disputes rise
why the same dispute count can create different outcomes at different volumes
when threshold pressure is still a guide-level problem versus an active account-state problem
which page to open next before you prepare a mitigation plan

Understanding the Chargeback Ratio¶

Your chargeback ratio is calculated by dividing the number of chargebacks by the total number of successful payments within a specific month. This is based on count, not volume.

Not all dispute issues are identical.

A merchant can have:

high dispute volume but manageable ratio because transaction volume is large
a smaller absolute number of disputes but a severe ratio because volume dropped
dispute pressure that overlaps with broader Stripe risk scoring or verification concerns

That is why threshold analysis, dispute operations, and account-state analysis should be read together rather than treated as the same problem.

Monitoring Thresholds¶

0.65% - 0.75% (Warning Zone): Stripe may flag your account for "Early Dispute Detection." You might receive automated warnings or notice a slight increase in manual reviews.
0.90% - 1.0% (Enforcement Zone): This is the industry standard threshold for card networks (Visa/Mastercard). Crossing this level typically triggers a Stripe compliance review.
Above 1.0% (High Risk): At this level, Stripe is often forced by card networks to take action, which may include imposing a 25% - 100% reserve or terminating the account to protect the network.

Card Network Monitoring Programs (The "Shadow" Enforcement)¶

Crossing the 1.0% threshold doesn't just alert Stripe; it triggers formal monitoring programs from Visa and Mastercard.

1. Visa Dispute Monitoring Program (VDMP)¶

Standard: 0.9% dispute-to-transaction ratio AND 100+ disputes per month.
High Risk: 1.8% ratio AND 1,000+ disputes per month.
Impact: Monthly fines (starting at $50 per dispute) and mandatory remediation reports.

2. Mastercard Excessive Fraud Merchant (EFM) Program¶

Threshold: 0.50% fraud-to-sales ratio AND 300+ fraud transactions.
Impact: Intense scrutiny and potential loss of ability to process Mastercard payments.

Threshold Versus Active State Pages¶

Read this page as the broad guide for dispute-threshold logic.

Move to the state page when the question has become concrete:

the ratio is already high or worsening
Stripe is already increasing monitoring pressure
payouts, reserves, or account review are already being affected

Use the concrete page here:

Stripe Chargeback Threshold Reached

Escalation Path¶

Dispute increase -> threshold pressure -> monitoring or reserve logic -> payout or payment friction -> account review -> termination risk

The important question is not only whether the threshold was crossed, but whether Stripe now sees the dispute pattern as part of a broader account-risk story.

Threshold vs. Dispute Volume vs. Monitoring Logic¶

These three concepts are related, but they are not interchangeable:

Concept	What it answers	Why it matters
Dispute volume	How many disputes arrived	Helps identify operational load and affected products
Chargeback threshold	Whether the dispute ratio crossed a risk boundary	Indicates whether network or platform monitoring may intensify
Monitoring logic	How Stripe and card networks interpret the pattern	Determines whether the issue stays local or escalates into reserves, review, or restrictions

This distinction matters because two businesses can report the same dispute count and still receive very different treatment from Stripe.

What to Review Before It Becomes a State Problem¶

Which products, offers, or fulfillment paths are generating the ratio pressure?
Is the problem isolated to disputes, or overlapping with fraud, refund, and verification signals?
Are you still in a guide-level monitoring question, or already in an account-state workflow?
Would the mitigation plan change the ratio trajectory fast enough to matter?

What to Check Next¶

Check the more specific Stripe Chargeback Threshold Reached page if you are already near or over a monitored threshold.
Check Stripe risk score guide if rising disputes overlap with fraud, refund, or behavioral anomalies.
Check Stripe account under review if the problem has already become an account-state issue.
Check Stripe account recovery guide if Stripe is asking for a mitigation plan or evidence package.

Structured Summary¶

This page explains how Stripe chargeback thresholds work before the issue hardens into an active account state.

Use it to understand monitoring logic, escalation paths, and when to move from broad threshold analysis into a concrete state page.

Back to: Stripe Risk Hub