The message tends to arrive at night, with the caps lock already warm. Refund me right now or I'm disputing this with my bank. Sometimes it's a support ticket, sometimes an email, sometimes a one-star review with a threat stapled to the end. Your stomach drops, and two instincts fire at once: refund immediately and make it disappear, or dig in your heels, because you did nothing wrong.
Both instincts are premature. A customer threatening a chargeback has accidentally handed you something most merchants never get: advance notice. The typical dispute arrives as a done deal — money already pulled from your account, evidence deadline already ticking. A threat means the dispute doesn't exist yet. And in that narrow window, you have options that evaporate the moment the customer actually calls the bank.
A threat is not a dispute — and the gap between them is worth real money
It helps to be precise about what changes at the moment of filing, because everything about your decision hangs on it.
Once a cardholder disputes a charge, three things happen no matter how the case ends. Stripe debits the disputed amount from your balance while the bank investigates. You're charged a dispute fee on top of it. And the dispute is added to your chargeback count — the ratio of disputes to transactions that card networks use to decide whether you're a merchant in good standing. That count doesn't care whether you eventually win. A dispute you fight brilliantly and overturn sits on your record exactly as heavily as one you lose.
Before the filing, none of that machinery exists. A refund issued while the charge is still just a charge costs you the sale and nothing else. A refund issued a day after the dispute is filed cancels nothing — the case proceeds anyway, and now the money is in limbo twice while the process untangles itself. That asymmetry is what makes the threat window valuable: it is the last moment when a refund is cheap.
Which doesn't mean the answer is always to refund. It means the answer deserves ten minutes of actual thought instead of a reflex.
Why people threaten instead of just filing
Here's the counterintuitive part: the threat itself is usually good news.
In Exit, Voice, and Loyalty, the economist Albert Hirschman described the two moves available to anyone unhappy with an organization: leave quietly, or complain in the hope that something changes. A silent chargeback is pure exit — the customer has decided you are not worth talking to and has recruited their bank to end the relationship for them. A threat is voice. It's an aggressive, unpleasant form of voice, but voice all the same. The customer is still, in their way, talking to you. People who have fully decided to go around you don't usually announce it first.
Decades of research on procedural justice points in the same direction. Tom Tyler's work on why people accept decisions they don't like keeps finding that satisfaction depends heavily on whether the process felt fair — whether they were heard, treated with respect, and given reasons — sometimes as much as on the outcome itself. A customer who feels processed rather than heard escalates. A customer who feels genuinely listened to will often accept a resolution they initially called unacceptable, including resolutions short of a full refund: a partial credit, a fixed bug, an honest explanation of what they actually bought.
So the goal of your reply is not to win the argument. It's to make your process feel fair enough that the bank stops being the more attractive audience.
Write the reply as though a bank analyst will read it — because one might
Everything you send in this window has two possible readers: the angry customer today, and a dispute reviewer months from now if the customer files anyway. Write for both at once and the tone almost takes care of itself.
Reply quickly — the threat is an open loop in the customer's head, and every silent hour makes the bank's phone number look better. Restate their complaint in your own words before you answer it; being accurately summarized is the cheapest form of being heard. Then lay out the facts without heat: what was purchased, when, what your policy says, what you can offer. Make the offer concrete and time-boxed — "I can refund the unused month today" lands differently than "we'll look into it."
Two things to leave out. Don't threaten back — telling a customer that disputes are fraud or that you'll send them to collections reads terribly to the second audience, and it converts a negotiation into a grudge. And don't admit fault you don't believe just to soothe them; a sentence like "you're right, we shouldn't have charged you" can be quoted back at you inside a dispute you're trying to win.
Do the math before you decide to fight
Sometimes the right move is a refund even when you're right, and it's worth being unsentimental about when.
Refund when the amount is small relative to the dispute fee plus the hours a fight will consume, when the complaint is at least plausible, or when your chargeback ratio is already creeping toward the networks' monitoring thresholds — because the count is the one cost you can't win back later. A $19 charge is rarely worth defending on principle if losing the principle costs you $15 in fees and a tick on a ratio that decides whether you keep processing cards at all.
Hold firm when the demand exceeds what the customer actually paid, when the same customer has run this play before, or when the amount is significant and your evidence is strong — delivery logs, usage records, a policy they demonstrably agreed to. Capitulating to a demand that smells like extortion doesn't buy peace; it teaches the customer, and sometimes their forum of choice, that the threat works on you.
Either way, decide deliberately. The worst outcome is the drifted one: you ignore the message, the customer files, and you've paid the full price of a dispute to defend a charge you might have happily refunded.
If they file anyway, the thread becomes your evidence
Some customers will dispute no matter how gracefully you respond. When that happens, the exchange you just handled carefully turns into the spine of your defense.
A correspondence trail undermines the most common dispute claims almost automatically. A cardholder who emailed you about the charge cannot easily claim they didn't recognize it or never dealt with you. A dated message offering a refund or a fix shows the reviewer a merchant who attempted resolution — which is exactly the question many dispute forms ask outright. So preserve everything from the moment the threat lands: timestamps, the exact offer you made, the policy links you sent, and the delivery or usage logs that back your version of events. You are no longer just doing customer service; you are assembling an exhibit.
The window is short, and it never reopens
The threats you see coming are the manageable part. The harder problem is the disputes that arrive with no warning at all — filed silently, discovered late, due in seven days whether or not you're at your desk. That's the part Argeback was built for: it ingests your Stripe disputes the moment they appear, drafts an evidence-backed response — including the correspondence trail you saved — and files it before the deadline, all from your phone. If you'd rather spend the threat window talking a customer down than formatting evidence for the ones you couldn't, you can start at argeback.lumenlabs.works.