Guides · Stripe dispute response

Stripe chargeback response checklist

When a dispute lands in your Stripe Dashboard, you typically have a limited time to submit a response. This checklist walks through what to verify before you upload evidence and send your narrative. Not legal advice. Outcomes depend on card network review — not guaranteed.

Response workflow at a glance

Confirm dispute reason
Build timeline
Gather evidence
Match evidence to claim
Keep response concise
Avoid emotional language
Submit before deadline
Review terms and policy links
Track outcome and improve process

New to disputes? Start with what evidence you need and how to organize it.

Organize dispute evidence with a repeatable toolkit

The Stripe chargeback evidence kit includes checklists, folder structures, and alert templates you control in Zapier or Make. Educational toolkit only — outcomes are not guaranteed.

Not legal advice. Templates support documentation only. Dispute outcomes depend on your case and Stripe or card network review.

Get the template kit

View pricing · Secure checkout on Gumroad

1. Confirm dispute reason

Open the dispute in Stripe and note the reason code and any network-specific fields Stripe displays. Your response should address that reason — not a generic "we delivered the product" paragraph if the claim is "subscription canceled" or "credit not processed."

Check: reason code copied; due date in calendar; dispute amount matches your records.

2. Build timeline

Write a one-page timeline: purchase date → delivery or access → support contact (if any) → dispute opened. Attach detailed files separately; the timeline orients reviewers quickly.

3. Gather evidence

Collect the categories that apply to your case — communication, delivery logs, receipts, policies, and so on. Use our evidence types guide as a reference and organization guide for folder structure.

4. Match evidence to claim

For each point in the dispute reason, attach at least one supporting file or screenshot. Label uploads clearly (e.g. 03-support-thread-refund-request.pdf) so reviewers do not hunt for relevance.

5. Keep response concise

Lead with facts: who bought what, when they received access, and what policies they agreed to. Avoid repeating the same attachment in multiple fields unless Stripe asks for it in each slot. For structure ideas see our response examples guide — adapt to your case; not guaranteed templates.

6. Avoid emotional language

Stick to neutral, factual statements. Accusations, sarcasm, or long rants do not help network review and can distract from strong documentation.

7. Submit before deadline

Stripe shows a response due date. Submit early enough to fix upload errors or missing fields. Late responses are often not accepted — treat the due date as hard unless Stripe states otherwise.

8. Review terms and policy links

Include refund policy, terms of service, or checkout disclosures from around the purchase date — not a page edited after the dispute. See our terms and privacy pages for how we publish site policies.

9. Track outcome and improve process

After submission, record dispute ID, date submitted, and outcome when Stripe updates status. If disputes recur, refine your folder template and evidence checklist for the next case.

Full response checklist

Dispute reason and due date confirmed
One-page timeline written
Evidence gathered and organized
Each claim point mapped to a file or screenshot
Response text is concise and factual
No emotional or accusatory language
Terms/refund policy from purchase date attached
Submitted before Stripe deadline
Outcome logged for future disputes

What this guide does not do

Does not guarantee dispute outcomes or chargeback wins
Does not replace Stripe's reason-code-specific fields or card network rules
Does not provide legal advice — consult qualified counsel for complex cases

Want templates for your own Stripe accounts?