← All playbooks
Start here

Where to Find Your Dispute Details in Stripe

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

1. Open the Dispute

In the Stripe Dashboard, open Disputes and select the dispute. The page shows the reason, the amount, and the date you must answer by. Stripe gives you 7 to 21 days in most cases, depending on the card network.

Have the email Stripe sent about the dispute? Paste it into the workbench and it fills in the dispute type, card, reason code, amount, and IDs. Check each one against the dispute page.

Note the card brand on the payment method. For a Visa fraud dispute, Stripe checks your history for Visa Compelling Evidence 3.0 and tells you on the dispute page and by email when it qualifies. Stripe then fills in those fields for you; leave them as they are.

2. Customer Details from the Payment

Open the disputed payment from the dispute page and copy the customer's email. When your checkout sends the IP address to Stripe, the payment's risk insights show it for up to 6 months.

The account or user ID, logins, and usage come from your own app. Export them with UTC timestamps.

3. Older Payments for Visa CE 3.0

Open the customer and look at their payments. Pick two successful payments on the same card from 120 to 365 days before the disputed payment, with no refund and no dispute.

For each one, copy the date, the charge ID (it starts with ch_ or py_), and the IP address. Stripe keeps IP details for 6 months, so take the IP of older payments from your own logs.

4. Terms, Logs, and Your Reply

Copy the refund or renewal wording as the customer saw it at checkout, with the date they accepted it. Write your reply in plain facts: dates, matching details, and what the customer received.

Questions

Can I change my response after I submit it in Stripe?

No. Stripe sends your response to the bank once, and you cannot edit it or add files afterwards. Run the check and fix what it flags before you submit.

What if I cannot find the network reason code?

Leave it empty. The check still runs and reminds you to confirm the code is 10.4 before you rely on CE 3.0.

Enter your details in the workbench.

The form follows the same order as this guide.

Open workbench
More playbooks