Stripe dispute "evidence due by" deadline: how to submit evidence via API
Submits dispute evidence through the Stripe API before the evidence-due deadline. Use when a chargeback arrives and you need to fight it with structured evidence. Not for preventing disputes or handling lost ones.
TL;DR
Every dispute carries an evidencedueby timestamp; submit before it via the dispute update endpoint with the evidence fields (and file uploads for documents). Prioritize compelling evidence: proof of delivery, customer communication, and matching billing descriptors. Late or missing evidence means an automatic loss, so calendar the deadline the moment the dispute lands.
Steps
- On charge.dispute.created, read evidencedueby and put it on your ops calendar with a 48-hour buffer.
Expected: The deadline is tracked from minute one.
- Gather evidence: order details, delivery proof, customer emails, terms accepted, and the billing descriptor the customer saw.
Expected: Your evidence file is complete before you write anything.
- Upload supporting documents as files, then update the dispute with evidence fields referencing them.
Expected: The submission is structured and complete.
- Submit well before the deadline and confirm the dispute status shows evidence submitted.
Expected: No last-minute failures.
- Record the outcome when it resolves and tag the dispute reason for prevention analysis.
Expected: Win or lose, the data improves prevention.
When to use
- A chargeback arrives and you want to contest it
- You automate dispute responses
- Evidence deadlines keep getting missed
When not to use
- The dispute is fraudulent-pattern and unwinnable (consider accepting to save the fee)
- You want to prevent disputes (see Radar and descriptors)
- The dispute already closed as lost (different playbook)
Compatibility
Stripe Disputes API; file uploads for evidence. evidencedueby on dispute objects. Dashboard dispute flow mirrors the API.
Variant phrasings
### Stripe submit dispute evidence API
### chargeback evidence due by deadline
### dispute evidence fields Stripe
Root cause
Card networks give issuers a fixed evidence window, and Stripe passes it through as evidencedueby; silence at the deadline is scored as no defense. Structured evidence wins because reviewers decide in minutes, and organized proof (delivery plus communication) beats narrative every time.
Edge cases
- File uploads must finish before you reference them in the evidence update
- Some dispute categories weight specific evidence (shipping proof for not-received claims)
- Submitting evidence does not pause the funds withdrawal; the money stays held during review
Provenance
Resolved from the public thread: https://vectle.com/posts/pst_bVncLXmiAm8e2grqvXsQKg
Maintainer review
No maintainer verification is recorded for this version.
This records the version a maintainer checked. It does not assert that the version is the latest upstream release.