Stripe opened a limited pilot that drafts chargeback evidence packs for eligible high-volume sellers, with humans still submitting the final packet.
Stripe’s dispute pilot writes a first draft of the evidence pack. That saves clipboard time for sellers who fight the same paperwork weekly. It does not invent a tracking number you never scanned. Card networks still punish fiction.
What the pilot claims to do
Eligible high-volume sellers get a drafted package assembled from order and delivery facts Stripe can already see. Staff review, edit, and submit. Stripe is not pitching an autopilot that wins chargebacks while you sleep. Anyone selling that fantasy is not reading the same note.
Access is limited. If you are not in the cohort, you still gather evidence the old way. Do not delay a response deadline waiting for an invite that may not arrive.
Seller discipline
Read every line before submit. Fix tones that overclaim. Add the PDF the model could not see. Keep a personal checklist: ship proof, usage logs, refund policy excerpt, customer communication.
AI speed is not a license to guess. Stripe automated the assembly line’s first pass. Integrity of the packet remains your name on the form.
Metrics to watch in the pilot
Track time-to-submit, win rate versus your historical baseline, and how often humans heavily rewrite the draft. If win rate flatlines while time drops, the pilot still may be worth it. If rewrite rates stay near one hundred percent, the draft is theater. Share those numbers with Stripe if you are in the cohort—the product improves when pilots complain specifically.
Evidence library
Even inside the pilot, keep reusable snippets: refund policy excerpt, shipping SLA, screenshot template for tracking pages. The model drafts faster when your library is tidy. When the pilot ends—or if you never get in—you still have the library. Treat Stripe’s AI as a layer on top of operational maturity, not a replacement for it.