A chargeback announces itself. Money leaves your balance, a fee lands next to it, and Stripe's dashboard turns a shade of urgent. You may not enjoy the next twenty minutes, but you will certainly spend them paying attention.
An inquiry arrives differently. No funds move. No fee posts. The status reads warning_needs_response — a phrase engineered, apparently, to sound like a shrug. The notification email could be mistaken for paperwork. And so most merchants do one of two things with it: they miss it entirely, or they file it under later.
Both are mistakes, and the same mistake. The inquiry is the only stage of a dispute where you can still make the whole thing not happen. It is the most valuable notice in the entire chargeback lifecycle, dressed as the least important one.
What a dispute inquiry actually is
When a cardholder questions a charge, their bank doesn't have to fire a chargeback immediately. It has a softer instrument available: it can ask you what happened first.
That's an inquiry — formally, a request for information. American Express and Discover use it heavily, because they occupy an unusual position: each is both the card network and, usually, the issuing bank. When their cardholder calls about a charge, they can open a direct line to the merchant before committing to a formal dispute. In Stripe, these arrive as disputes with statuses like warning_needs_response, then warning_under_review, and — if things go well — warning_closed.
The critical difference from a chargeback is what hasn't happened yet. In a chargeback, the cardholder typically receives a provisional credit, the funds are pulled from your Stripe balance, and the dispute fee posts. In an inquiry, none of that has occurred. The bank is holding the file open and asking a genuine question: our cardholder doesn't recognize this, or isn't satisfied — tell us your side.
If the word "inquiry" sounds unfamiliar, you may know its ancestor: the retrieval request, the old mechanism by which a bank asked for a copy of the sales receipt before disputing. Visa and Mastercard have largely retired that step — their disputes now tend to arrive as chargebacks straight away — but the inquiry survives and thrives on American Express and Discover. If you sell to an audience that carries those cards, you will meet it.
The stage where the dispute can still not exist
Here is the structural asymmetry worth internalizing.
Once a chargeback is filed, it exists. It counts toward your dispute rate — the number card networks watch when deciding whether you're a merchant worth keeping. The fee is charged. Even in the best case, where you submit evidence and win, you spend weeks waiting to recover money that was already taken, and the dispute still happened as far as the network's ledger is concerned.
An inquiry that ends at the inquiry stage is different in kind, not just degree. If the bank closes it satisfied, there is no chargeback. No provisional credit to claw back, no formal representment, no mark accumulating against your processing history in the way a chargeback would.
And you have two ways to close it. The first is to answer the question — send evidence that the charge was legitimate and the customer got what they paid for. The second is to refund. This is worth pausing on, because it inverts a rule many merchants have learned painfully: refunding a customer after a chargeback is filed does not cancel the chargeback. The dispute proceeds anyway, and you risk paying twice. During an inquiry, the opposite is true — issuing a full refund typically resolves the inquiry and prevents it from ever becoming a chargeback. The refund that is useless on Tuesday, after escalation, is a clean exit on Monday.
At the chargeback stage, you fight to win money back. At the inquiry stage, you can still prevent the fight.
Why merchants ignore their most valuable notice
If inquiries are this useful, why do so many expire unanswered? The answer is less about negligence than about how human attention allocates itself — and two well-documented findings explain most of it.
The first is loss aversion, the centerpiece of Kahneman and Tversky's prospect theory: losses loom larger in our decision-making than equivalent gains. A chargeback presents as a loss — a specific dollar amount, visibly subtracted from your balance — and losses mobilize us. An inquiry presents as a question. Nothing has been taken. There is no sting to react to. So the notice that offers the most leverage produces the least urgency, because urgency, for humans, tracks what has already been lost rather than what could still be saved.
The second is alarm fatigue, a phenomenon studied most seriously in hospitals, where clinicians exposed to constant low-stakes alerts become progressively slower to respond to all of them. A busy founder's inbox is a milder version of the same environment. Stripe notifications, failed webhook alerts, review requests, receipts — an inquiry email, with its soft language and its warning_ prefix, sinks into that stream without a ripple. It gets triaged by tone. And its tone lies about its stakes.
Knowing this doesn't make you immune, but it does suggest the fix: don't let inquiries be triaged by how they feel. Route them — by filter, by webhook, by whatever mechanism you trust — into the same lane as the alerts you'd never ignore.
How to answer the question well
An inquiry response is not a legal brief. A person at the issuing bank is asking a fairly plain question — does the cardholder's confusion or complaint hold up? — and your job is to make the legitimate sale easy to see.
Send the shape of the transaction: what was purchased, when, for how much, with the receipt. If the inquiry smells like an unrecognized charge — and many do — explain your billing descriptor, and show how it connects to your product; a customer who didn't recognize LUMEN*4829 on a statement often recognizes a screenshot of what they bought. Include proof the customer received value: tracking for physical goods, login and usage records for digital ones. Attach any correspondence with the customer, especially anything showing satisfaction or continued use. If the dispute is cancellation-shaped, include the policy as it appeared at checkout.
Then arrange it chronologically and write it short. The reviewer is trying to close a file. A response that reads like the story of an ordinary, legitimate sale gives them exactly the reason they need.
When refunding is the honest answer
Sometimes you open the inquiry and find a sale you couldn't defend: the order genuinely failed, the evidence doesn't exist, or the charge looks like fraud you missed. The inquiry stage is the cheapest exit you will ever be offered. Refund now and the matter typically ends — no chargeback, no fee, no addition to your dispute count. It's the same fight-or-fold calculus every merchant runs on a chargeback, except the fold costs less here than it ever will again.
The deadline is real even when the tone isn't
Every inquiry in Stripe carries a respond-by date, and it is not decorative. An inquiry that expires unanswered doesn't quietly disappear — it typically escalates into a formal chargeback, at which point the funds are pulled, the fee posts, and the question you declined to answer becomes a verdict you now have to appeal. The window is short. Treat an inquiry as this-week work, not someday work, and the softest notice in your inbox stays soft.
This is, in the end, a problem of attention more than of argument — the dispute that's easiest to resolve is the one engineered to look least like a dispute. Argeback exists for exactly that gap: it ingests your Stripe disputes the moment they appear, inquiries included, drafts an evidence-backed response from your order and customer data, and files it before the deadline — from your phone, in the same week the bank asked its question. If you'd rather never learn what an expired inquiry turns into, you can see how it works at argeback.lumenlabs.works.