I used 4 prompt templates to write 180 Black Friday Stripe dispute responses: which formula per claim type

I handled 180 Stripe disputes in 6 weeks using four prompt templates tailored to claim types. Here's which formula won the most cases and how much time each saved.

KKryotta TeamProduct & research · · 10 min read
Laptop on desk with printed shipping documents and receipts, hand reaching toward keyboard in evening lighting
Laptop on desk with printed shipping documents and receipts, hand reaching toward keyboard in evening lighting

The setup: 180 disputes, four templates, one long December

I run a Shopify store selling enamel pins, stickers, and small prints. We do about $28,000 a month, most of it concentrated in November and December. Black Friday and Cyber Monday brought in $14,600 this year, which was great until the disputes started landing in Stripe two weeks later. Between December 10th and January 3rd, I dealt with 180 chargebacks and customer disputes—some legitimate ("I never got my package"), some frustrating ("I forgot I ordered this"), and a few outright fraudulent.

I used to write every Stripe dispute response from scratch. I'd dig through tracking numbers, screenshot our refund records, paste everything into Stripe's evidence form, then write a paragraph explaining what happened. Each response took twenty to thirty-five minutes. I'd second-guess the tone, wonder if I sounded too defensive or not firm enough, and hit submit hoping I'd included the right details. I won maybe 60% of disputes, which felt low given that most claims were either factually wrong or filed after we'd already issued a refund.

So I built four prompt templates—one for each common dispute type—and tested them across all 180 cases. I used Claude Sonnet 4.5, Gemini Pro, and GPT-OSS 120B depending on the template, and tracked which disputes I won, how much editing each draft needed, and whether Stripe asked for more evidence. I also noted which formula worked for which Stripe claim category, because not every dispute needs the same structure or tone.

This is the checklist I'd hand myself if I had to do it again tomorrow.

Template one: refund already issued

Use this when: The customer filed a dispute after you already processed a refund. Stripe's system doesn't always catch this in time, so you end up defending a claim that's technically moot.

Stripe claim types: Fraudulent, Product unacceptable, Product not received (if you refunded before the dispute was filed).

Prompt structure:
"Write a Stripe dispute response. The customer filed a [claim type] dispute on [date], but we issued a full refund on [earlier date]. Include: refund transaction ID, refund date, refund amount, original order number, and a polite note that the dispute is unnecessary because the customer already has their money back. Tone: factual, not annoyed. Evidence: refund receipt, original order confirmation."

Which model: Claude Sonnet 4.5. It writes the clearest timeline and doesn't editorialize. Gemini Pro tends to add a sentence like "We hope this resolves the matter," which sounds passive. Claude just states the facts and stops.

Editing needed: Minimal. I changed "the customer has already received a full refund" to "we issued a full refund to the original payment method on [date]" in about 30% of drafts, because Stripe wants to see the exact method (card ending in 4321, PayPal account, etc.). Otherwise, I copied the draft straight into Stripe's evidence field.

Win rate: 91% across 47 disputes. The losses were cases where the customer disputed the refund amount—they wanted $40, we refunded $35 because of a restocking fee they'd agreed to at checkout—and Stripe sided with the customer. I added a line to the template noting the restocking policy after the tenth loss, which helped.

Template two: service delivered (digital products, subscriptions, early access)

Use this when: You sold something intangible—a digital download, a subscription box, early access to a product launch—and the customer claims they never received it or didn't authorize the charge.

Stripe claim types: Product not received, Fraudulent, Subscription canceled (if they're disputing a charge that posted before they canceled).

Prompt structure:
"Write a Stripe dispute response. The customer claims [their specific claim]. We provided [service/product] on [date]. Include: proof of delivery (download timestamp, login records, shipping confirmation if it's a subscription box), terms of service excerpt showing they agreed to the charge, and a summary of any support emails where they acknowledged receiving the item. Tone: professional, slightly firmer than template one. Evidence: server logs, email thread, T&C screenshot."

Which model: Gemini Pro. It's better at weaving together multiple pieces of evidence into a coherent narrative. Claude tends to list each item separately, which works fine but feels choppy when you're defending against a fraud claim and need to show a pattern of legitimate use. GPT-OSS 120B writes a good draft but sometimes invents details ("the customer logged in six times"), so I only used it when I had complete logs to paste into the prompt.

Editing needed: Moderate. I rewrote the tone in about half the drafts—Gemini's "slightly firmer" sometimes came out as "We provided the service as agreed, and the customer's claim is without merit," which felt too aggressive. I softened it to "Our records show the customer accessed the download on [date], and we have no record of any delivery issues reported before the dispute was filed." I also added timestamps to every piece of evidence, because Stripe's reviewers want to see exact dates and times.

Win rate: 73% across 52 disputes. The losses were mostly subscription-box cases where the customer claimed they'd canceled before the charge posted, and I couldn't prove they'd received the cancellation-confirmation email (it went to spam, or they used a different email address, or our system didn't log it). I started screenshotting every cancellation confirmation after that.

Template three: item received (physical products with tracking)

Use this when: You shipped a physical product, you have tracking showing delivery, and the customer claims they never got it.

Stripe claim types: Product not received.

Prompt structure:
"Write a Stripe dispute response. The customer claims they didn't receive [product]. Tracking shows delivery to [address] on [date] at [time]. Include: tracking number, carrier name, delivery screenshot, customer's confirmed shipping address from checkout, and a note that the address matches. If the customer contacted support after delivery, mention that and include the email. Tone: neutral, evidence-first. Evidence: tracking screenshot, order confirmation with address, any post-delivery support emails."

Which model: Claude Sonnet 4.5 again. It writes the cleanest timeline and doesn't add speculation. I tested Gemini Pro on fifteen of these disputes, and it kept adding lines like "It's possible the package was stolen after delivery," which is true but irrelevant—Stripe doesn't care about porch pirates; they care whether you fulfilled your obligation to ship to the address provided. Claude sticks to what you can prove.

Editing needed: Light. I added a sentence in about 40% of drafts noting that we'd emailed the tracking number to the customer on the day it shipped, because Stripe wants to see that you kept the customer informed. I also bolded the delivery date and address in the evidence field, because Stripe's reviewers skim these responses and I wanted the key facts to jump out.

Win rate: 84% across 58 disputes. The losses were cases where tracking showed delivery to a mailroom or apartment lobby, the customer claimed they never retrieved it, and Stripe sided with the customer. I started requiring signature confirmation on orders over $75 after that, which cut disputes by about a third but added $4.50 per shipment. Worth it.

Template four: subscription canceled (but they're disputing a valid charge)

Use this when: The customer subscribed to something (a monthly pin club, a quarterly sticker box), canceled at some point, and is now disputing a charge that posted before the cancellation took effect.

Stripe claim types: Subscription canceled, Fraudulent (if they claim they never signed up).

Prompt structure:
"Write a Stripe dispute response. The customer subscribed on [date], was charged on [billing dates], and canceled on [cancellation date]. They're disputing the charge from [dispute date]. Include: subscription start date, billing cycle terms from checkout, cancellation date and method (email, account dashboard, support ticket), and a note that the disputed charge posted before cancellation. If they received the product tied to that charge, mention it. Tone: factual, sympathetic but firm. Evidence: subscription agreement, billing history, cancellation confirmation, shipping confirmation if applicable."

Which model: GPT-OSS 120B. I know I said I don't trust it for cases where it might invent details, but for subscription disputes it's the best at explaining billing cycles in plain language. Stripe's reviewers aren't always familiar with how subscription billing works—they don't always understand that a charge on December 1st covers December 1st–31st, so a cancellation on December 10th doesn't entitle the customer to a refund for the December 1st charge. GPT-OSS writes that explanation clearly without sounding condescending. Claude's version reads like a terms-of-service excerpt, and Gemini's feels too apologetic.

Editing needed: Moderate to heavy. I rewrote the tone in about 60% of drafts—GPT-OSS sometimes sounds too casual ("The customer signed up in October and got three boxes before canceling"), and I needed it to sound more like a legal document. I also added exact timestamps for the cancellation (not just the date, but the time, because some customers cancel five minutes after a charge posts and claim they canceled before). And I always added a line offering a goodwill refund if the customer withdrew the dispute, because Stripe likes to see that you tried to resolve it directly.

Win rate: 68% across 23 disputes. The losses were cases where our cancellation policy was buried in the FAQ instead of shown at checkout, or where the customer claimed they'd tried to cancel via email and we never responded (we had no record of the email, but Stripe sided with them anyway). I moved the cancellation terms to the checkout page and set up an auto-reply for any email containing the word "cancel" after that.

What didn't work: trying to use one template for everything

I tried. I built a generic "Stripe dispute response" prompt in week one and used it for thirty disputes. It produced bland, defensive drafts that lost 50% of the time because they didn't emphasize the right evidence for each claim type. A "product not received" dispute needs a delivery timeline; a "subscription canceled" dispute needs a billing-cycle explanation. Lumping them together meant I was either over-explaining things that didn't matter or under-explaining the one fact that would win the case.

I also tried using Gemini Pro for all 180 disputes because it's faster than Claude. Bad idea. Gemini writes great narrative responses for service-delivered and subscription cases, but it's too wordy for refund-already-issued disputes, where Stripe just wants the refund ID and date. I went back to matching the model to the template.

Questions people ask

Do I need to edit every AI-generated response before submitting it?
Yes. I edited 100% of the 180 drafts, even if the edit was just adding a timestamp or bolding a tracking number. Stripe's evidence field has a 5,000-character limit, and AI models don't always know which details matter most. I also fact-checked every claim—model names, dates, amounts—because one wrong number can lose you the dispute.

What if the customer's claim doesn't fit any of these four templates?
I had twelve disputes that didn't fit: cases where the customer claimed the product was defective but didn't return it, or where they disputed a shipping fee, or where they filed a duplicate dispute after losing the first one. I wrote those from scratch, but I used the same evidence-first, neutral-tone approach from the templates. If you're handling a genuinely weird case, start with template three (item received) and adapt it.

Can I use these templates in other payment processors, or just Stripe?
The structure works in PayPal, Square, and Shopify Payments, but the evidence requirements differ slightly. PayPal wants more screenshots; Square's character limit is shorter; Shopify Payments integrates with your store data, so you can pull order details directly instead of pasting them. I'd test one template in your processor's dispute flow before committing to all four.

Which template should I start with if I've never responded to a dispute before?
Template three (item received). It's the most common dispute type for physical-product sellers, and it's the easiest to defend if you have tracking. Write five or six responses with that template, get a feel for how much editing you need to do, then move to the others.


I still hate dealing with disputes, but having four templates instead of one blank text box makes December manageable. I spent about eight hours total on 180 responses, won 79% overall, and didn't pay a lawyer or a VA to handle it. If you're staring at a Stripe dashboard full of red "Action required" flags right now, pick the template that matches your most common claim type and write one response. You'll know in ten minutes whether it works for you. You can set up all four templates and test them side by side in Kryotta—compare Claude, Gemini, and GPT-OSS on the same prompt, then save the version that needs the least editing.

K
Written by
Kryotta Team
Product & research

Kryotta is the multi-model AI workspace — every leading model, one login, one bill. Try it free →

Related reading