Stripe Disputes: The Founder's Playbook
Stripe disputes cost more than the $15 fee suggests. This guide covers how chargebacks work on Stripe, what evidence wins by reason code, how to respond within the deadline, and how to reduce your dispute rate before they file.
Contents
A Stripe dispute is an immediate reversal. The moment a cardholder contacts their bank to contest a payment, Stripe freezes the funds and debits your account. You get 7 to 21 days to respond with evidence. The card issuer decides. If you lose, the funds are gone and the $15 dispute fee is non-refundable.
This guide covers how disputes work on Stripe, what evidence wins by reason code, how to respond correctly, and how to prevent disputes before they happen.
What a Stripe dispute actually costs
The $15 dispute fee understates the real cost. A $100 chargeback that you lose costs you the $100 refund, the $15 Stripe dispute fee, plus a dispute counter fee introduced in June 2025 if you contested it and lost. Add lost fulfillment costs for physical goods and the total cost of a lost $100 dispute runs to $150 or more.
A $1 fraudulent chargeback costs US merchants $4.61 in 2025, a 37 percent jump from 2020 levels. The multiplier effect comes from fees, lost product, processing costs, and staff time spent on evidence submission.
There is also a threshold risk. Visa and Mastercard monitor dispute rates by merchant. Exceeding 0.9 percent dispute rate (Visa) or 1.5 percent (Mastercard) triggers monitoring programs that can result in fines, increased scrutiny, and in extreme cases, loss of the ability to process payments. Stripe does not publish a specific threshold, but high dispute rates are a material risk to your account.
How disputes work on Stripe
The dispute lifecycle has five stages.
1. Cardholder contacts their bank. The customer does not contact you first in most cases. Javelin data shows customers go directly to their bank in 75 percent of dispute cases. You find out when Stripe notifies you.
2. Stripe freezes the funds. The disputed amount is immediately reversed from your balance. You cannot use those funds while the dispute is open.
3. You receive the dispute notification. Stripe emails you and surfaces the dispute in your dashboard. The notification includes the reason code, the disputed amount, and your response deadline.
4. You respond with evidence. You have 7 to 21 days depending on the card network and reason code. The deadline is hard. Miss it and you lose automatically.
5. The card issuer decides. The issuing bank reviews your evidence and makes a final ruling. The process typically takes 2 to 3 months from dispute filing to resolution. The issuer's decision is final.
Dispute reason codes and what wins
Every dispute comes with a reason code that tells you what the cardholder claimed. The reason code determines what evidence wins, and submitting the wrong evidence is the most common reason merchants lose winnable disputes.
Fraudulent (unauthorized transaction)
The cardholder claims they did not authorize the charge. This is the most common reason code for subscription businesses and includes both genuine fraud and friendly fraud (a legitimate customer claiming non-authorization to avoid a charge).
Evidence that wins: AVS match showing the billing address matched on the original transaction, CVV match, IP address and device fingerprint from the original purchase, proof of prior successful charges to the same card, customer login activity logs, and delivery confirmation for physical goods.
For subscription businesses, showing a history of prior charges the customer did not dispute is often the strongest piece of evidence for a fraudulent claim on a renewal.
Subscription cancelled
The cardholder claims they cancelled the subscription before the disputed charge. This is the most common dispute type for SaaS companies.
Evidence that wins: your cancellation policy clearly presented at signup, screenshot of the customer's account showing no cancellation request was received before the billing date, your terms of service with the cancellation clause highlighted, any email correspondence with the customer about the subscription, and login activity showing the customer used the product after the date they claim to have cancelled.
The key to winning subscription cancelled disputes is documentation. If your cancellation flow generates a confirmation email, keep records of every cancellation. If no cancellation request was received, your system logs showing the absence of that request are your evidence.
Product not received / service not provided
The cardholder claims they did not receive what they paid for.
For SaaS, this usually means the customer is claiming the service was unavailable or not delivered as described. Evidence that wins: access logs showing the customer logged in and used the product during the disputed period, uptime records showing service availability, screenshots of feature usage, and any support tickets the customer filed (or the absence of any complaints before filing the dispute).
Credit not processed
The cardholder claims a refund was promised but never issued.
Evidence that wins: documentation showing no refund was promised, or if a refund was promised, evidence that it was processed (Stripe refund ID, date, amount). If a refund was genuinely owed and not processed, accepting the dispute and issuing the refund is usually the right call.
Not as described
The cardholder claims the product or service was materially different from what was advertised.
Evidence that wins: screenshots of your product description at the time of purchase, your terms of service, and usage logs showing the customer had access to exactly what was described.
Stripe Smart Disputes
Stripe Smart Disputes automates evidence submission for certain dispute types. For eligible disputes, Stripe automatically compiles and submits evidence on your behalf, including transaction data, AVS and CVV results, and Radar signals.
Smart Disputes has limited coverage for disputes that require third-party evidence: product not received, not as described, cancelled subscription, credit not processed, and services not provided. For SaaS and subscription companies, the exposure sits mostly in subscription cancellation and services-not-provided disputes.
From June 2025, Stripe charges a dispute counter fee when you contest a dispute, refunded if you win. Smart Disputes users have this counter fee waived in exchange for a 30 percent success fee on recovered amounts.
For fraud disputes on card-present or simple card-not-present transactions, Smart Disputes performs well. For the subscription-specific reason codes that SaaS companies face most often, it covers less ground.
How to respond to a dispute correctly
Respond to every dispute. An ignored dispute is an automatic loss. Even disputes you expect to lose are worth responding to, because building a response pattern and evidence library improves your rate over time.
Check the deadline first. Open the dispute in your Stripe dashboard immediately when you receive the notification. The deadline is visible and non-negotiable. Missing it forfeits the dispute.
Match your evidence to the reason code. Do not submit a generic evidence package. Read the reason code, understand what the cardholder claimed, and build evidence that directly contradicts their claim.
Be concise. Card issuers review hundreds of disputes. A 2-page summary with the key evidence highlighted is more effective than a 20-page document dump. Lead with your strongest piece of evidence.
Include a rebuttal letter. A well-structured rebuttal letter framing why the dispute is invalid and referencing the evidence you are submitting, helps issuers who skim long submissions. Keep it factual, not emotional.
Use Stripe's evidence fields correctly. Stripe's dispute response form has specific fields for different evidence types. Putting the right evidence in the right field matters. Customer communication goes in the customer communication field, not the general notes field.
Preventing disputes before they file
Winning disputes is good. Not getting them is better.
Clear billing descriptors. The number one cause of friendly fraud is customers not recognizing a charge on their statement. 75 percent of them call their bank rather than you. Your statement descriptor should be your company name or brand, not a payment processor name or a truncated string. Test how your descriptor appears on a real card statement.
Cancellation confirmation emails. Every cancellation should trigger an immediate email confirmation. This eliminates the "I cancelled but you kept charging me" dispute before it starts. Keep a log of every cancellation with timestamp, customer ID, and confirmation email sent.
Proactive communication before renewals. An email 3 to 5 days before an annual renewal fires gives customers a chance to cancel before the charge rather than dispute after it. Annual subscription disputes spike because customers forget the subscription exists until they see the charge.
Respond quickly to refund requests. A customer who asked for a refund and did not get one files a dispute. A quick refund policy, even a generous one, costs less than the dispute fee plus the time to fight it.
Use Stripe Radar. Blocking high-risk transactions before they process prevents the fraud disputes that follow. A fraudulent charge that succeeds will almost always result in a dispute. Radar's ML scoring reduces the volume of fraudulent charges that get through.
Alert on dispute rate trends. Monitor your dispute rate monthly. A rising rate is a signal that something systematic is wrong: unclear billing descriptors, a broken cancellation flow, or a surge in fraud targeting your customer segment.
What Recova adds for disputes
Recova's Disputes product handles the full dispute response workflow. When a dispute comes in through the Stripe webhook, Recova classifies the reason code, compiles the relevant evidence from your Stripe data, and generates an AI-drafted rebuttal letter. You review and submit.
For subscription cancellation disputes, Recova pulls your cancellation logs, customer login activity, and prior charge history automatically. The evidence package is built in minutes rather than hours.
Recova charges 20 percent of won disputes. Nothing on losses.
Start with a free Stripe audit to see your current dispute rate and flag any reason codes appearing with unusual frequency.
- How long do I have to respond to a Stripe dispute?
- Between 7 and 21 days depending on the card network and reason code. The deadline is visible in your Stripe dashboard when the dispute is created. Missing it results in an automatic loss.
- Does Stripe refund the $15 dispute fee if I win?
- The standard $15 dispute fee is non-refundable in most regions. From June 2025, Stripe introduced a separate dispute counter fee that is refunded if you win. Fee structures vary by region.
- What is the most common reason code for SaaS disputes?
- Subscription cancelled is the most common for SaaS companies, followed by fraudulent (unauthorized transaction). Both are winnable with the right evidence.
- What evidence wins a subscription cancelled dispute?
- Your cancellation policy shown at signup, system logs showing no cancellation request was received before the billing date, login activity showing the customer used the product after the claimed cancellation date, and your terms of service with the cancellation clause highlighted.
- What dispute rate triggers Stripe monitoring?
- Stripe follows card network thresholds. Visa's threshold is 0.9 percent dispute rate before monitoring programs begin. Mastercard's threshold is 1.5 percent. Staying well below 0.6 percent is a safe target.
- Should I accept a dispute I know I will lose?
- Usually yes. Accepting saves the counter fee and your time. If the dispute is frivolous and you have strong evidence, contesting is worth it. But for disputes where the customer has a valid grievance, a clean acceptance is better than a contested loss.
