Most merchants lose Stripe disputes because their evidence does not match what the card issuer is actually asked to decide. Winning is less about having a strong case and more about structuring the response around the specific reason code. This guide walks through the evidence that actually moves the needle and the patterns that consistently lose.
Understand What You Are Actually Fighting
A chargeback is a decision made by the cardholder’s issuing bank, not by Stripe. Stripe is a passthrough: it collects your evidence, forwards it to your acquirer, which forwards it to the card network, which delivers it to the issuer. The issuer reads whatever you submitted, compares it to the reason code the cardholder filed under, and picks a side.
The practical implication: your evidence is read by someone who has about 60 seconds, a reason code, and a checklist. They are not reading a story. They are checking whether the documents you sent satisfy the specific criteria for that reason code.
Evidence that wins is evidence that matches the criteria. Everything else is noise.
The Reason Codes That Drive Most Disputes
Nine out of ten disputes fall into a small set of reason codes. Each one has different winning evidence.
Fraudulent — card not present (Visa 10.4, Mastercard 4837). The cardholder claims they did not authorize the transaction. Winning evidence: AVS full match, CVV match, IP geolocation near the billing address, prior successful orders from the same card, device fingerprint match to prior sessions, delivery to the billing address with signature confirmation.
Product not received (Visa 13.1, Mastercard 4855). The cardholder claims the product never arrived. Winning evidence: tracking number with delivery confirmation to the billing address, photo of delivery if the carrier captured one, signed proof of delivery, digital access logs for digital goods, timestamped login history for SaaS.
Product not as described (Visa 13.3, Mastercard 4853). The cardholder claims the product was materially different from the listing. Winning evidence: screenshots of the product description as of the purchase date, the refund policy the customer accepted at checkout, correspondence showing you offered a remedy and they declined, photos or documentation matching the listed specifications.
Subscription cancelled (Visa 13.2, Mastercard 4841). The cardholder claims they cancelled before the charge. Winning evidence: the terms they accepted at sign-up, the cancellation policy and notice period, logs showing no cancellation request before the billing date, prior successful billing on the same subscription.
Duplicate processing (Visa 12.6, Mastercard 4834). The cardholder claims they were billed twice. Winning evidence: transaction logs showing the two charges were for different items or different dates, shipping records for both, or a refund record if you already corrected it.
If you do not know the reason code, open the dispute in the Stripe dashboard — it is the first thing displayed under the dispute header. Do not start drafting evidence until you know it.
The Structure of a Winning Response
The issuer’s reviewer is not reading prose. Structure the response so they can check each criterion in ten seconds.
Open with a one-paragraph summary. State the facts: what was ordered, when, for how much, by whom, and what evidence follows. Ninety words maximum. This is the only narrative part.
Follow with labeled exhibits. Each exhibit is one document with a one-line caption explaining what it proves. Exhibit A: AVS and CVV match from authorization response. Exhibit B: shipping label with tracking number. Exhibit C: delivery confirmation. Label them alphabetically, reference them in the summary, and stop.
Close with the policy the customer accepted. Attach the terms of service and refund policy as a final exhibit. Include the timestamp they agreed and the IP address it came from if you have it.
This structure beats longer, more detailed responses almost every time. The reviewer does not want to read. They want to tick boxes.
Evidence That Loses
Several categories of “evidence” routinely lose and make the response weaker by their inclusion.
- Character testimony. “This customer has been a regular buyer for three years” is not evidence of the specific transaction. If you want to show history, include a list of prior successful orders from the same card.
- Unverified screenshots. A screenshot of a chat message with no timestamp or URL is discounted. Use exported transcripts with metadata, or do not include them.
- Internal notes. Your CRM record of what a support agent thought happened is not evidence. It is hearsay from the issuer’s perspective.
- Long narratives without exhibits. Stories without documents supporting each claim are read as weak cases padded with text.
- Generic policy language. “Our terms of service prohibit this” means nothing unless you show the specific clause and proof the customer accepted it.
The rule: if an exhibit does not directly answer the reason code’s criteria, it weakens the response.
When Not to Respond
Not every dispute is worth fighting. Three situations where accepting the loss is the rational call:
The transaction was genuine fraud. If the card was actually stolen and used without the holder’s knowledge, you will lose. The issuer has liability protection obligations that override your evidence. Accept, refund, and move on.
The dispute amount is smaller than the representment cost. Stripe charges a $15 dispute fee that is not refunded even if you win. Plus the time cost of assembling evidence. For a $30 transaction where you have moderate evidence, the expected value of fighting is often negative.
Your evidence is thin. Submitting weak evidence still loses — but it also flags your account as one that responds with poor documentation. Issuer systems track that over time. If you do not have the reason-code-matched exhibits, accept the loss rather than submit a weak response.
The heuristic: respond when you have strong, matched evidence and the dispute amount justifies the work. Otherwise, absorb it.
The Representment Timeline
Understanding the timeline prevents the most common cause of losses: missed deadlines.
- Dispute opens. The cardholder contacts their issuer. The issuer files the chargeback through the card network to Stripe.
- Stripe debits your balance. The disputed amount and the $15 fee are held immediately.
- Stripe posts the dispute in your dashboard. You are notified by email. The clock starts.
- Stripe’s response deadline. Typically 7 to 21 days. This is earlier than the network deadline so Stripe has buffer to submit.
- Evidence submitted. Stripe forwards to the acquirer, which forwards to the network, which delivers to the issuer.
- Issuer decides. Takes between 30 and 90 days. If you win, funds return to your balance. If you lose, the hold becomes permanent.
Miss the Stripe deadline and the dispute auto-loses. No extensions, no appeals. Set a calendar reminder for 48 hours before the deadline as a hard internal checkpoint.
Winning Rates and What They Really Mean
Published win rates cluster between 20% and 40% for typical merchants. Well-operated businesses with disciplined responses see 55% to 70% on the categories where evidence is clean.
The distribution matters more than the average:
- Product-not-received disputes with tracking and delivery proof: 70% to 85% win rate.
- Fraud disputes with full AVS, CVV, and delivery: 50% to 70%, lower because the issuer’s obligation to the cardholder is strongest here.
- Subscription cancelled disputes with clear terms and no cancellation on record: 60% to 75%.
- Product-not-as-described disputes: 30% to 50%. The subjectivity works against you.
- True fraud with no delivery proof: under 10%. Usually not worth fighting.
Tracking your own win rates by reason code is the single most useful post-dispute exercise. It tells you where your evidence is strong and where your operational gaps are.
Prevention Is Still the Only Compounding Fix
Winning a dispute recovers the money, but the chargeback still counts in the monthly ratio that Stripe and the card networks use to evaluate the account. A 1% dispute ratio with a 70% win rate is still a 1% dispute ratio. The warning thresholds do not care whether you won representment.
The durable fix is reducing the dispute rate itself: clearer billing descriptors so customers recognize charges, faster support response so disputes become tickets, tracked and signed-for delivery so fraud claims are defensible before they are filed, and proactive refunds for the customers most likely to dispute.
FreezeAlert monitors dispute velocity, refund rate, and the risk signals that tend to precede a chargeback spike — with alerts when any of them trend toward the thresholds that matter. If you are building a disciplined response process, pairing it with upstream visibility turns dispute handling from a fire drill into a routine.
Found this useful?
Subscribe to get engineering deep dives every week.