You find out from Stripe, not from them. A dispute notification lands, you read the name, and something in your chest tightens before your brain catches up. Then you do the thing every merchant does: you open your inbox and search. Nothing. You check the chat logs, the contact form, the DMs. Nothing. This person paid you, received what they paid for or at least never said otherwise, and then walked past your front door to tell their bank you had wronged them. No email. No question. No chance to make it right.

It feels like being ghosted by someone you thought you were on good terms with. And the instinct it produces is a bad one: to treat the silence as an insult, to want to prove that they are lying. Hold that instinct for a minute. The silence is not an insult. In a consumer dispute, it is often the strongest piece of evidence you have, and most merchants never put it in the file.

Why people call the bank instead of you

Start with what the silence actually means, because the honest answer is more useful than the angry one.

In 1970 the economist Albert Hirschman published Exit, Voice, and Loyalty, a short book about the two things a person can do when an organization lets them down. They can speak up and try to fix it, which he called voice, or they can leave, which he called exit. Decades of complaint-behavior research since has confirmed the uncomfortable half of his thesis: most dissatisfied customers never complain to the business at all. They simply go. Voice is socially expensive. It means writing to a stranger, saying “I’m not happy,” and waiting to be judged. It risks being told no. For many people, that small confrontation is more aversive than the money is worth.

A chargeback is what exit looks like when the bank hands you a form. The customer never has to talk to you. They open their banking app, tap the transaction, tap “report a problem,” and choose from a menu of reasons that are phrased as findings rather than requests. “Merchandise not as described.” “Services not provided.” There is no box for “I changed my mind and did not want to have the conversation.” The interface converts an awkward ask into a tidy report, and the bank becomes the person who says the hard thing on their behalf.

That is the mechanism. Not malice, usually. Conflict avoidance plus a path of less resistance. It also means that at the moment they filed, the customer was almost certainly asked a question by their bank: did you try to resolve this with the merchant? And the answer they gave is sitting in your dispute file.

The precondition most reviewers quietly check

Card-network rules for the consumer-dispute family (the codes about quality, description, delivery and cancellation, not the fraud codes) generally expect the cardholder to have made a good-faith attempt to resolve the problem with the merchant before the bank steps in. Visa’s rules say this explicitly for several of its dispute conditions, including not-as-described and defective merchandise. The issuing bank is supposed to confirm it. In practice, the bank asks the cardholder, the cardholder checks a box, and nobody verifies it.

Nobody except you. The bank’s evidence that contact happened is a checkbox. Your evidence that it did not is every record you keep. A reviewer looking at a dispute where the customer claims they tried to reach you, and the merchant shows with specificity that no such attempt exists, is looking at a credibility gap. The customer’s entire narrative rests on it. If the first checkable claim turns out to be hollow, the rest gets read with a colder eye.

This is why the silence matters. Not because it proves the customer is dishonest, but because it shows the dispute skipped the step it was supposed to begin with, and it hands the reviewer a reason to doubt the story before they reach the parts you cannot disprove.

Turning nothing into something a reviewer can see

Absence is hard to attach. You cannot upload an email that was never sent. So the work is to make the absence concrete, and to surround it with proof that contact would have been easy and would have worked.

First, do the search properly and document it. Check every channel a customer could plausibly have used: your support inbox, your personal inbox if customers sometimes find it, the contact form, live chat, social DMs, phone and voicemail logs, and any marketplace messaging. Search by the cardholder’s name, the email on the Stripe charge, the order number, and the billing name if it differs. Then screenshot the empty results with the search term and date visible. One clean image of a support search returning zero results is worth more than a paragraph swearing to it.

Second, prove that reaching you was easy. Attach the receipt and the order confirmation with your support email or phone number highlighted. Stripe receipts pull the support contact from your business settings, so make sure it is actually filled in. Add a screenshot of your website footer or help page. The point is to close the escape hatch of “I couldn’t find how to contact them.”

Third, show what would have happened if they had. Attach your refund or resolution policy and state, plainly, how it would have applied to this order. If a refund was available on request, say so. A reviewer will wonder why a customer with a reasonable path to a refund chose a dispute instead, and you want them wondering that.

Fourth, reach out now, after the dispute, and put that in the file. A short, warm email on the day the dispute lands: you saw it, you are sorry there was a problem, here is what you can do, here is how to reply. Most customers will not answer. That is fine. The sent email shows the reviewer that the merchant tried to resolve this even after being bypassed, and the lack of a reply extends the pattern. One caution that trips people up: do not refund in that email hoping it ends things. A refund does not cancel an open dispute, and you can end up out the money twice.

Then write the paragraph. Keep it factual and unheated. Something like: “Our records contain no contact from the cardholder prior to this dispute. We searched our support system, contact form, chat and social channels by name, email and order number (Exhibit A). Our support email appears on the receipt (Exhibit B) and the order confirmation (Exhibit C). Our refund policy (Exhibit D) would have permitted a full refund on request within 30 days of purchase. We contacted the cardholder on the day the dispute was received (Exhibit E) and have had no reply.” Five sentences, five attachments, no adjectives. Let the gap speak.

What not to do with the silence

Do not call the customer a liar. Reviewers at issuing banks read hundreds of these, and an indignant merchant is indistinguishable, on paper, from a guilty one. Do not speculate about motives. Do not pad the file with every email you have ever received from anyone, hoping volume reads as proof. And do not lean on this argument for fraud reason codes. If the cardholder says the charge was unauthorized, no contact precondition applies, because the claim is that they never bought anything in the first place. For those, your evidence is about identity and authorization, not about conversations.

Your next moves

  • Run the silence search today, before deadline pressure makes you sloppy. List every channel a customer could use to reach you, search each one for the cardholder’s name, email and order number, and screenshot each empty result with the date visible.
  • Open your own receipt and confirmation email as if you were the customer and check whether a support email or phone number appears. If it does not, add it in your Stripe business settings and your confirmation template this afternoon.
  • Write a three-sentence outreach email you can send the moment a dispute arrives: you saw it, you are sorry, here is how to fix it. Save it as a template so you never have to compose it while upset.
  • Add a standing contact-history paragraph to your rebuttal template with blanks for the exhibits, so the argument becomes a fill-in rather than a fresh draft every time.
  • Tag every support conversation with the order ID from now on. The search that proves silence only works if the records that would have shown contact are easy to find.

Where Argeback fits

The hardest part of this argument is not writing it. It is doing the search, gathering five exhibits, and filing them inside Stripe’s seven-day window while the rest of your business keeps happening. Argeback was built for exactly that stretch: it ingests your Stripe disputes as they arrive, drafts an evidence-backed response around the records you attach, and files it before the deadline, from your phone. If a customer went to their bank instead of coming to you, the least you can do is make sure your side of the story shows up on time. Try it at https://argeback.lumenlabs.works.