Card-network playbooks.

The card-network rules behind Stripe disputes, and how to write a reply that holds up.

Start here

Where to Find Your Dispute Details in Stripe

The workbench fields come from two places: your Stripe Dashboard and your own app.

4 sections · 2 FAQs Read playbook →
Visa 10.4 · CE 3.0

Visa Compelling Evidence 3.0 on Stripe: 120 to 365 Day Rules

On a Visa fraud dispute (reason code 10.4), CE 3.0 moves the loss to the cardholder's bank when the same customer paid you at least twice before, 120 to 365 days earlier, with matching details such as the IP address or email.

4 sections · 3 FAQs Read playbook →
Visa 10.4 · MC 4837

Stripe Fraud Disputes (Visa 10.4) Without CE 3.0: What Proof to Send

The customer says they didn't make the payment. Without the earlier payments Visa CE 3.0 needs, you answer by showing that the real cardholder paid and used what they bought.

3 sections · 3 FAQs Read playbook →
Visa 13.2 · MC 4841

Stripe subscription_canceled (13.2) Checklist for SaaS

Recurring SaaS disputes turn on two facts: affirmative auto-renewal consent at signup and whether the user canceled before billing.

2 sections · 2 FAQs Read playbook →
Visa 13.1 · MC 4855

Order Never Arrived? Stripe product_not_received (13.1) Checklist

The customer says the order never came. You answer by showing it did: the carrier's delivery record for shipped goods, or the customer's logins and downloads for a digital product.

4 sections · 3 FAQs Read playbook →
Rebuttal QA

Phrases That Lose Stripe Chargeback Rebuttals

You can lose a winnable dispute when your reply includes phrasing that bank analysts read as an admission of fault.

2 sections · 2 FAQs Read playbook →