At a glance
Triggers when the trailing 30-day chargeback rate exceeds 0.9% (Visa’s Chargeback Monitoring Program threshold). Above 0.9%, Stripe enrols the merchant in a monitoring program with mandated chargeback-prevention measures and additional fees. Above 1.5% Mastercard threshold, the same applies for Mastercard transactions. Sustained breach of either can lead to processor account termination.
| What it counts | COUNT(disputes_with_chargeback_filed_in_30d) ÷ COUNT(successful_charges_in_30d). Both numerator and denominator anchored on the same 30-day window. |
| Numerator: which disputes count | Formal chargebacks only, status IN ('needs_response', 'under_review', 'won', 'lost'). Early-warning notifications (warning_needs_response, warning_closed) are excluded because they don’t count toward card-network thresholds. |
| Denominator: which charges count | Successful charges (status = 'succeeded') where the payment method is a card. Bank-debit, SEPA, manual transfer, gift cards, and Apple Pay direct don’t count toward the chargeback-rate calculation. |
| Currency | n/a, this is a count-ratio. |
| Fees / processing cost | n/a for the rate; each lost dispute adds a $15 fee separately. |
| Refunds | A refunded charge that’s later disputed still counts toward both numerator and denominator (the dispute filed against the original charge). Refunding before the dispute files is the right pre-emptive action. |
| Disputes / chargebacks | This card measures disputes. |
| Failed / declined payments | n/a, declined charges aren’t in the denominator. |
| Payout timing | n/a. |
| Card-network specific thresholds | Visa: >0.9% triggers VCMP enrolment, >1.0% triggers Excessive Chargeback Merchant Program (more severe). Mastercard: >1.5% triggers MECP. American Express: >1.0%. The default alert uses Visa’s >0.9% because it’s the strictest of the three; if your customer base is Mastercard-heavy, the threshold can be raised to 1.5% (but the safer default is the strictest threshold). |
| Page cap | API page cap on charges (1,000 per refresh). For very high-volume merchants, the rate is computed on a sample; the card surfaces this caveat when sampling is in effect. |
| Time window | 30D (rolling, matching card-network monitoring window) |
| Alert trigger | >0.9% (Visa, default), customisable to >1.5% (Mastercard-heavy) or >1.0% (American Express-heavy). |
| Roles | owner, finance |
Calculation
Calculated automatically from your Stripe data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading.Worked example
A US DTC apparel brand on Shopify + Stripe, 30-day window covers 13 Mar 26 to 11 Apr 26.| Metric | Value | Threshold band |
|---|---|---|
| Successful card charges (denominator) | 6,420 | |
| Card-network chargebacks (numerator) | 58 | |
| Chargeback rate (this card) | 0.90% | AT VISA THRESHOLD |
| Open disputes (still in needs_response) | 11 | (informational) |
| Average dispute value | $228 | |
| Total at-risk in window | $13,224 |
| Window | Charges | Chargebacks | Rate |
|---|---|---|---|
| 11 Jan to 9 Feb 26 | 6,140 | 28 | 0.46% |
| 11 Feb to 12 Mar 26 | 6,280 | 39 | 0.62% |
| 13 Mar to 11 Apr 26 | 6,420 | 58 | 0.90% |
- The card is at exactly the Visa 0.9% threshold. One more chargeback in the next refresh and the alert fires above. The merchant is on the edge of VCMP enrolment, which means roughly $30/month in monitoring fees, mandated 3DS for high-risk transactions, additional Radar rules required, and a 4-month minimum monitoring period. The cost of crossing 0.9% is significant; this is the moment for action, not a moment from now.
- The trend is the real story: 0.46% → 0.62% → 0.90% over 90 days. The chargeback rate has nearly doubled in 3 months. The card alerts at the threshold; the trend card surfaces this earlier. Pair with Dispute Rate Trend to identify when the inflection started.
- The most likely cause: a fraud-attack campaign. Sustained 60% increase over 90 days isn’t normal volatility; it’s structural. Common causes: (a) the merchant launched in a new payment-friendly geography (LATAM, EMEA emerging markets) with higher chargeback baselines, (b) Radar’s tuning is too lenient, (c) a specific product launch is attracting fraud (high-resale-value items like trainers, consumer electronics). Pair with Dispute Reasons, if
fraudulentis the dominant reason and rising fastest, the cause is fraud. - What does the merchant do today? Three-step playbook. (a) Tighten Radar to block higher-risk score ranges (raise the block threshold from “high” to “elevated”); accept ~1 to 2pp lift in false-positive blocks. (b) Mandate 3DS for high-risk transactions (cards from high-risk countries, large-value, new customers). 3DS shifts liability from merchant to issuer for fraudulent disputes; reduces chargeback rate within 30 days. (c) Refund early-warning disputes pre-emptively, even if the merchant could fight them. Each pre-emptive refund avoids one chargeback against the rate.
- At 0.9%, the merchant has roughly 30 days before VCMP enrolment. Stripe’s monitoring window is 30 days; sustained breach for 4+ months can lead to account termination. But a single month above 0.9% with corrective action visible in subsequent months typically avoids termination, the network gives merchants time to fix.
Sibling cards merchants should reference together
| Card | Why pair it with Dispute Threshold Watch |
|---|---|
| Dispute Rate | The rolling-rate view. The alert fires at 0.9%; the rate card surfaces the trend leading to it. |
| Dispute Rate Trend | The leading indicator. A sustained climb from 0.4% → 0.6% → 0.8% predicts threshold breach 30 to 60 days out. |
| Open Disputes | The pipeline view. Open disputes about to file as formal chargebacks add to next month’s rate; pair to forecast threshold proximity. |
| Dispute Reasons | The diagnostic view. Threshold approaches driven by fraudulent need Radar tuning; driven by product_not_received need fulfilment improvement; driven by unrecognized need clearer billing-descriptor copy. |
| Chargeback Forecast | The predictive view. Forecasts whether next-30-day rate will breach threshold based on current open-dispute pipeline. |
| Radar Score Distribution | The fraud-prevention lever. The single highest-leverage tool for reducing chargeback rate when fraud is the cause. |
| Dispute Win Rate | The defensive view. Higher win rate doesn’t directly affect rate (the chargeback still files), but reduces dollar loss. |
| 3DS Friction Loss | The trade-off view. Mandating 3DS on high-risk transactions reduces chargebacks but creates checkout friction; the friction-loss card quantifies the trade. |
Reconciling against the vendor’s own dashboard
Where to look in Stripe Dashboard: Disputes → Analytics for the official 30-day chargeback rate. This is the rate Stripe uses internally for monitoring-program enrolment decisions. Match this card’s reading to within sync-lag timing. Stripe Radar → Risk Insights for the per-charge risk decomposition; useful for diagnosing whether Radar tuning would help. Stripe Notifications for any monitoring-program enrolment notices. Stripe sends these proactively when a merchant approaches or breaches threshold. Why our number may legitimately differ from Stripe Dashboard:| Reason | Direction | Why |
|---|---|---|
| Definition of “card chargeback rate”. Vortex IQ uses formal chargebacks ÷ successful card charges. Stripe’s official rate uses the same definition; should match closely. | Should match | If gaps appear, check that early-warning notifications are being correctly excluded. |
| Card-network specificity. Stripe Dashboard sometimes splits Visa-only and Mastercard-only rates separately; this card uses the aggregate which is the strictest interpretation. | Either, drift small | Check the per-network breakdown in Dashboard for nuance. |
| Page cap (1,000 charges). For very high-volume merchants, Vortex IQ samples; the Dashboard processes the full population. | Vortex IQ may slightly over- or under-state | Sampling bias is small in practice (<5pp on the rate). |
| Time-zone. Dashboard uses your account-level time zone; Vortex IQ runs on UTC. | Boundary days off | Doesn’t affect the 30-day rolling window meaningfully. |
| Refresh lag. Dashboard refreshes immediately; Vortex IQ refreshes at API sync interval (5 to 15 minutes). | Vortex IQ slightly stale | Wait for next refresh. |
| Card | Expected relationship | What causes legitimate divergence |
|---|---|---|
paypal.pp_dispute_rate | Stripe and PayPal dispute rates are independent; PayPal has different threshold rules | A merchant using both processors must monitor both rates separately; they don’t aggregate to a single network-threshold view. |
shopify.fraud_rate | Leading indicator at 30 to 90 day lag | Chargebacks file 30 to 90 days after the original transaction; rising Shopify fraud-flag rate today predicts rising Stripe chargeback rate next quarter. |
stripe.dispute_rate_trend | Internal identity | These cards measure the same underlying rate but at different windows / smoothing. |
Known limitations / merchant FAQs
The alert fired at 0.9%. What happens at 1.0%, 1.5%, 2.0%? At 0.9% (Visa), monitoring program enrolment begins. At 1.0%, the program tightens (more required prevention measures). At 1.5% (Mastercard), parallel Mastercard enrolment. At 2.0%+, Stripe may pause card processing until corrective action is verified. Sustained breach (4+ consecutive months above 0.9%) typically leads to Stripe account termination, which is account-level (not just chargeback-rate-level). Recovery from termination is hard; account moves to “high-risk processor” alternative providers with 5 to 8% fees vs Stripe’s 2.9%. My rate is 0.85%. Should I be worried? Yes. The threshold is not a brick wall; Stripe’s monitoring algorithms treat 0.85% as “approaching threshold” and may already be applying internal scrutiny. The right operational pattern is to act at 0.7% (15% margin below threshold) rather than waiting for the alert to fire. Set a custom alert at 0.7% if the default is too late for your operational tempo. What’s the fastest way to bring chargeback rate down? Three actions, each with different time-to-effect. (a) Refund early-warning disputes pre-emptively. Effect: immediate, every refund avoids one chargeback. Cost: the refund itself (which would have been disputed anyway, but at least no chargeback fee + no rate impact). (b) Tighten Radar to block higher-risk score ranges. Effect: 7 to 14 days (new charges flow through new rules). Cost: ~1 to 2pp false-positive on legitimate transactions. (c) Mandate 3DS for high-risk transactions. Effect: 30 to 60 days (3DS shifts liability for fraud disputes to issuer; existing chargebacks still count). Cost: ~5 to 15% checkout friction on affected transactions. Can I dispute the chargebacks aggressively to lower the rate? No, the rate counts every chargeback that filed regardless of whether you won or lost. Win rate matters for dollars-recovered, not for rate-against-threshold. The card-network monitoring programs care about whether chargebacks filed at all, the cardholder’s “I dispute this charge” event is the violation, the resolution is downstream. Why does the rate includefraudulent chargebacks I had no way to prevent?
Card-network monitoring programs treat the merchant as accountable for fraud chargebacks because the merchant is the party best positioned to prevent them (3DS, address verification, Radar tuning, fraud-screening tools). The argument “we couldn’t have prevented it” doesn’t change the rate. The right response is investing in fraud-prevention tools that reduce future fraud chargebacks; the existing ones are already counted.
My business is high-risk by category (CBD, supplements, certain SaaS). What threshold applies?
The same 0.9% / 1.5% thresholds apply to every merchant on Stripe. High-risk categories often run higher chargeback rates structurally; if your category baseline is 0.7 to 1.0%, you’re operating right at the threshold continuously. Some high-risk merchants need to move to specialised high-risk processors (which charge higher fees but have higher tolerance for chargeback rate). Confirm with Stripe’s account team whether your category is sustainable at 0.9% threshold.
Stripe’s account team isn’t responding. Who do I escalate to?
The escalation path: (1) Stripe Support via Dashboard, request “chargeback program review”. (2) If account-tier qualifies, request the Account Manager. (3) For enterprise customers (>$1M monthly volume), escalate to the Strategic Accounts team. (4) Last resort: file a formal complaint with Stripe and ask for documented program-enrolment criteria; this rarely moves Stripe but gives the merchant a paper trail if account termination later results in legal dispute. Don’t wait for Stripe to respond before taking corrective action; the corrective measures (Radar tuning, 3DS, refund-early-warnings) are entirely under merchant control.
My rate is 0.5% but trending up sharply. Should I act now or wait?
Act now. The card alerts at threshold; the trend card surfaces the trajectory. A trend rising from 0.3% → 0.5% → 0.7% over 90 days will breach 0.9% in the next 30 to 60 days at the same trajectory. Acting at 0.5% is far cheaper than acting at 0.85%, the corrective measures take 30 to 60 days to fully effect, so starting earlier prevents threshold breach.
Do early-warning disputes count toward this rate?
No. The card-network monitoring programs only count formal chargebacks (needs_response, under_review, won, lost). Early-warning notifications (Visa RDR, Mastercom Collaboration) are designed precisely to let merchants resolve issues before chargebacks file; they’re not penalised in the rate. Refunding early-warning disputes pre-emptively is the single highest-leverage action for keeping rate below threshold.
Will the rate drop after I take action?
Yes, but with lag. The 30-day rolling window means corrective actions today affect the trailing rate over the next 30 days. If you fix the cause completely on Day 1, the rate drops linearly to its new baseline by Day 30. If the rate breaches threshold on Day 5 and you fix on Day 5, expect 25 days of “above threshold” reading before the window rolls past the bad period. The best practice is to act before threshold breach; if you breach, document corrective action for Stripe’s monitoring team to soften the program response.