Most founders think Stripe sets the chargeback rules. Stripe does not. The card networks do, and Stripe is enforcing thresholds that flow down from Visa and Mastercard. Understanding the math — and where your account sits on the curve — is the difference between an account that survives a bad month and one that does not.
The Visa and Mastercard Chargeback Thresholds in Plain English
There are two card network programs that matter: Visa’s VAMP (Visa Acquirer Monitoring Program) and Mastercard’s ECM (Excessive Chargeback Merchant) program. Both measure chargeback ratios, but they define the ratio and the thresholds differently.
Visa VAMP:
- Monitoring starts at 0.5% dispute ratio.
- Early warning at 0.65%.
- Excessive designation at 0.9% — this is where program fees, fines, and mandatory remediation kick in.
- The ratio is chargebacks divided by transaction count in the prior month.
Mastercard ECM:
- Standard program threshold: 1.5% chargeback ratio for three consecutive months with at least 100 chargebacks per month.
- Excessive program threshold: 3% ratio, or 300+ chargebacks in a single month.
- Mastercard counts the ratio slightly differently — chargebacks this month divided by transaction count last month.
Stripe enforces tighter internal thresholds than either network. Their warning zone starts around 0.75% because they need time to act before you breach the network-level limits, which would impose fines Stripe would have to absorb or pass through.
How Stripe Calculates Your Chargeback Ratio
The calculation looks simple, but there are three details that trip up most founders.
Detail one: it is a monthly ratio, not a rolling one. A bad week can spike the ratio for the whole month, even if the rest of the month was clean.
Detail two: the denominator is transactions, not revenue. Five chargebacks on 500 transactions is 1%, regardless of whether your average ticket is $10 or $1,000.
Detail three: representments do not reduce the ratio in the moment. If you win a dispute after representment, the chargeback still counts in the ratio for the month it occurred. You can appeal after the fact, but the damage to the current-month metric is already done.
The operational consequence: you cannot fix a bad month by winning disputes. You can only fix it by preventing the next ones.
Why the 0.75% Warning Zone Matters More Than 1%
Most founders anchor on the 1% number because it sounds like the line. It is not. The real line is Stripe’s internal warning threshold — roughly 0.75% — because that is when Stripe starts taking action: elevated review priority, reserves, or restrictions designed to protect themselves before the network threshold is breached.
By the time you hit 0.9% or 1%, you are already in the program enrollment zone — which means monthly fines from the card networks, required remediation plans, and a significantly higher chance that Stripe decides the relationship is not worth continuing.
Staying below 0.75% is not about avoiding the top of the range. It is about staying out of the warning band that triggers Stripe’s own protective actions.
What Happens When You Enter a Monitoring Program
If you breach a network threshold and get enrolled in VAMP or ECM, the consequences cascade:
- Monthly program fees. Typically $25,000 per month for VAMP enrollment, plus additional fines per chargeback over the threshold. These are passed from the network to the acquirer to you.
- Mandatory remediation plan. You submit a written plan for how you are reducing chargebacks, with monthly reporting to the network through your acquirer.
- Processing restrictions. Some categories and geographies may be restricted during the remediation period.
- Elevated reserve requirements. Stripe almost always adds a reserve to protect against the ongoing risk.
- Reputational flag. Once you are in a monitoring program, switching processors becomes harder. Other acquirers see the flag when you apply.
The cost of enrollment is high enough that most businesses cannot stay in the program for long — either the chargeback rate comes back down quickly, or the relationship with the processor ends.
How to Lower Your Chargeback Ratio Without Tanking Revenue
If your ratio is climbing, the instinctive fix — refund everyone aggressively to preempt disputes — is a trap. Aggressive refunds shift the problem to refund velocity, which is itself a risk signal, and can trigger reviews for different reasons.
The approaches that actually work:
- Identify the disputed transactions and find the cluster. Most spikes are not distributed evenly — they concentrate around a specific product, campaign, or fulfillment issue. Fix the source.
- Improve customer service response time. Many disputes are filed because the customer could not reach you. Faster responses convert disputes-that-would-have-happened into resolved support tickets.
- Add descriptive billing descriptors. Chargebacks for “fraudulent transaction” are often customers who did not recognize the charge. A clear descriptor with your business name and a support contact reduces these materially.
- Proactively refund the at-risk accounts. Customers who complained but did not dispute — the ones you can identify from support tickets — are the most likely to dispute next. Refund them before the dispute hits.
- Slow down acquisition on high-risk channels. If a specific traffic source produces a disproportionate share of disputes, its customers are not worth the risk to the account.
Done together, these tactics can move a 0.9% ratio back below 0.6% in 30 to 60 days.
Tracking the Metric in Real Time
The chargeback ratio is a lagging indicator. By the time you see it in your monthly dashboard view, the month that produced it is already gone. The point of real-time tracking is to see the ratio trending toward the warning band while you can still change the outcome.
FreezeAlert tracks chargeback ratio, refund velocity, and the leading indicators that predict dispute spikes — with alerts when any of them move toward the thresholds that matter. The free tier covers the core metrics. If you are anywhere near the 0.75% warning band, seeing the trajectory early is the difference between fixing the month and losing it.
Found this useful?
Subscribe to get engineering deep dives every week.