The Wednesday everything broke
I run a skincare and beauty shop in Surulere, Lagos. We sell through Instagram, take orders on WhatsApp, and process payments through Paystack—cards, bank transfers, USSD, whatever the customer prefers. Most months we handle sixty to eighty orders, all under ₦50,000, mostly repeat customers who know the drill. Payment comes through, I confirm on WhatsApp, pack the order, hand it to a dispatch rider, done.
Then the first week of December hit. I'd taken on a bulk corporate order for Christmas hampers, posted a flash sale on Instagram Stories, and suddenly I had forty orders in three days on top of the usual flow. Payments flooded in. So did the problems. A customer in Ikeja said she'd been charged twice. Another in Abuja claimed her ₦18,500 payment failed but Paystack still debited her account. Someone filed a chargeback through their bank for an order that had already been delivered and signed for. And a guy in Port Harcourt demanded a refund because the rider took four days to reach him—Lagos traffic plus fuel scarcity, nothing I could control, but he wanted his money back.
I had twelve dispute emails from Paystack sitting in my inbox, each one asking for evidence, timelines, proof of delivery, screenshots. I'd reply to one, two more would arrive. I was copying and pasting bits of old emails, rewriting the same explanation four different ways, and still getting follow-up questions from Paystack support because I'd left out a transaction reference or forgotten to attach the waybill.
I opened Kryotta, dumped one of the emails into Claude Sonnet 4.5, and asked it to draft a reply. It came back clear, polite, and included every detail Paystack had asked for. I sent it. They accepted the response within two hours. So I built four templates—one for each type of dispute I kept seeing—and ran the next hundred and thirty-eight emails through them.
The four disputes that kept showing up
Most Paystack disputes fell into four buckets: duplicate charges, failed transactions where the customer still got debited, chargebacks filed by the bank, and delivery complaints that turned into refund demands. Each needed a different tone and a different set of facts.
Duplicate charges usually happened when a customer's network dropped mid-payment and they retried without realising the first attempt had gone through. Paystack would email me with both transaction references and ask which one was valid. The reply needed to be fast, factual, and include proof that I'd only fulfilled one order.
Failed transactions were messier. The customer's account got debited, Paystack's dashboard showed the payment as failed, and now someone's ₦12,000 is stuck in limbo. These emails needed empathy, a clear timeline of what happened on my end, and confirmation that I hadn't shipped anything.
Chargebacks came through the customer's bank, often weeks after delivery. The customer would claim they never received the order or never authorised the payment, and I'd have twenty-four hours to submit evidence. These needed everything: waybill, delivery photo, chat screenshots, transaction reference, the works.
Delivery disputes weren't Paystack's fault, but customers would file them as payment disputes anyway. The order arrived late, or damaged, or the rider asked for extra cash, and now they want a refund. I couldn't just say "not my problem"—I needed to show what I'd done to fix it and whether a refund was fair.
Template one: duplicate charge (Claude Sonnet 4.5)
I used Claude for these because the reply had to be precise and boring. No emotion, no apology beyond the standard line, just the facts. Claude's good at that—it doesn't try to be clever.
The template:
Subject: Re: Duplicate Charge Dispute – Transaction [Reference Number]
Hi [Paystack Agent Name],
Thank you for flagging this. I can confirm that two payments were processed for the same order:
- Transaction 1: ₦[Amount], [Date and Time], Reference [Number], Status: Successful
- Transaction 2: ₦[Amount], [Date and Time], Reference [Number], Status: Successful
Only one order was fulfilled. I have shipped [Item Description] to [Customer Name] on [Date], tracking number [Waybill]. The second payment of ₦[Amount] should be refunded to the customer.
Attached: Waybill and order confirmation WhatsApp chat.
Please let me know if you need anything else.
[Your Name]
[Shop Name]
I'd fill in the blanks, attach the waybill PDF, and send. Claude handled the tone perfectly—no fuss, no drama. Paystack approved fourteen out of fifteen of these within a day. The one rejection was my fault; I'd attached the wrong waybill.
Template two: failed transaction (Gemini Flash)
Failed transactions needed more empathy. The customer's angry, their money's gone, and they think I've scammed them. I switched to Gemini Flash because it writes warmer without tipping into grovelling, and it's faster when I'm pasting in chat screenshots.
The template:
Subject: Re: Failed Transaction Dispute – [Transaction Reference]
Hi [Paystack Agent Name],
I've reviewed this case. The payment of ₦[Amount] from [Customer Name] on [Date] shows as failed in my Paystack dashboard. I did not receive the funds, and I have not shipped any order to this customer.
I spoke with [Customer Name] on WhatsApp on [Date] and confirmed that their account was debited. I advised them to contact their bank for a reversal, as the payment did not reach my Paystack balance. I have not issued a refund because I never received the payment in the first place.
Attached: Screenshot of Paystack dashboard showing failed status, and WhatsApp chat with the customer.
I understand this is frustrating for [Customer Name]. Please let me know how Paystack can assist in reversing the debit from their bank.
[Your Name]
[Shop Name]
Gemini's phrasing—"I understand this is frustrating"—came across as human without sounding like I was taking blame. I used this template thirty-two times. Paystack escalated most of them to the customer's bank, and I didn't hear back, which I took as a win.
Template three: chargeback with delivery proof (Claude Sonnet 4.5 again)
Chargebacks scared me the most. If I lost, Paystack would claw back the payment plus a ₦2,500 dispute fee. These emails needed every scrap of evidence, formatted clearly, with no room for Paystack to ask follow-up questions.
I went back to Claude because it's methodical. I'd paste in the chargeback notice, the waybill, the delivery photo, and the customer's original order message, and tell Claude to structure a reply that addressed every point Paystack had listed.
The template:
Subject: Chargeback Response – [Transaction Reference]
Hi [Paystack Agent Name],
I am responding to the chargeback filed by [Customer Name] for ₦[Amount], transaction reference [Number], dated [Date].
Evidence of valid transaction:
- Customer placed order via WhatsApp on [Date] at [Time]. Screenshot attached.
- Customer confirmed delivery address: [Full Address].
- Payment of ₦[Amount] was received on [Date] via [Payment Method].
Evidence of delivery:
- Order dispatched on [Date] via [Logistics Company].
- Waybill number: [Number]. Waybill attached.
- Delivered on [Date] at [Time]. Delivery photo attached showing package and signature.
Customer communication:
- Customer confirmed receipt on WhatsApp on [Date]. Screenshot attached.
- No complaint was raised until the chargeback was filed on [Date], [X] days after delivery.
I fulfilled this order in full. The chargeback appears to be fraudulent. I request that Paystack reject it and retain the payment.
Attachments: [List each file]
[Your Name]
[Shop Name]
Claude formatted the evidence in a way that looked like a legal document, which I think helped. I used this twenty-three times. Paystack ruled in my favour on nineteen. The four I lost were cases where the delivery photo was blurry or the customer claimed someone else signed for the package—I couldn't prove otherwise.
Template four: delivery complaint refund (Mistral Large)
Delivery disputes were the hardest to write because I was often partly at fault. The rider was late, or the packaging got crushed, or the customer paid extra cash to the rider because he claimed I hadn't covered fuel. I needed to acknowledge the problem, explain what I'd done to fix it, and either offer a partial refund or explain why I couldn't.
I tried Claude first, but the replies came out too stiff. Gemini was too apologetic—it made me sound like I was admitting liability for things I couldn't control. Mistral Large got the balance right: sorry for the inconvenience, here's what happened, here's what's fair.
The template:
Subject: Re: Delivery Complaint – Order [Number]
Hi [Paystack Agent Name],
I've looked into the complaint from [Customer Name] regarding their order of ₦[Amount], delivered on [Date].
What happened:
[Two-sentence summary: e.g., "The rider was delayed by two days due to fuel scarcity in Abuja. I stayed in contact with the customer via WhatsApp and updated them twice a day."]
What I've done:
[One or two actions: e.g., "I've spoken with the logistics company and confirmed they will not charge this customer extra fuel fees in future. I've also offered the customer a ₦2,000 discount on their next order."]
Refund decision:
[State clearly: e.g., "I am offering a partial refund of ₦3,000, which reflects the delay but accounts for the fact that the order was delivered in full and the customer has kept the items." OR "I am not issuing a refund because the delay was beyond my control, the customer was kept informed, and the order was fulfilled as agreed."]
Attached: WhatsApp chat log showing updates to the customer, and waybill showing delivery date.
Let me know if you need further information.
[Your Name]
[Shop Name]
Mistral's tone felt the most honest. I used this forty-nine times. Thirty-one ended with Paystack accepting my partial refund offer. Eighteen went to full refunds because I couldn't prove I'd kept the customer updated, or the delay was long enough that I just wanted the dispute closed.
What I'd do differently now
I'd start logging disputes the day they arrive instead of letting them pile up. I didn't realise how many duplicate charges I was getting until I looked back at the templates—if I'd caught the pattern earlier, I could have added a payment confirmation step on WhatsApp that would have stopped customers retrying.
I'd also take better delivery photos. Half the chargebacks I lost came down to a blurry picture or no picture at all. Now I tell every rider: photo of the package, photo of the recipient, or I don't pay the dispatch fee.
And I'd use Kryotta's compare feature more. I only tested Mistral Large for delivery disputes after I'd already sent thirty replies with Claude. Running the same prompt through two models side by side would have saved me a week of trial and error.
Questions people ask
Can I use these templates for Flutterwave disputes too?
Yes. Flutterwave's dispute process is nearly identical to Paystack's—they ask for the same evidence and timelines. You'll just need to swap "Paystack" for "Flutterwave" in the subject line and adjust the transaction reference format.
Which model is fastest for disputes that need a reply in an hour?
Gemini Flash. It's quick, and the replies are good enough that you won't need to rewrite much. Claude's better if you have time to review, but Flash gets you to "send" faster.
Do I need to rewrite the AI reply every time, or can I send it as-is?
I rewrote about 20 per cent of them—usually just to add a sentence the AI missed or to soften a phrase that sounded too formal. The rest I sent unchanged. If the facts are right and the attachments are there, Paystack doesn't care whether a human or an AI wrote it.
What if Paystack rejects my reply and asks for more evidence?
Paste their follow-up email into Kryotta, attach the original dispute and your first reply, and ask the model to draft a response that addresses the new questions. I had to do this six times. Claude handled it well—it picked up what was missing and added it without repeating the stuff Paystack already had.
If you're sitting on a backlog of Paystack disputes and the thought of writing another "Dear Support" email makes you want to close the shop, try one template. Fill in the blanks, attach the proof, send it. You'll clear the inbox faster than you think, and you'll stop losing money to chargebacks you could have won. I built all four templates in Kryotta—it's free to start, and you can test Claude, Gemini and Mistral side by side before you pick one.
