Dispute Intelligence · 2026
Every SaaS founder memorizes the Visa 0.9% threshold. Stripe terminates accounts at 0.5–0.7% — well before you ever trigger a card network program. This is the complete 2026 guide to chargebacks, dispute reason codes, the 21-day evidence window, friendly fraud, and the pre-ban alert system that keeps your Stripe account alive.
5
Dispute thresholds
25+
Reason codes covered
40–65%
Win rate with automation
14 days
Pre-ban alert window
Quick answer
A chargeback is a forced payment reversal initiated by the cardholder's bank — not Stripe and not the merchant. On Stripe, merchants have 7–21 days to submit evidence and contest a dispute. Chargeback rates above 1% trigger processor warnings; above 2% risk merchant account termination. Friendly fraud — cardholders disputing legitimate charges — accounts for 40–80% of all chargebacks. Winning a dispute returns the original transaction amount minus the dispute fee.
Overview
A failed payment costs you revenue. A chargeback can cost you your entire Stripe account.
This distinction — payment failure versus dispute — separates how SaaS founders should think about billing protection. Payment failures are a recoverable billing problem. Disputes are a survival problem. Yet most billing guides treat them the same way.
The critical fact most founders learn too late: Stripe operates its own internal monitoring system that is more conservative than any card network threshold. Stripe may restrict your account, require a reserve fund, or terminate your account entirely at a dispute ratio of approximately 0.5–0.7% — before you ever cross Visa's 0.9% standard threshold.
The threshold you know is not the threshold that ends your business. Stripe's internal limit is.
This guide covers everything: the complete threshold matrix, every reason code across Visa, Mastercard, and American Express, the dispute lifecycle and evidence deadlines, automated evidence assembly, friendly fraud detection, and the 14-day pre-ban alert window.
Why SaaS Is High-Risk
01
Annual subscriptions that auto-renew without sufficient advance notice are the single largest source of subscription chargebacks. A customer who forgot they signed up a year ago sees a $299 charge and files a dispute before thinking to contact you.
02
Free trials that convert to paid plans without clear communication, or low-cost plans that accumulate over months, create disputes from customers who genuinely do not recognize the charge — even though it is entirely legitimate.
03
If your Stripe billing descriptor says "RECURFLUX-SOFTWR" instead of your actual product name, customers may file an unrecognized transaction dispute even for charges they authorized. Descriptor mismatch is the most preventable source of disputes.
04
Customers who want a refund but believe you have a no-refund policy file a chargeback instead. This is the fastest-growing dispute category — increasing approximately 25% annually — and also the most winnable if you have proper evidence of service delivery.
Part 1 · Thresholds
Part 1
Every SaaS founder processing through Stripe should have these numbers memorized. The most dangerous threshold is the one Stripe does not publish.
| Program | Threshold | Consequence |
|---|---|---|
| Stripe (internal) | ~0.5–0.7% | Account review, restriction, or termination |
| Visa VDMP (standard) | 0.9% | Monitoring program + fines $5K–$100K/month |
| Visa VDMP (high-risk) | 1.8% | Accelerated enforcement timeline |
| Mastercard CMM | 1.0%–1.5% | Chargeback Monitored Merchant status |
| Mastercard ECM | 1.5%+ | Excessive Chargeback Merchant + $1K–$100K/month fines |
The three-month misunderstanding: Many founders assume they have three months to fix a threshold breach. They do not. Visa's monitoring program begins the moment the threshold is crossed — the three-month window refers to sustained breaches triggering escalated enforcement, not a grace period. And Stripe acts before the card networks do.
Part 2 · Reason Codes
Part 2
Each card network uses its own reason code taxonomy. Submitting the wrong evidence for a code is as bad as submitting no evidence at all. Know your code before you build your response.
| Code | Description |
|---|---|
| 10.4 | Other Fraud — Card Present Fraud |
| 10.5 | Recurring Transaction Not Honored Authorization |
| 11.1 | Card Recovery Bulletin Authorization |
| 11.2 | Declined Authorization Authorization |
| 12.1 | Late Presentment Processing Error |
| 12.6 | Duplicate Processing Processing Error |
| 13.1 | Services Not Provided Consumer Dispute |
| 13.2 | Cancelled Recurring Transaction Consumer Dispute |
| 13.3 | Not as Described Consumer Dispute |
| 13.6 | Credit Not Processed Consumer Dispute |
Most impactful for SaaS: 10.5 (Recurring Transaction Not Honored) and 13.1 (Services Not Provided). Together they account for 60–70% of subscription chargebacks.
| Code | Description |
|---|---|
| 4807 | Warning Bulletin File Authorization |
| 4808 | Required Authorization Not Obtained Authorization |
| 4834 | Point of Interaction Error Processing Error |
| 4841 | Cancelled Recurring or Digital Goods Transaction Consumer |
| 4853 | Cardholder Dispute (Services Not Provided) Consumer |
| 4863 | Cardholder Does Not Recognize Transaction Fraud |
| 4871 | Chip/PIN Transaction Fraud Fraud |
Pre-arbitration risk: Unlike Visa, Mastercard disputes can enter a pre-arbitration phase if either party contests the initial decision — adding $250–$500 in fees and 15–30 days to the timeline.
| Code | Description |
|---|---|
| A01 | Charge Amount Exceeds Authorization Amount Authorization |
| A02 | No Valid Authorization Authorization |
| C02 | Credit Not Processed Credit |
| C08 | Goods/Services Not Received Goods/Services |
| C14 | Paid by Other Means Goods/Services |
| C31 | Goods/Services Not as Described Goods/Services |
| FR2 | Fraud — Card-Not-Present Transaction Fraud |
| M10 | Recurring Charges — Cancelled Recurring |
Amex note: Amex operates as both network and issuer for most of its cards — meaning it evaluates disputes with more issuer-side information than Visa/MC disputes, which generally lowers merchant win rates on borderline cases.
Part 3 · Lifecycle
Part 3
Missing a single deadline is equivalent to conceding the dispute. The disputed amount, the $15 fee, and the ratio impact all remain regardless of the merits of your case.
Phase 1
Dispute Filed
Day 0
What happens
Customer contacts bank. Stripe creates Dispute object. Funds immediately deducted from balance and held in escrow.
Your action
charge.dispute.created webhook fires. 21-day evidence clock starts.
Phase 2
Evidence Window
Days 1–21
What happens
Your window to submit dispute evidence. Deadline is absolute — late submissions are automatically rejected.
Your action
Assemble: subscription agreement, usage logs, billing history, renewal emails, cancellation policy disclosure.
Phase 3
Network Review
Days 21–75
What happens
Card network reviews your evidence vs. customer claim. Funds remain in escrow. Mastercard may enter pre-arbitration (+30 days).
Your action
Wait. Track the dispute object status via Stripe dashboard or webhook.
Phase 4
Resolution
Day 75+
What happens
Network issues final decision. Win: funds returned (minus $15 fee). Lose: amount + $15 permanently deducted.
Your action
Dispute counts toward ratio regardless of outcome. Track patterns for prevention.
The ratio reality: Whether you win or lose, every dispute counts toward your dispute ratio. Winning recovers the revenue but does not improve your standing with Stripe or the card networks. Dispute prevention is the only strategy that eliminates both the financial loss and the ratio impact.
Part 4 · Evidence
Part 4
The industry average win rate for merchants who submit manually assembled dispute evidence is approximately 25%. Merchants using automated evidence collection win 40–65% — a 15–40 percentage point improvement driven by completeness, speed, and network-specific formatting.
Source 1
Every email your service sent to the customer — onboarding, subscription terms, billing receipts, renewal notices, support responses — timestamped and formatted per network requirements.
Source 2
Login timestamps, feature access records, session durations, and API call volumes from the disputed billing period. Directly counters 13.1 (Services Not Provided) and 4853 (Mastercard equivalent).
Source 3
Complete timeline of payment attempt records showing the authorization date, retry cadence, and the customer's interactions with the Hosted Payment Portal.
Source 4
Timestamped record of when the customer accepted your terms of service, what those terms said about recurring billing and renewal, and the cancellation process.
Source 5
Proof of when, where, and how your refund and cancellation policies were presented — at signup, in billing emails, and in the payment portal.
Source 6
The customer's complete subscription lifecycle. A 6-month history of $49/month charges followed by a dispute on month 7 tells a very different story than a first-month dispute on a new account.
Evidence formatting by network
Visa: Evidence organized by specific reason code category, with mandatory fields per code.
Mastercard: Narrative response statement with supporting attachments. Pre-arbitration requires a formal rebuttal letter.
American Express: Concise factual statement (under 500 words) with attached supporting documents.
This is where manual evidence most commonly fails — even when the underlying documentation is strong. Each network requires evidence organized differently. Wrong format = automatic disadvantage.
Part 5 · Pre-Ban Alerts
Part 5
When a Stripe account is terminated, the merchant is placed on the MATCH list — a shared database maintained by Mastercard that all major payment processors check before onboarding new merchants. MATCH list entries persist for five years. For a SaaS company, Stripe termination is not a billing problem. It is a survival problem.
When a Stripe merchant account is terminated:
Root Cause Identification
Review the customers driving dispute volume. Is it one plan type? One acquisition channel? One geographic region? Segment your dispute data to identify the source.
Preventive Customer Outreach
Proactively contact customers showing dispute risk signals: inactive users, customers who contacted support about cancellation, annual renewal accounts in the next 30 days.
Billing Descriptor & Communication Fix
If disputes are driven by unrecognized charge complaints, update your Stripe billing descriptor immediately. Review your renewal notification email timing and content.
Stripe Communication
If the ratio improvement is insufficient, proactively communicate with Stripe's risk team — demonstrating awareness of the issue, documenting corrective actions taken, and showing a credible remediation path.
Part 6 · Friendly Fraud
Part 6
Friendly fraud — also called first-party fraud — occurs when a customer who authorized a charge files a dispute to recoup the payment rather than requesting a refund directly. Growing approximately 25% annually. Most winnable category if you have proper evidence of service delivery and authorization.
Trigger
Annual plan renewals
Customer forgot about the subscription. Charge appears as an unexpected expense a year after signup.
Trigger
Low product usage
The charge feels unjustifiable in retrospect. Low session count makes it easy to rationalize as "unused."
Trigger
No-refund policy
Customer wants a refund but believes they cannot get one through normal channels. Chargeback becomes the perceived only recourse.
Trigger
Hidden cancel button
Customer cannot find the cancellation flow quickly. Files a dispute as the faster path to stopping the charges.
4-signal friendly fraud detection
Usage recency
Time since last login vs. disputed billing period — low usage is a friendly fraud signal
Support contact history
Customers who filed disputes without prior support contact are more likely friendly fraud
Chargeback timing
Disputes filed within 2 days of renewal charge vs. mid-cycle have different root cause profiles
Billing history length
6+ month billing history followed by sudden dispute is a high-confidence friendly fraud indicator
Part 7 · Prevention
Part 7
Every dispute you prevent is worth more than every dispute you win. Prevention eliminates the disputed revenue loss risk, the $15 fee, and the ratio impact. Winning a dispute only recovers the revenue — it does not reduce your ratio.
Cancellation Flow with Exit Survey
Converts 15–25% of would-be cancellations into pauses or plan downgrades — reducing churn and chargeback-via-abandonment simultaneously.
Renewal Notification Emails (30 and 7 days)
Eliminates annual plan renewal surprise — the single largest source of subscription chargebacks. Clear date + amount + cancellation link.
Billing Descriptor Clarity
Match your Stripe descriptor to your product name, not your legal entity. "RECURFLUX" beats "RECURFLUX TECHNOLOGIES LTD." for recognition.
Frictionless Cancellation Path
Counterintuitive: easy cancellation reduces chargebacks. Customers who find the cancel button do not file disputes.
Real-Time Dispute Rate Monitoring
Early warning before you cross Stripe's internal threshold. Trigger at 75% of any network threshold — giving you 14 days to act.
FAQs
What is the Visa dispute threshold for SaaS merchants?
Visa's standard threshold is 0.9% of transactions sustained across three consecutive months, with a minimum of 100 disputes/month. High-risk merchants face an accelerated threshold of 1.8% over two months. Critical distinction: Stripe's own internal threshold (~0.5–0.7%) will trigger account action before you ever reach Visa's limit.
How long do I have to respond to a Stripe dispute?
You have 7–21 days from the dispute filing date to submit evidence, depending on the card network and reason code. This deadline is absolute — late submissions are automatically rejected without review, regardless of the merits of your case.
What is the MATCH list and how do I avoid it?
The MATCH list (Member Alert to Control High-Risk Merchants) is a Mastercard-maintained database of terminated merchants. Placement occurs when Stripe terminates your account for excessive disputes or fraud. MATCH entries persist for 5 years and are checked by every major payment processor before onboarding. Avoidance: monitor your dispute ratio in real time and act before Stripe's internal threshold.
What evidence do I need to win a Stripe dispute?
Winning evidence typically includes: the subscription agreement with timestamp, renewal notification emails sent before the disputed charge, service usage logs (login timestamps, feature access, API calls), your cancellation and refund policy as presented at signup, and the customer's billing history. The specific documents required vary by reason code.
What is friendly fraud in SaaS?
Friendly fraud occurs when a customer who authorized a charge files a chargeback to recoup the payment instead of requesting a refund. Most common after annual renewals, during low-usage periods, or when a no-refund policy leaves chargeback as the perceived only option. It is the most winnable dispute category — if you have proper evidence of service delivery and authorization.
Does winning a dispute remove it from my dispute ratio?
No. Whether you win or lose, every dispute counts toward your dispute ratio. Winning recovers the revenue but does not protect your account standing. Dispute prevention — stopping the filing before it happens — is the only strategy that reduces both the financial loss and the ratio impact simultaneously.
What is the difference between a Visa and Mastercard chargeback?
Both use the same core reversal process. Key differences: Mastercard disputes can enter a pre-arbitration phase if either party contests the initial decision (adds $250–$500 in fees and 15–30 days). Visa disputes are generally final after the review period. Amex disputes are faster (15–30 days) because Amex operates as both the network and issuer.
Related Features
Related Features
Run the Numbers
Run the Numbers
The fee is visible. The lost LTV from a customer who disputed and churned is not.
Revenue at Risk
Failed payments and chargebacks often share the same root cause: bad payment data.
See the monthly revenue at risk from failures before they escalate into disputes — and what recovering them is worth.
Calculate →LTV Impact
A recovered payment keeps the customer. A disputed charge loses them permanently.
See how payment recovery rate affects your average LTV — and what one additional year of retention is worth in ARR.
See LTV impact →ROI Calculator
Preventing a chargeback is worth more than winning one. Here's the math.
See how a 20-point improvement in payment recovery affects your ARR — before disputes enter the equation at all.
See the ROI →Dispute intelligence
Run the free Recurflux Analyzer to see your real-time dispute exposure, ratio trajectory, and the specific customers driving your dispute volume.