Stripe dispute evidence — what to assemble before chargeback

Disputes are won on evidence, not opinion. The evidence is much easier to assemble before a dispute arrives than after.

Definition. Stripe dispute evidence is the documentation a merchant submits to demonstrate that a transaction was authorized, the product or service was delivered as described, and the customer’s claim does not align with the records. Stripe’s dispute evidence best practices lists what tends to be effective.

What card networks accept as evidence

Card networks evaluate a fixed set of evidence categories. The strongest representment packets cover most or all of them:

• Order confirmation. Email or in-account receipt showing the customer’s email, the product purchased, the price, and the date.
• Customer consent. A record showing the customer accepted your terms before payment — checkbox state, IP address, timestamp.
• Delivery proof. Tracking number, carrier scans, signature where applicable. For digital goods: download logs, license activations, login records.
• Usage logs. For subscriptions and SaaS: the customer’s login dates, feature usage, and session duration after purchase.
• Customer communication. Support tickets, chat logs, emails — the full thread from first contact through the dispute.
• Refund history. Prior refunds or partial refunds related to this customer or transaction.
• Cancellation logs. For subscriptions: when did the customer last log in, did they cancel before or after the disputed charge?
• Terms acceptance. A copy of the terms in effect at the time of purchase, plus the user’s acceptance record.

Not every dispute requires all of these. Subscription disputes lean heavily on usage logs and cancellation records. Physical goods disputes lean on tracking and delivery. Digital downloads lean on access logs.

The evidence gaps we see most often

Order confirmation is unstructured

Many merchants have the data but the email is a marketing template that buries the order detail under banner imagery and CTAs. The card network reviewer needs to see customer name, email, product, price, and date in a clean block, not in a footer.

Customer consent is implicit

A “By signing up you agree to terms” sentence below a button is a consent claim. Without a stored record of which version of the terms was in effect, which IP submitted, and at what timestamp, the consent claim is harder to defend.

Delivery proof is incomplete for digital products

For digital goods, “the user downloaded it” is evidence; “the user has not contacted us about not receiving it” is not. The strongest digital delivery evidence includes the timestamp of the download, the IP, and ideally a second touch — a login or a license activation.

Usage logs are missing for SaaS subscriptions

A customer disputing a $29 monthly charge after using your product for 90 days has a weaker friendly-fraud claim than they realize. But you have to produce the usage data — sessions, logins, features touched, dates.

Customer communication is buried in helpdesk silos

Three months of support thread that demonstrates the customer asked for and received help is excellent evidence. But only if you can export it as a chronological PDF. If your evidence is “we have it in Intercom somewhere,” it is not yet evidence.

A pre-dispute readiness checklist

Before the first chargeback arrives, confirm you can produce — within five minutes — for any past transaction:

1. The order confirmation as a structured record (not a marketing email)
2. The consent record (terms version, IP, timestamp)
3. Delivery proof appropriate to the product type
4. Usage records (for subscriptions) or download records (for digital)
5. Every customer communication
6. Any prior refund or partial refund
7. The terms of service in effect at the time
8. The cancellation flow record (for subscriptions)

If any one of these takes more than five minutes, that gap is a real exposure.

Representment, in two paragraphs

When a dispute arrives, you have two choices: accept it, or represent. Representment is the formal process of submitting evidence to the card network to challenge the dispute. Stripe routes the evidence through its dashboard. The issuer reviews and decides.

The decision time is typically 60 to 75 days. Even if the customer claims to have withdrawn the dispute, you must submit evidence — silence is treated as accepting the claim. Submitting strong evidence also signals to the issuer that you contest the dispute on the merits, which matters for borderline cases.

What this guide does not cover

This guide is about evidence assembly. It does not advise on whether to fight a specific dispute (that depends on your win-rate history and the cost of the chargeback fee) and does not address chargeback prevention via Stripe Radar rules, which is a separate workflow. For a self-audit specifically tied to a current dispute spike, see our dispute evidence checklist.