The complete guide to Stripe dispute evidence
Stripe accepts specific, named evidence fields for disputes, not a general make your case submission. Knowing which fields exist, and which ones actually matter for your specific reason code, is most of what separates a strong response from a weak one.
What counts as evidence
Evidence is anything you submit through Stripe's Dashboard or API to counter a dispute claim. It falls into five broad categories: proof of delivery, proof of communication, proof of authorization, proof of refund or cancellation, and proof of product or service description.
Proof of delivery
- Shipping documentation: carrier, tracking number, ship date
- Shipping address, matched against the billing address
- Signature confirmation, where available
- Access activity logs, for digital goods, showing login or download after purchase
- Service documentation, confirming when access or service was provided
Matters most for: product not received.
Proof of communication
- Customer communication: any message exchange relevant to the dispute
- Customer email address and name, tied to the account or order
Matters most for: nearly every reason code, since it can support or contradict almost any claim.
Proof of refund or cancellation
- Refund policy and refund policy disclosure
- Refund refusal explanation, where a refund wasn't owed
- Cancellation policy and cancellation policy disclosure
- Cancellation rebuttal, directly addressing a specific cancellation claim
- Duplicate charge ID, explanation, and documentation, where two charges are being conflated
Matters most for: credit not processed, subscription canceled, duplicate.
Proof of product or service description
- Product description, as shown at time of purchase
- Service date, confirming when a service was scheduled or delivered
Matters most for: product unacceptable.
What makes evidence strong
Three traits, consistently: specific rather than vague, timestamped rather than undated, and verifiable by someone other than you rather than self reported. A tracking number alone is weak. A tracking number showing delivery to the exact billing address, before the date a customer claims non receipt, is strong.
How Recovra handles evidence
Recovra pulls the specific fields that matter for each reason code, checks whether they actually exist for a given case, and only builds a submission when the evidence genuinely supports it.
Request your free dispute auditFrequently asked questions
Do I need to submit every evidence field Stripe offers?
No. Only the fields relevant to your specific reason code and case. Submitting irrelevant fields doesn't strengthen a case.
What's the single most important evidence trait?
Specificity. Vague or generic evidence, even a lot of it, is weaker than one precise, verifiable fact.
Can I add evidence after I've already submitted?
Updating any evidence field resubmits the entire evidence hash for review, so treat your submission as complete when you send it.
Not sure what evidence you actually have for a current dispute?
Request your free dispute audit