Stripe Disputes: How Merchants Respond and Win [2026]
Stripe disputes cost $15 per case and must be answered through the Stripe Dashboard within 5 to 7 days. This guide explains exactly how the Stripe dispute system works, what evidence Stripe accepts, and what separates merchants who consistently win disputes from those who lose them.
Have a Stripe dispute open right now?
ChargeMate connects to Stripe and generates your rebuttal letter in minutes — tailored to the exact dispute reason.
How Stripe Disputes Work
Stripe occupies an unusual position in the payment infrastructure: it functions as the payment processor and acquirer for most merchants who use it. Unlike a traditional acquiring bank, Stripe manages the entire dispute process within its own dashboard and handles communication with card networks on your behalf.
When a cardholder contacts their bank to dispute a charge made through Stripe, the sequence is:
- 1The customer calls their bank or files a dispute through their banking app.
- 2The issuing bank reverses the transaction, credits the customer's account, and notifies the card network (Visa, Mastercard, Amex, or Discover).
- 3The card network routes the chargeback to Stripe as the acquirer.
- 4Stripe deducts the disputed amount from your Stripe balance and charges a $15 dispute fee.
- 5Stripe notifies you by email and creates a dispute record in your Dashboard under Disputes.
- 6Stripe's Dashboard displays the dispute reason and a submission deadline — typically 5 to 7 days from when the dispute was created.
- 7You submit evidence through the Dashboard. Stripe compiles your evidence and forwards it to the issuing bank.
- 8The issuing bank reviews the evidence and makes a final decision.
A critical point that confuses many merchants: Stripe's internal deadline (5–7 days) is shorter than the card network's formal deadline (typically 30 days or more). Stripe sets a shorter window to give itself time to package and submit your evidence before the network deadline. You must respond by Stripe's deadline — not the network's. The network deadline is not directly accessible to you; Stripe is the intermediary.
| Step | Who Acts | Timeline |
|---|---|---|
| Dispute filed by customer | Card issuer | Day 0 |
| Stripe notifies merchant | Stripe | Day 0–1 |
| Merchant submits evidence | Merchant via Dashboard | Within 5–7 days |
| Stripe submits to issuer | Stripe | Day 5–7 |
| Issuing bank reviews and decides | Card issuer | 30–75 days from original filing |
The $15 Stripe Dispute Fee
Every Stripe dispute costs $15, charged immediately when the dispute is created — before you respond, before the outcome is determined. This is a flat fee regardless of the disputed amount, and it is non-refundable under all circumstances.
The implications for dispute economics are significant:
- •On a $15 transaction: the fee equals the entire transaction value. You break even if you win.
- •On a $50 transaction: winning the dispute recovers $50 but costs $15, for a net $35 recovery.
- •On a $10 transaction: you are better off accepting the loss than fighting, since the $15 fee exceeds the disputed amount.
- •On a $500 transaction: the $15 fee is 3% of the disputed value — worth responding to every time.
This economics calculation is one reason that many merchants set a threshold — for example, they respond to all disputes above $50 and accept losses on disputes below that amount. The exact threshold depends on your average order value, win rate, and operational cost of preparing a dispute response.
Note that even if Stripe's Radar prevented a fraudulent transaction from being processed in the first place, that prevention does not generate a $15 fee. Fees only apply when a transaction goes through and is later disputed. This is one reason that investing in fraud prevention (via Radar rules or 3DS) is economically superior to fighting disputes after the fact.
Responding in the Stripe Dashboard
Stripe's dispute response interface is more structured than most payment processors. Rather than a blank text field, Stripe presents a form with specific fields for each type of evidence — and it pre-populates some fields automatically from your transaction data.
To respond to a Stripe dispute:
- 1Navigate to Disputes in the Stripe Dashboard (or via Payments → Disputes). Open the specific dispute.
- 2Review the dispute reason code displayed at the top — this is critical for knowing which evidence fields matter most.
- 3Note the response deadline displayed prominently. This is your hard deadline.
- 4Click "Submit evidence." The evidence form opens with Stripe-populated fields (customer details, billing info, prior charge history).
- 5Fill in the relevant evidence fields for your dispute type. Upload supporting files — tracking numbers, screenshots, communications, policy documents.
- 6In the "Additional information" or rebuttal field, write a clear, concise statement addressing the dispute claim directly.
- 7Click "Submit evidence." You cannot resubmit after this — Stripe treats it as a single submission.
What Stripe auto-populates: When you open the evidence form, Stripe pre-fills fields with data from the transaction: customer name, email, billing address, prior charges from the same customer, the charge amount and date, and dispute history for that customer. This pre-populated data is submitted as part of your response whether or not you add anything to those fields.
What you must add: Stripe cannot auto-populate external evidence — tracking numbers with delivery scans, product listing screenshots, customer communication exports, your refund policy, proof of service delivery, or any signed agreements. These must be uploaded manually.
Evidence by Dispute Reason
Stripe's dispute form is contextual — the fields shown depend on the dispute reason code. Knowing what each reason code requires before you open the form means you can gather everything before clicking “Submit evidence,” rather than scrambling mid-form.
Fraudulent / Not recognised charge
This is the most common Stripe dispute reason. Evidence: prior successful transactions from the same card or email address (Stripe often auto-populates this). Billing address verification — AVS match confirmation. IP address of the transaction session matching the billing address city or region. Device fingerprint consistency across sessions. Most importantly: 3D Secure (3DS) authentication records. If the transaction was authenticated with 3DS2 and carries ECI code 05 or 02, you have a strong liability shift argument — the issuing bank authorised the transaction. Include the authentication timestamp and ECI code in your rebuttal.
Product not received
Full tracking history with a delivery confirmation scan. The delivery address shown in the tracking record must match the billing address or the shipping address provided at checkout. For physical goods, a signature confirmation record is stronger than a standard delivery scan. If your product is a service or digital good, provide server-side access logs showing the customer accessed the product after purchase, or delivery confirmation emails with open tracking.
Product not as described
A screenshot or export of your product listing as it appeared at the time of purchase — title, description, condition notes, photos. If your listing was subsequently updated, use an archived version (Wayback Machine or your own CMS version history). Photos of the item you shipped, ideally with timestamps. Customer communications — especially if the customer did not complain about the product until after the return window closed, or if they previously indicated satisfaction. Your return and refund policy, showing the customer had recourse before filing a dispute.
Subscription cancelled / credit not processed
Your terms of service and subscription agreement showing the billing terms, including how recurring charges work and the cancellation policy. Usage logs showing the customer actively used the subscription during the disputed billing period. The cancellation policy clearly showing how to cancel and what the customer's obligations were. If the customer cancelled and you did not stop billing, the dispute is likely valid — issue the refund proactively. If the customer cancelled and you stopped billing correctly, provide the cancellation confirmation timestamp alongside the billing records showing the disputed charge predates the cancellation.
Duplicate charge
Pull both transaction records from Stripe and confirm they are for different orders — different order IDs, different cart contents, different timestamps. If they are genuinely different transactions, submit both records side by side showing the differences. If one is genuinely a duplicate, refund it immediately and indicate in the Stripe dispute response that you have already processed the refund for the duplicate.
Stripe-Specific Tips for Dispute Responses
Stripe has operational quirks that differ from other payment processors. Understanding them prevents avoidable mistakes that cost merchants winnable disputes.
Respond within 5–7 days, not the network's 30 days
The deadline in your Stripe Dashboard is Stripe's internal cutoff — not the card network's formal deadline. Many merchants assume they have 30 days (the typical Visa/MC representment window) and miss the actual deadline by 3 to 4 weeks. Stripe does not forward evidence submitted after its deadline, even if the network window is still technically open. Treat the Dashboard deadline as absolute.
Submit everything in one go — no partial submissions
After you click "Submit evidence" in Stripe, you cannot add to your submission. Stripe sends everything to the issuing bank as a single package. If you click Submit too early and realise you forgot a tracking document, there is no way to add it. Build a checklist before you open the evidence form, gather everything, then submit.
Keep evidence files under 5MB each
Stripe has file size limits for evidence uploads. Keep individual files under 5MB. For tracking histories, export as PDF rather than screenshot. For long email threads, export as PDF or compress the images. If a file is too large, Stripe will reject it at upload time — without warning that your submission is incomplete unless you notice the failed upload.
Use the rebuttal statement to guide the reviewer
The rebuttal text field is often underused. A clear, two-paragraph statement — "This dispute should be found in the merchant's favour because..." followed by a summary of your evidence — helps the issuing bank reviewer understand your case quickly. Reviewers handle high volumes; a well-organised response is more likely to be read carefully than a document dump with no explanation.
Check whether a refund was already issued
If you refunded the transaction before the dispute was filed, Stripe should reflect this in the dispute details. Flag it explicitly in your rebuttal: "A full refund of $X was issued on [date], prior to this dispute being filed. The refund should already be reflected in the cardholder's account." This prevents the customer from recovering both the refund and the chargeback — a scenario called double recovery.
Stripe Radar and Dispute Prevention
Stripe Radar is Stripe's built-in fraud prevention system. It uses machine learning trained on transaction data across millions of Stripe businesses to score every payment request for fraud risk. Radar is available on all Stripe plans; Radar for Fraud Teams (paid add-on) adds custom rules and more detailed review tooling.
How Radar reduces disputes: By blocking fraudulent transactions before they complete, Radar prevents chargebacks that would otherwise arrive 30 to 90 days later. A transaction blocked by Radar generates no revenue — but it also generates no chargeback, no $15 fee, and no hit to your dispute rate.
Custom Radar rules allow merchants to add their own risk logic on top of Stripe's machine learning. Common patterns merchants block or review:
- •Orders over a defined value threshold from new customers with no purchase history.
- •Multiple orders in a short window using different cards from the same IP address.
- •Billing address country not matching card-issuing country.
- •Email addresses using known throwaway domains.
- •Shipping address to a freight forwarder or known high-fraud zip code.
3D Secure 2 (3DS2) is the most powerful dispute prevention tool available to Stripe merchants. When Stripe requests 3DS2 authentication and the cardholder successfully authenticates, liability for any subsequent fraud dispute shifts from you to the issuing bank. The bank authorised the transaction; it cannot then claim the transaction was fraudulent.
Stripe can be configured to request 3DS2 automatically for transactions that Radar scores as elevated risk. You can also set Stripe to always request 3DS2 for any transaction above a certain value. The tradeoff is checkout friction — some customers abandon at the 3DS step. For high-value or high-risk product categories, the tradeoff is typically worth it.
Stripe Dashboard vs ChargeMate for Dispute Responses
Stripe's built-in dispute interface is functional but basic. It provides a form, pre-populates some transaction data, and forwards your submission to the issuing bank. What it does not do is help you win.
| Capability | Stripe Dashboard | ChargeMate |
|---|---|---|
| Submit evidence to issuer | Yes | Yes (via Stripe) |
| Pre-populated transaction data | Yes | Yes (synced from Stripe) |
| Evidence checklist by reason code | No | Yes |
| AI-generated rebuttal letter | No | Yes |
| Deadline tracking and alerts | Limited | Yes |
| Win-rate guidance per reason code | No | Yes |
| Bulk dispute management | Basic | Yes |
The gap that matters most in practice is the rebuttal letter. The Stripe Dashboard provides a free-text field for “additional information.” Most merchants either leave it blank (a significant missed opportunity) or write a generic statement. What actually moves the needle with issuing bank reviewers is a structured rebuttal that directly addresses the specific dispute reason — explaining precisely why each piece of evidence shows the dispute is invalid.
ChargeMate connects to your Stripe account, syncs your disputes, and generates a tailored rebuttal letter for each case based on the Stripe dispute reason code. It also generates an evidence checklist — so instead of wondering what to gather, you have a specific list of documents to collect before you open the Stripe evidence form.
For merchants handling more than five disputes a month, the time savings alone justify the tool. For merchants who handle disputes infrequently, ChargeMate removes the need to remember the process each time a dispute arrives.
Frequently Asked Questions
How do I respond to a dispute on Stripe?▾
Does Stripe refund the $15 dispute fee if I win?▾
How long do I have to respond to a Stripe dispute?▾
What evidence should I submit for a Stripe dispute?▾
Can I use ChargeMate for Stripe disputes?▾
ChargeMate
Win more Stripe disputes — built for Stripe merchants
Connect your Stripe account, sync disputes automatically, and generate tailored rebuttal letters in minutes. ChargeMate turns a 45-minute manual process into a 5-minute one — with better results.
Try ChargeMate free →