ProofPack
ProofPack/Sample Evidence Pack

Sample Chargeback Evidence Pack

One of the hardest parts of preparing a dispute response is not knowing what the finished product should look like. This page shows a synthetic example of a complete, structured evidence pack — the kind you would submit with a Stripe dispute response for a SaaS or digital product business. All details below are fictional and illustrative only.

What makes an evidence pack strong

A well-structured evidence pack does three things: it orients the reviewer quickly, it demonstrates delivery and fulfillment clearly, and it addresses the specific claim the customer made. The goal is not to overwhelm the reviewer with volume — it is to give them exactly what they need to understand your case.

  • Starts with a clear summary so the reviewer knows the basics immediately
  • Presents a chronological timeline of the key events
  • Provides direct evidence of delivery or fulfillment — not just a receipt
  • Includes the policy that applies to the dispute claim
  • Uses labeled, captioned files — not a pile of numbered screenshots

Example evidence pack structure

Synthetic example

The following is a fictional example. Business name, customer details, and all other specifics are invented for illustration only.

Dispute Evidence Pack
Example · Not a real case
Section 1

Case Summary

BusinessAcme SaaS Co.
Customer nameJordan Example
Customer emailjordan@example.com
Order dateNovember 14, 2024
Disputed amount$49.00 USD
ProductAcme Pro — Annual Plan
Dispute typeSubscription canceled / not recognized
Dispute filedJanuary 8, 2025
Section 2

Product and Service Description

Acme Pro is a subscription SaaS product providing project management tools for small teams. The Annual Plan provides 12 months of full access for a one-time annual fee of $49.00. Access is provisioned immediately upon payment confirmation. Customers agree to the annual billing terms during checkout via a visible checkbox. The subscription renews automatically unless canceled before the renewal date.

Section 3

Proof of Delivery and Access

  • Account provisioned Nov 14, 2024 at 14:03 UTC — access confirmation email sent
  • Customer logged in Nov 14, 15, 17, 21, Dec 3, Dec 11, Dec 22, 2024
  • Customer created 4 projects and 12 tasks between Nov 14 and Dec 22, 2024
  • Last login recorded Dec 22, 2024 — 39 days after purchase
  • No cancellation request received before the dispute date
Section 4

Evidence Timeline

  1. Nov 14, 2024
    Customer purchased Acme Pro Annual Plan$49.00 charged, access provisioned immediately
  2. Nov 14, 2024
    Welcome email sentConfirmation and login link delivered to jordan@example.com
  3. Nov 14–Dec 22, 2024
    Active product usage8 login sessions, 4 projects created, 12 tasks added
  4. Jan 8, 2025
    Dispute filed by cardholderReason: subscription canceled / not recognized
  5. Jan 9, 2025
    No cancellation request on recordNo cancellation found in platform logs for this account
Section 5

Customer Communication

No support tickets or emails received from jordan@example.com prior to the dispute. No cancellation request was submitted through the account portal, email, or any other channel before the dispute was filed. A copy of the full communication log is included as Exhibit C.

Section 6

Applicable Policy

At the time of purchase, the checkout page clearly displayed: “You are subscribing to Acme Pro Annual Plan at $49.00/year. Your subscription renews automatically. Cancel any time before your renewal date.” The customer checked the billing agreement checkbox before completing payment. A screenshot of the checkout page is included as Exhibit A.

Section 7

Supporting Evidence Files

  • Exhibit ACheckout page screenshot — showing billing terms and agreement checkbox
  • Exhibit BAccount login log — timestamps for all sessions Nov 14 – Dec 22, 2024
  • Exhibit CCommunication log export — confirming no support contact or cancellation request
  • Exhibit DStripe payment record — charge ID, date, amount, card last four

What this example shows

The case summary is first

The reviewer immediately knows who the customer is, what was purchased, when, for how much, and why there is a dispute — without digging through the document.

Delivery is documented directly

Login records and usage activity show the customer actively used the product for 39 days after purchase. This directly contradicts a claim of non-recognition or cancellation.

The timeline is scannable

Events are listed in date order with a brief description. A reviewer can follow the sequence in 30 seconds.

Exhibits are labeled, not numbered arbitrarily

Each file has a label and a one-line description of what it shows and why it is relevant. Unlabeled files create confusion and reduce the impact of good evidence.

Policy documentation is included

The checkout terms and billing agreement are referenced and attached. This is especially important for subscription and cancellation disputes.

Why structured presentation matters

Dispute reviewers handle large volumes of cases. A submission that starts with a clear summary, uses consistent section headers, and labels every file allows a reviewer to evaluate your case quickly and accurately. Disorganized submissions — even when the underlying evidence is strong — are harder to assess and more likely to be resolved unfavorably.

This is especially true for SaaS and digital product businesses, where evidence tends to be scattered across platforms: Stripe for billing, your app for usage logs, email for communication, and a separate tool for support tickets. Getting all of that into one readable document is the core challenge — and the core purpose of ProofPack.

Build a real pack with ProofPack

ProofPack generates this structure automatically from your case details. Fill in the sections, upload your exhibits, and download a complete, structured PDF in minutes.

Build your evidence pack$4.99 one-time · No account · No data stored

Related guides