Respond to dispute evidence requests

Respond to dispute evidence requests in Stripe — with the four heights of help laid out: do it now, make it easier for the next person to accept, work out the right move when you are stuck, and learn the pattern so it stops coming back.

4prompt heights
Open it in the interactive atlas →

The four heights

The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.

Execute — do the immediate task

+
Customer support has asked for evidence to respond to a dispute for $85 from June 9. Compile the…
Customer support has asked for evidence to respond to a dispute for $85 from June 9. Compile the invoice, the logged support chat showing the customer’s acknowledgment, the refund policy linked at purchase, and the shipment proof. Write the evidence submission narrative that ties those documents to the charge and queue it for upload today, then notify support and finance.

Improve — make it easier to accept

+
Before we respond to the platform’s evidence request, make the submission reviewer-friendly:…
Before we respond to the platform’s evidence request, make the submission reviewer-friendly: surface the charged amount and date at the top, call out the line in the chat where the customer accepts the charge, and mark the exact clause in our refund policy. Point out any contradictions in the customer’s account and suggest a one-line summary to close the case faster.

Decide — diagnose the stuck moment

+
The payments platform requested more evidence for a dispute opened last week; they want proof of…

Platform requested additional evidence this morning.

The payments platform requested more evidence for a dispute opened last week; they want proof of customer consent. I have a chat log with ambiguous wording and an email that doesn’t explicitly say 'I agree.' The support lead, Marcos, says the customer did consent verbally. I’m afraid hearsay won’t help. What is the likely decision and what is the single best piece of evidence I should try to obtain now?

Become — change the pattern

+
We keep getting follow-up evidence requests because our intake doesn't capture explicit cardholder…

Evidence requests often come back for consent proof.

We keep getting follow-up evidence requests because our intake doesn't capture explicit cardholder consent or clear delivery proof. This forces ad hoc evidence hunting and delays. Which two changes to the checkout flow and the support templates will most reliably produce the consent and proof reviewers demand?

Next to this one

Other payments work people do in Stripe.

Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.

The rest of the map

Same library, five ways in.