Guides · Response template
Stripe chargeback response template
A chargeback response template gives you a consistent structure for the rebuttal you submit through the Stripe Dashboard when a customer disputes a charge. This guide explains what a response is, the sections a strong template should include, and what to write in each one — so you are not drafting from a blank page under a deadline. Educational only — not legal advice. A template organizes your case; it does not guarantee the outcome, which depends on the issuing bank and card network review.
What a chargeback response is
When a cardholder disputes a payment, their bank (the issuer) opens a chargeback. Stripe surfaces it in your Dashboard with a reason code and a response deadline, then debits the disputed amount plus a dispute fee while the case is reviewed. Your response — sometimes called a rebuttal or evidence submission — is the package of text and files you send back to argue the charge was legitimate.
Stripe forwards your evidence to the card network and issuer; Stripe does not decide the outcome. Because a human reviewer at the issuer may skim your submission, a clear, well-labeled template that maps directly to the dispute reason tends to read better than a long, unstructured wall of text.
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 kitView pricing · Secure checkout on Gumroad
The structure of a strong response template
A reusable template should contain the following sections. Fill in only the ones relevant to your dispute reason — a "product not received" case leans on delivery proof, while a "fraudulent" case leans on AVS/CVV and prior order history.
- Summary paragraph. Three to five neutral sentences: what was purchased, when, by which customer, how it was delivered or accessed, and why the charge is valid. Reference the dispute reason directly. Let the attachments carry the detail.
- Evidence list. A short index of every file you are attaching, each labeled with what it proves (e.g.
02-download-log.pdf — file accessed 3 days after purchase). This helps a reviewer connect documents to claims quickly. - Product or service description. Exactly what the customer bought, the price, and a snapshot of the product page or offer as it appeared at purchase — not a version edited afterward.
- Delivery / access proof. For digital goods: download timestamps, login events, license activation, course progress, or API usage tied to the customer's account or email. For services: fulfillment records and dates.
- Customer communications. Support threads, onboarding emails, or in-app messages showing the buyer received the product, got help, or acknowledged the purchase. Redact unrelated third-party data.
- Refund / cancellation policy. The refund, cancellation, and terms the customer agreed to at checkout, ideally dated to the purchase. This matters most for subscription and "credit not processed" disputes.
- AVS/CVV & authorization data. If the payment cleared address verification (AVS) and card verification (CVV) checks and shows a normal authorization, note it — this is especially relevant to "fraudulent" disputes. Stripe records these fields on the charge.
What to put in each section
Keep the writing factual and specific. Use the customer's name and email, the Stripe charge or payment intent ID, exact dates, and the product name as it appeared on their receipt. Where Stripe provides structured evidence fields (product description, customer communication, service documentation, uncategorized file), place each document in the field that matches it rather than dumping everything into one box. A one-page timeline — purchase → delivery/access → any support contact → dispute date — orients the reviewer before they open a single attachment.
Common mistakes to avoid
- Ignoring the reason code — answering "we delivered it" when the claim is "subscription canceled"
- Submitting a policy page edited after the purchase without noting the original version
- Emotional or accusatory language instead of dated, verifiable facts
- Unreadable screenshots, oversized bundles, or files with no labels
- Missing the Stripe deadline — check the exact due date in your Dashboard and submit early
- Claiming a guaranteed win — stick to what your records actually show
Response template readiness checklist
- Summary paragraph draft that names the reason code and the customer
- Evidence index with one line per attachment
- Product/service description matching the receipt
- Delivery or access proof exported for the disputed charge
- Relevant customer communications, redacted where needed
- Refund/cancellation policy from the purchase date
- AVS/CVV and authorization details noted where relevant
- One-page timeline and a final proofread before submission
Want templates for your own Stripe accounts?
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 kitView pricing · Secure checkout on Gumroad
New to disputes? Start with the free Stripe Dispute Evidence Starter Checklist — no signup required.
What this guide does not do
- Does not promise a favorable chargeback outcome
- Does not provide legal advice — consult qualified counsel for complex cases
- Does not replace Stripe or card network rules and evidence fields