Guides · Folder setup

How to create a chargeback evidence folder for Stripe disputes

Before a dispute lands in your Stripe Dashboard, you need a calm place for files — not a scramble through email and screenshots. This guide walks through a practical evidence folder structure for digital product and SaaS sellers: what subfolders to create, what belongs in each, and how to maintain them weekly. Not legal advice. A good folder helps you respond consistently; it does not guarantee favorable outcomes or prevention.

Evidence folder setup at a glance

Why an evidence folder helps
Folder structure overview
Customer communication folder
Delivery and access proof folder
Order/payment records folder
Refund/support history folder
Policy and terms folder
Timeline summary folder
Submission-ready folder
Naming conventions
Weekly maintenance workflow

New to dispute evidence? Start with our organization guide, evidence types guide, and response checklist.

1. Why an evidence folder helps

Stripe disputes arrive with deadlines. If transaction receipts live in billing, support threads in a help desk, and delivery logs in engineering tools, assembling a packet takes longer than it should. One folder per dispute (or one master template you copy) reduces hunt time and missed files — see our chargeback evidence organization guide for the baseline mindset.

Folders improve clarity and handoffs; they do not replace card network review or guarantee outcomes.

Organize dispute evidence with a repeatable toolkit

Folder structure templates and checklists from the evidence kit help you duplicate a case folder quickly in Drive or Notion. Educational toolkit only.

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

2. Folder structure overview

Use a top-level folder per dispute (or a standing template folder you duplicate when Stripe opens a case). A simple structure that works for many digital sellers:

01-order-payment — receipts, invoices, Stripe metadata
02-delivery-access — logs, downloads, license activation
03-customer-comms — support threads, refund offers
04-refund-support-history — prior tickets, cancellation notes
05-policies-terms — checkout copy, refund policy snapshots
06-timeline — one-page chronology for your team
07-submission-ready — PDFs and cover note draft for Stripe

Align folder names with your spreadsheet tracking columns so ops and support use the same vocabulary.

3. Customer communication folder

Store exports of relevant email or ticket threads — not every message the buyer ever sent. Include timestamps, subject lines, and any refund or cancellation offers your team made before the dispute. Redact unrelated customer data where your policy requires it.

Strong communication files support many reason codes; they still do not guarantee the issuer agrees with your narrative. Pair this folder with habits from our prevention guide.

4. Delivery and access proof folder

For digital products, collect access logs, download timestamps, course progress, or API usage tied to the customer account. Screenshots should include date/time context — not cropped UI without metadata. Use our delivery documentation guide as a checklist for what to export at dispute open.

Automating exports into this folder at purchase or dispute-open time saves hours; automation does not improve issuer decisions on its own.

5. Order/payment records folder

Include Stripe receipt PDFs or exports, Checkout session details, customer email from payment, amount, currency, and charge ID. If your product logs IP or user agent where permitted, add those here — not in a unrelated marketing spreadsheet.

This folder answers “did this person pay, for what, and when?” — a basic question issuers expect you to document clearly.

6. Refund/support history folder

Separate from live comms: prior support cases, partial refunds, account warnings, or cancellation attempts. Product-not-received and subscription disputes often hinge on whether the buyer tried support first — document what you know without overstating certainty.

If your SaaS team uses macros or tags, note them here for context — see SaaS readiness for team habits.

7. Policy and terms folder

Store snapshots of terms, refund policy, and checkout disclosure the customer saw at purchase time — not a generic page edited after the dispute. PDF or archived HTML with date stamps work well. Map files to evidence categories when you draft your response.

8. Timeline summary folder

One short document or spreadsheet tab: purchase date → delivery/access → support contacts → dispute opened → evidence deadline → submission date. A timeline helps your team and any reviewer follow the story; it is not a substitute for primary source files in other folders.

After a case closes, add a learning note — use our lost dispute review guide for what to record.

9. Submission-ready folder

When files are final, copy or move PDFs and images here with clear filenames. Draft a cover note that references Stripe dispute ID and maps each attachment to an evidence category — follow our response checklist before upload. Keep a local copy of what you submitted; Stripe's portal is the system of record, but your folder is your backup.

10. Naming conventions

Consistent names reduce errors when multiple disputes are open. Examples:

Top folder: 2026-06-dispute-ch_abc123 (date + charge/dispute id fragment)
Files: 2026-06-01_receipt.pdf, 2026-06-02_access-log.csv
Prefix with category number if helpful: 03-support-thread-export.pdf

Pick one scheme and document it in your internal wiki — change only with team agreement.

11. Weekly maintenance workflow

Spend 10–15 minutes weekly (even when no dispute is open):

Verify your master template folder still matches current checkout and policy URLs — or start from our Stripe evidence template guide
Confirm delivery log exports still run (or fix broken scripts)
Review open spreadsheet rows from the tracking guide
Archive closed dispute folders per retention policy
Note one improvement for next case in your learning column

Maintenance reduces scramble; it does not guarantee fewer chargebacks or future wins.

Evidence-folder checklist

Master template folder created (or duplicate-from template documented)
Subfolders for order, delivery, comms, support history, policies, timeline, submission-ready
Naming convention written down for the team
Delivery export path tested into 02-delivery-access
Policy snapshots dated at purchase time stored in 05-policies-terms
Timeline template ready in 06-timeline
Response checklist linked before any Stripe upload
Spreadsheet row opened when dispute opens
Weekly maintenance slot on calendar

Example folder tree

Simplified example — adapt to your stack. Names and IDs are illustrative only.

2026-06-dispute-ch_abc123/
├── 01-order-payment/
│   ├── 2026-05-28_stripe-receipt.pdf
│   └── 2026-05-28_checkout-metadata.txt
├── 02-delivery-access/
│   ├── 2026-05-28_access-log.csv
│   └── 2026-05-29_download-confirmation.png
├── 03-customer-comms/
│   └── 2026-05-30_support-thread-export.pdf
├── 04-refund-support-history/
│   └── prior-ticket-8842-summary.pdf
├── 05-policies-terms/
│   ├── refund-policy-at-purchase.pdf
│   └── terms-checkout-snapshot.html
├── 06-timeline/
│   └── dispute-timeline-one-pager.md
└── 07-submission-ready/
    ├── cover-note-draft.md
    └── submission-packet-v1.pdf

What this guide does not do

Does not guarantee favorable dispute outcomes
Does not guarantee prevention of future chargebacks
Does not replace Stripe, card network, or platform policies
Does not provide legal advice — consult qualified counsel for complex cases

Want folder templates and checklists ready to use?

The Stripe chargeback evidence kit includes folder structures, checklists, and alert templates for your own accounts. Educational toolkit only — outcomes are not guaranteed.