whatpayment .
What you'll get
    Skip to Whop

    Stripe risk management guide

    Stripe chargeback prevention : how to stay under 0.75% before they hold your funds

    Practical guide to keeping your Stripe dispute rate below the 0.75% warning threshold. Covers Visa and Mastercard requirements, billing descriptors, chargeback alerts, Stripe Radar rules, RDR, evidence submission, and what happens if you cross the line.

    Gaetan Chardon

    Gaetan Chardon

    Founder & Editor

    Stripe chargeback prevention : how to stay under 0.75% before they hold your funds

    Some links in this article are affiliate links. We may earn a commission if you sign up, at no extra cost to you. Read our affiliate disclosure.

    Stripe will start watching your account closely at a 0.75% dispute rate. Cross 1.0%, and you are in reserve-hold territory, potentially losing access to payouts for months. The gap between "everything is fine" and "Stripe is holding my funds" is narrower than most creators realize. If you are running a course, coaching program, paid community, or any digital product with recurring billing, your dispute rate is the single most important metric to monitor, more important than conversion rate, more important than churn. Because if chargebacks push you past the threshold, none of those other metrics matter.

    This guide covers the practical, layered approach to staying under 0.75%. No theory. No vague advice about "providing great customer service." Specific tools, specific configurations, and the exact sequence of defenses that keeps your Stripe account healthy.

    The thresholds you need to know

    Stripe's internal risk thresholds are informed by the card network monitoring programs. Here is how the system works at each level.

    Visa Dispute Monitoring Program (VDMP)

    Visa tracks merchants in two tiers:

    • Early Warning : 0.65% dispute rate AND 75 disputes in a calendar month. Visa notifies the acquiring bank (in this case, Stripe). No fines yet, but you are on the radar.
    • Standard Program : 0.9% dispute rate AND 100 disputes in a calendar month. Visa begins fining the acquiring bank $50 per dispute, escalating monthly. The bank passes these costs to you (or terminates you to avoid them).
    • Excessive Program : 1.8% dispute rate AND 1,000 disputes. Fines escalate to $10,000-25,000 per month. Almost certain termination.

    Mastercard Excessive Chargeback Program (ECP)

    • Chargeback Monitored Merchant : 1.0% dispute rate AND 100 chargebacks in a calendar month. Mastercard notifies the acquirer. Remediation plan required within 45 days.
    • Excessive Chargeback Merchant : 1.5% dispute rate AND 150 chargebacks. Fines of $1,000-200,000 per month. MATCH list risk.

    Where Stripe draws the line

    Stripe acts before you hit network thresholds, because Stripe (as the acquirer) pays the fines if you do not. In practice:

    • 0.75% dispute rate : Stripe's internal warning trigger. You may receive an email asking you to address your dispute rate. No action yet, but your account is flagged for monitoring.
    • 1.0% dispute rate : reserve hold territory. Stripe may hold 5-25% of your incoming volume for 90-180 days. Payout delays begin.
    • Above 1.0% sustained : account termination risk. If your rate does not improve within 30-60 days, Stripe may terminate your account and potentially report you to the MATCH list.

    If you are already past 0.75%, read our guide on Stripe holding funds for immediate steps. If you are past 1.0%, see our Stripe account frozen playbook. This article focuses on prevention: staying safely below the line.

    Layer 1 : fix your billing descriptor

    The most overlooked cause of chargebacks is the billing descriptor, the text that appears on a customer's bank or credit card statement. If a customer does not recognize the charge, they call their bank and file a dispute. This is not fraud. It is confusion. And it is completely preventable.

    In Stripe Dashboard, go to Settings, then Business settings, then Public details. You will see two fields:

    • Statement descriptor : the default text that appears on all charges. Maximum 22 characters. Use your brand name, not your legal entity name. "COACHINGBYANNA" is better than "ANNA SMITH LLC." "FITPRO ACADEMY" is better than "FPA HOLDINGS INC."
    • Shortened descriptor : used when there is not enough space on the statement for the full descriptor. Maximum 10 characters. Use the most recognizable abbreviation of your brand.

    You can also set dynamic descriptors per transaction using the statement_descriptor_suffix parameter in the Stripe API. This appends up to 10 characters to your base descriptor. Use it to include the product name: "FITPRO* COURSE" or "FITPRO* COACHING." This makes it immediately obvious what the charge is for.

    One overlooked detail: test your descriptor by making a small real charge to your own card and checking how it renders on your bank statement. Some banks truncate differently. If your descriptor renders as "FITPRO ACADE" because the bank truncates at 12 characters, the customer still may not recognize it.

    Layer 2 : pre-transaction confirmation emails

    Send a purchase confirmation email within 60 seconds of checkout. This email serves a specific anti-chargeback function: it creates a reference the customer can find when they see an unfamiliar charge on their statement.

    The confirmation email should include:

    • Your brand name (matching the billing descriptor)
    • The exact amount charged
    • The product or service purchased
    • Your support email address
    • If it is a subscription, the renewal date and cancellation instructions

    For subscriptions, also send a renewal reminder email 3-7 days before each billing cycle. Subscription chargebacks from customers who forgot they were subscribed are one of the most common dispute types for creators. A simple reminder email ("Your FitPro Academy membership renews on June 15 for $49. To cancel or pause, click here.") eliminates this category almost entirely.

    Layer 3 : proactive refund policies

    A refund you initiate does not count toward your dispute rate. A chargeback does. This math changes everything about how you should handle unhappy customers.

    The optimal refund strategy for chargeback prevention:

    • Make refunds easy to request. Put a "Request a refund" link in your post-purchase emails and on your account page. The harder refunds are to find, the more customers skip your process and go straight to their bank.
    • Respond within 24 hours. A customer who emails asking for a refund on Monday and hears nothing by Wednesday will file a chargeback on Thursday. Speed matters more than policy details.
    • For high-ticket products ($500+), use a cancellation flow instead of a refund wall. Offer a 30-minute "save" call where you understand the issue and offer alternatives (different product, pause, partial refund). If the customer still wants out, process the refund immediately. This approach recovers 20-40% of would-be refunds while ensuring the rest get refunded before they chargeback.
    • Publish your refund policy prominently. It must be visible before checkout (not buried in terms of service) and linked from your confirmation email. This is also critical for chargeback evidence if you do get a dispute.

    The counterintuitive truth: creators with generous, easy-to-access refund policies have lower chargeback rates than creators with strict "no refund" policies. Because when you block the refund path, customers use the chargeback path instead. And the chargeback path costs you significantly more (dispute fee, lost funds, rate impact).

    Layer 4 : chargeback alerts (Ethoca and Verifi)

    Chargeback alert services notify you when a cardholder contacts their bank about a charge, before the formal chargeback is filed. You then have a window (typically 24-72 hours) to issue a refund, which prevents the chargeback from being created.

    Two systems dominate the market:

    • Ethoca (owned by Mastercard) : covers approximately 40% of US card-issuing banks, including major issuers like JPMorgan Chase and Bank of America. Provides alerts for Visa, Mastercard, and other card brands despite being Mastercard-owned.
    • Verifi CDRN (Cardholder Dispute Resolution Network) (owned by Visa) : covers Visa-issuing banks primarily. Provides the pre-dispute alert that gives you a refund window.

    Most merchants subscribe to both for maximum coverage. You can sign up directly with Ethoca and Verifi, or use a third-party chargeback management provider (Chargebacks911, Midigator, Chargeflow) that bundles both into a single dashboard with automated refund rules.

    Cost varies. Direct enrollment with Ethoca and Verifi typically runs $25-40 per alert. Third-party providers charge $15-35 per alert or a monthly subscription plus per-alert fees. At scale, this is significantly cheaper than the cost of a chargeback ($15 Stripe dispute fee + the transaction amount + the rate impact).

    Rapid Dispute Resolution (RDR)

    RDR is a Visa program (operated through Verifi) that takes alerts one step further: it automatically resolves qualifying disputes based on rules you set in advance. You define criteria like "auto-refund disputes under $100" or "auto-refund disputes on transactions older than 60 days," and the system executes without manual intervention. The dispute never reaches Stripe, never appears in your dashboard, and never counts toward your rate.

    RDR is particularly useful for subscription businesses where a significant portion of chargebacks are from customers who simply want to cancel but filed a dispute instead of contacting you. Setting an auto-refund rule for subscription disputes under your average ticket price eliminates these with zero manual effort.

    Layer 5 : Stripe Radar rules

    Stripe Radar is included free with every Stripe account (basic rules) or available as Radar for Fraud Teams at $0.07 per screened transaction (advanced rules and manual review queues). For chargeback prevention, focus on these rule categories:

    Block rules (reject the transaction)

    • Velocity limits : block if the same card attempts more than 3 transactions in 1 hour. Fraudsters test stolen cards with rapid small charges.
    • Country mismatch : block if the card country does not match the IP country AND the risk score is above 65. This catches card-not-present fraud without blocking legitimate travelers.
    • Disposable email domains : block or review transactions from disposable email providers (mailinator.com, guerrillamail.com, etc.). These correlate heavily with fraud and friendly fraud.

    Review rules (flag for manual review)

    • High-ticket first purchase : review if the transaction amount exceeds $500 AND it is the customer's first purchase. This catches both stolen cards and impulse purchases that lead to buyer's remorse chargebacks.
    • Risk score threshold : review if Radar risk score is above 50. The default Stripe threshold blocks at 75; lowering your review trigger to 50 catches borderline cases you can verify manually.

    3D Secure rules

    • Require 3DS for transactions above your threshold. For most creators, requiring 3D Secure on transactions above $200-300 provides meaningful fraud liability shift without materially affecting conversion on lower-ticket products.
    • Require 3DS when Radar risk score exceeds 40. This selectively adds friction only for suspicious transactions.

    A critical point: Radar prevents fraud chargebacks. It does not prevent friendly fraud, service disputes, or subscription confusion chargebacks. Radar is one layer, not the whole solution.

    Layer 6 : winning disputes you cannot prevent

    Even with all prevention layers active, some chargebacks will happen. Your win rate on dispute evidence submission directly affects your bottom line and your dispute rate (won disputes are removed from rate calculations on some card brands).

    Build a reusable evidence template that includes:

    • Proof of delivery : screenshots of course platform access logs, Discord server join date, download timestamps, coaching call recordings. For digital products, IP-stamped access logs are the strongest evidence.
    • Terms acceptance : screenshot or log showing the customer accepted your terms of service and refund policy at checkout. If you use Stripe Checkout, the terms acceptance is logged automatically. If you use a custom checkout, log it yourself.
    • Customer communication : email threads showing the customer engaged with the product, asked questions, or received support. This proves they knew what they bought and used it.
    • Refund policy : a link to (and screenshot of) your published refund policy, showing it was available before purchase.
    • Transaction details : the customer's name, email, IP address, device information. Stripe provides most of this in the payment object.
    • AVS and CVC match : if the address verification and CVC matched at checkout, include this. It weakens fraud claims.

    Submit evidence as early as possible. Do not wait until the deadline. Banks review disputes in the order received, and early submissions sometimes resolve before reaching formal arbitration.

    For a detailed walkthrough of Stripe's evidence submission process and escalation tactics when disputes go against you, see our guide on Stripe account termination.

    What happens if you cross the threshold

    If your prevention layers fail and your dispute rate climbs above 1.0%, here is the sequence of events you should prepare for.

    Stage 1 : the email (0.75-1.0%)

    Stripe sends a notification asking you to address your dispute rate. This email is not a threat yet, but it is a signal that your account is being actively monitored. You typically have 30 days to bring your rate down. Take it seriously. Every action described in this guide should be implemented within a week of receiving this email.

    Stage 2 : reserve hold (1.0%+)

    Stripe imposes a rolling reserve on your account, holding 5-25% of incoming volume for 90-180 days. Payouts continue for the remaining percentage, but your cash flow takes a significant hit. The reserve releases gradually as transactions age past the chargeback window. If you are in this stage, read our Stripe fund holds guide for detailed tactics.

    Stage 3 : account termination

    If your dispute rate remains above 1.0% for 60-90 days despite the reserve, Stripe may terminate your account. Termination means:

    • All funds held for 90-180 days against potential chargebacks
    • No new transactions processed
    • Potential MATCH list placement. Stripe can add your business to the MATCH list, a Mastercard database shared across all payment processors. Being on MATCH makes it nearly impossible to get approved by another traditional processor for five years.

    The MATCH list consequence is the most severe. It does not just affect Stripe. It affects your ability to use Square, PayPal (for card processing), Adyen, or any other traditional acquirer. For creators in this situation, Merchant of Record platforms become the primary path forward, because MoR platforms process transactions under their own merchant account, making your MATCH status irrelevant.

    The Merchant of Record alternative

    Merchant of Record (MoR) platforms like Whop, Paddle, and Lemon Squeezy fundamentally change the chargeback equation. When you sell through an MoR, the platform is the merchant of record on the transaction. The customer's bank statement shows the MoR's name, disputes go to the MoR, and the MoR handles the evidence submission and representment process.

    For Whop specifically:

    • Whop automatically handles and fights disputes on your behalf. You do not submit evidence, manage deadlines, or monitor rates.
    • Just 2.7% + $0.30 per transaction. No subscription required. No hidden costs.
    • Whop helps protect from holds and account closures because compliance reviews trigger at predictable revenue milestones, not as surprise freezes.
    • Named social proof: Iman Gadzhi made $25M+ on Whop. TJR runs $1M/month. Airrack hits $250K/month. These creators operate in verticals with structurally higher dispute rates, and they scale without chargeback-related account actions.

    The tradeoff is pricing. Whop's effective rate (approximately 3.0% all-in) is higher than Stripe's 2.9% + $0.30. But that comparison ignores the hidden costs of self-managing chargebacks on Stripe: alert fees ($25-40 per alert), Radar for Fraud Teams ($0.07 per transaction), dispute fees ($15 per chargeback), and the catastrophic cost of account termination. For creators in dispute-prone verticals, the MoR model is often cheaper on a total-cost basis.

    The complete prevention checklist

    Here is the full stack, ordered by impact. Implement the first three within a week. Add layers 4-7 as your volume grows.

    LayerWhat it preventsSetup timeCost
    Clear billing descriptorUnrecognized charge disputes10 minutesFree
    Confirmation and renewal emailsForgotten subscription disputes1-2 hoursFree (or email tool cost)
    Proactive refund policyBuyer's remorse chargebacks1 hourFree
    Chargeback alerts (Ethoca + Verifi)All dispute types (pre-filing intercept)1-3 days (enrollment)$25-40 per alert
    RDR auto-resolutionLow-value and subscription disputes1-2 daysPer-resolution fee
    Stripe Radar rulesFraud chargebacks1-2 hoursFree (basic) or $0.07/txn (advanced)
    3D Secure for high-ticketFraud liability shift30 minutesFree
    Evidence templateImproves win rate on filed disputes2 hours (one-time)Free

    The bottom line

    Chargeback prevention on Stripe is not one tool or one setting. It is a layered defense where each layer catches a different type of dispute. Billing descriptors stop the "I don't recognize this charge" disputes. Confirmation emails stop the "I forgot I bought this" disputes. Proactive refunds stop the "I want my money back and you're not responding" disputes. Chargeback alerts intercept disputes before they are filed. Radar blocks fraud. 3DS shifts liability. Evidence submission wins the disputes that get through everything else.

    If you are running a business in a vertical where dispute rates run structurally higher (coaching, courses, paid communities, info-products, financial education), consider whether self-managing all of these layers on Stripe is the right use of your time. Merchant of Record platforms like Whop handle the entire dispute lifecycle for you, which means you focus on your product instead of your chargeback rate. That is not a judgment call on Stripe. Stripe is an excellent payment processor for businesses with low dispute rates. The question is whether your business fits that profile.

    Frequently asked questions

    What is Stripe's chargeback threshold before they freeze your account ?

    Stripe begins internal review at 0.75% dispute rate in a rolling 30-day window. At 1.0% or above, you enter territory where Stripe may impose reserve holds (5-25% of volume), restrict payouts, or terminate your account entirely. These thresholds align with Visa and Mastercard monitoring programs, which impose fines on acquiring banks whose merchants exceed 0.9% (Visa) or 1.0% (Mastercard).

    Do refunds count as chargebacks on Stripe ?

    No. A refund you initiate proactively does not count toward your dispute rate. Only formal chargebacks filed by the cardholder through their bank count. This is why proactive refund policies are one of the most effective prevention tactics: a $200 refund today prevents a $200 chargeback plus a $15 Stripe dispute fee plus damage to your dispute rate.

    What is the difference between Ethoca alerts and Verifi CDRN ?

    Both are early warning systems that notify you when a cardholder contacts their bank about a charge, before the formal chargeback is filed. Ethoca (owned by Mastercard) covers roughly 40% of US card-issuing banks. Verifi CDRN (owned by Visa) covers Visa-issuing banks. When you receive an alert, you can issue a refund immediately, which prevents the chargeback from being filed. Most merchants use both services for maximum coverage. Third-party providers like Chargebacks911 and Midigator bundle both into a single dashboard.

    What is Rapid Dispute Resolution (RDR) and how does it work with Stripe ?

    RDR is a Visa program (through Verifi) that automatically resolves disputes before they become formal chargebacks. You set rules in advance (for example, "auto-refund any dispute under $50" or "auto-refund any dispute on transactions older than 90 days"). When a cardholder initiates a dispute, the RDR system checks your rules and, if a match is found, issues the refund automatically. The dispute never reaches Stripe, never hits your dashboard, and never counts toward your dispute rate. Setup requires a Verifi account or a third-party chargeback management provider.

    Can Stripe Radar completely prevent chargebacks ?

    No. Stripe Radar blocks fraudulent transactions before they process, which prevents fraud-related chargebacks. But many chargebacks are not fraud. They are "friendly fraud" (buyer regret, forgotten subscriptions, unrecognized billing descriptors) or service disputes ("product not as described"). Radar cannot prevent these because the original transaction was legitimate. You need a combination of Radar for fraud prevention, clear billing descriptors for recognition, proactive refunds for unhappy customers, and chargeback alerts for early interception.

    What happens if I get put on the MATCH list ?

    The MATCH list (Member Alert to Control High-Risk Merchants) is a Mastercard database shared across all payment processors. If Stripe terminates your account for excessive chargebacks or fraud and reports you to MATCH, most traditional processors will decline your application for five years. However, Merchant of Record platforms like Whop, Paddle, and Lemon Squeezy are not affected by MATCH because you are selling through their merchant account, not your own. This is one of the key advantages of the MoR model for creators in high-dispute verticals.

    How long does Stripe give me to submit chargeback evidence ?

    Stripe gives you the window set by the card network, which is typically 7-21 days from the dispute notification date (varies by issuing bank and card brand). The countdown starts when the dispute appears in your Stripe dashboard. Submit evidence as early as possible. Late submissions cannot be accepted, and Stripe automatically accepts the chargeback if you miss the deadline.

    Does 3D Secure completely protect against chargebacks ?

    3D Secure shifts fraud liability from you to the card-issuing bank for transactions that complete the 3DS authentication. If a cardholder authenticated with 3DS and later files a fraud chargeback, the issuing bank absorbs the loss, not you. However, 3DS does not protect against non-fraud chargebacks (service disputes, "product not as described," subscription cancellation disputes). It also adds friction to checkout, which can reduce conversion rates by 5-15% depending on your market. Use it strategically: enable for high-ticket transactions and flagged orders, consider skipping for low-value repeat purchases from known customers.

    Last reviewed : 2026-05-08. Visa VDMP and Mastercard ECP thresholds are current as of 2026. Stripe's internal thresholds are based on published documentation and creator interviews, not official Stripe disclosures. Nothing here is legal or financial advice. WhatPayment may earn a commission on certain links. Read our affiliate disclosure.

    Keep reading

    The newsletter

    New comparisons. New data. Once a month.

    Honest write-ups on payment processors, sales tax compliance, and the platforms creators are quietly switching to. No spam, no AI-generated filler.

    No spam. Unsubscribe anytime.