How to Dispute a Stripe Chargeback
Updated June 2026
To dispute a Stripe chargeback, open the dispute in your Stripe Dashboard, read the reason code to see what the cardholder is claiming, gather evidence that directly answers that claim, and submit it before the due-by date Stripe shows. Stripe forwards your evidence to the cardholder's issuing bank, which makes the final decision. This guide walks through the process step by step, including deadlines, fees, and what happens to your money along the way.
Who decides a Stripe dispute?
Stripe is not the judge. When a cardholder disputes a charge, the claim originates with their issuing bank, and that bank decides the outcome. Stripe's role is to notify you, collect the evidence you submit, and pass it to the card network on your behalf. Understanding this matters: your evidence is written for a bank reviewer who has never seen your business, not for Stripe.
Key point: No payment processor or service can guarantee that you win a dispute. The issuing bank makes the call. What you control is whether your evidence clearly answers the reason code.
Step 1: Find the dispute in your Stripe Dashboard
In the Stripe Dashboard, go to Payments → Disputes. Open the disputed payment to see the transaction details, the dispute reason, the amount in question, and the response due-by date. You can also retrieve and respond to disputes through the Stripe API if you manage volume programmatically.
Each open dispute shows its current status (for example, needs response, under review, won, or lost) and how much time remains. Start here so you are working from Stripe's own deadline rather than guessing the card network window.
Step 2: Read the reason code and decide whether to challenge
The dispute reason tells you what the cardholder is claiming and therefore what evidence the bank wants. Stripe groups reasons into categories such as fraudulent, product not received, product unacceptable, subscription canceled, duplicate, and credit not processed. Map your evidence to the category before you respond.
| Stripe Dispute Reason | What to Prove | Evidence That Helps |
|---|---|---|
| Fraudulent | The real cardholder made the purchase | AVS/CVV match, 3D Secure result, IP and device data, prior order history |
| Product not received | The item or service was delivered | Tracking with delivery confirmation, signature, or access logs for digital goods |
| Product unacceptable | The product matched its description | Listing screenshots, specifications, and any return request the customer skipped |
| Subscription canceled | The customer consented to recurring billing | Checkout terms, cancellation policy, renewal notices, post-charge usage |
| Duplicate | Each charge is a separate transaction | Distinct order IDs, itemized receipts, separate fulfillment records |
| Credit not processed | A refund was issued or none was owed | Refund receipt, refund policy, terms the customer accepted |
If the dispute is legitimate and you cannot prove the claim wrong, you can accept it in the Dashboard rather than spend the countered-dispute fee on a case you will not win. For a deeper breakdown by network code, see our reason code library.
Step 3: Gather and submit your evidence
Stripe provides structured evidence fields for the dispute (for example, customer name, receipt, shipping documentation, and a free-text explanation). Fill the fields that apply to your reason code and attach supporting files. Quality beats quantity: a focused set of documents that disproves the specific claim outperforms a large dump of unrelated files.
Lead with the strongest proof
Put the single piece of evidence that most directly answers the reason code first: delivery confirmation for "product not received," authentication data for fraud.
Write a short, factual explanation
Use the explanation field to walk the reviewer through what each attachment proves, in plain language and without emotional argument.
Submit, then leave it alone
Once you submit, Stripe forwards the evidence to the issuing bank. You generally cannot edit a submission afterward, so review it carefully before sending.
Step 4: Submit before the deadline
After a dispute is created you have a limited window to respond, typically 7 to 21 days depending on the card network. Stripe shows the exact due-by date on the dispute, and it is set earlier than the raw card network deadline to leave room for processing. Missing it means the chargeback stands and the funds stay debited.
Do not wait until the last day. Aim to submit several days early. If you need more evidence (for example, a carrier confirmation), request it as soon as the dispute opens.
Fees and timeline: what to expect
When a dispute opens, Stripe immediately debits the disputed amount plus a dispute fee from your balance. If you challenge the dispute and win, Stripe returns the disputed funds and, in most regions, the countered-dispute fee; the original dispute fee is generally non-refundable. Fee amounts vary by country and have changed over time, so confirm the current figures on Stripe's pricing page.
After you submit, the issuing bank reviews your evidence, commonly 60 to 75 days depending on the network, so the full dispute lifecycle often runs two to three months. The status in your Dashboard updates to won or lost when the bank decides.
Frequently Asked Questions
How long do I have to respond to a Stripe dispute?↓
Does it cost money to dispute a chargeback on Stripe?↓
What happens to my money during a Stripe dispute?↓
Can I win a Stripe dispute?↓
Build a Stripe-Ready Evidence Pack
ChargebackKit organizes your evidence the way card networks expect to see it. Answer a few questions about your dispute, add your exhibits, and get a submission-ready response you can upload in Stripe.
Build My Evidence Pack — $19