The dispute that argues about meaning, not money
Most chargebacks are arguments about facts. Did the customer get the package? Did the card belong to them? Was there a refund? You can usually settle those with a tracking number, an address match, or a transaction log.
A not as described chargeback is different. The customer isn't claiming the charge was fraudulent or the item never arrived. They're claiming it arrived and was wrong — not what the listing promised, not the quality they expected, not the thing they thought they were buying. On Stripe, this surfaces as the product_unacceptable dispute reason; on the card networks it usually maps to Visa reason code 13.3, Not as Described or Defective Merchandise, or Mastercard's 4853.
This is the one dispute category that argues about meaning rather than money. And meaning is exactly where the burden of proof quietly shifts onto you.
Why these are harder to win
In a fraud dispute, the question is binary and the network leans toward making the merchant prove the cardholder was involved. In a not as described dispute, the network has already accepted that a real customer made a real purchase. What's in question is whether the thing they received lived up to what they were sold.
That sounds like it should favor you — they got the product, after all. But the framing is treacherous. The cardholder has effectively made a claim about a gap between promise and delivery, and the issuing bank's reviewer has only two documents to compare: what the customer says they were promised, and what you can show you actually promised. If your side of that comparison is thin — a one-line product title, a stock photo, no record of what the customer agreed to — the reviewer fills the gap with the customer's version.
There's a cognitive reason this works against merchants. People reconstruct disappointment after the fact. A customer who is unhappy with a purchase for reasons that have nothing to do with the description — buyer's remorse, a cheaper option elsewhere, a product that's fine but not delightful — will often reach for "it wasn't what was described" because it's the socially acceptable, refundable version of "I changed my mind." Psychologists call this motivated reasoning: the conclusion comes first (I want my money back), and the justification is assembled to fit. The dispute reason isn't a lie so much as a story the customer has come to believe.
Your job in the response isn't to call them a liar. It's to make the original promise so concrete and well-documented that there's no room left for a reconstructed version.
What you're actually proving
A not as described representment has to answer one question: did the product the customer received match what they agreed to buy at the moment they bought it?
Notice the precision. Not "is the product good." Not "do other customers like it." Did this delivery match that promise, frozen at the timestamp of purchase. Three things follow from that.
The promise has to be the one they saw. The description that matters is the one live on your site the day they checked out — not the improved copy you wrote last week, not what you meant to say. If you've edited a product page since the order, the reviewer will weigh the version the customer can point to. Keep an archive of your listings, or at minimum be able to reconstruct what was published on the order date.
The agreement has to be documented, not assumed. Specs, dimensions, materials, delivery timelines, what's included and what isn't, and especially anything the customer might later call a surprise — "final sale," "digital only," "some assembly required." If a customer accepted terms at checkout, the record of that acceptance (the timestamp, the IP, the checkbox text they agreed to) is some of the strongest evidence you have, because it shows informed consent to the exact thing they're now disputing.
The delivery has to be shown, not described. If you can demonstrate what actually shipped — order photos, batch QA images, the file the customer downloaded, the version they accessed — you close the gap from the other side. For physical goods, a photo of the packed item before it left is worth more than a paragraph swearing it was perfect.
The evidence that moves a reviewer
Reviewers spend seconds, not minutes. They are looking for a clean side-by-side that lets them rule quickly. Assemble it for them:
The exact listing as it stood on the order date — the title, the full description, the photos, the spec table. This is your version of the promise. Make it impossible to argue you over-claimed.
Proof of what the customer agreed to — terms of service, return policy, and any disclosures, with the record of acceptance at checkout. If the dispute is "I didn't know it was non-refundable" and you have a timestamped checkbox where they agreed it was, the story collapses.
Your communication history — if the customer wrote in, what they said matters enormously. A customer who emailed "it works great, but I found it cheaper" and then filed a not as described dispute has handed you the case. Pull the support thread.
Evidence the product performed — login records, usage logs, download confirmations, delivery photos. A customer disputing that software "didn't work as described" while your logs show forty successful sessions is contradicted by their own behavior.
A short, factual narrative that walks the reviewer through it: here is what we promised, here is what they agreed to, here is what we delivered, here is the timeline. No outrage, no adjectives. Let the documents carry the weight.
The trap of arguing quality
The most common way merchants lose these is by defending their product instead of their description. You'll be tempted to explain why the item is actually excellent, why other customers love it, why the complaint is unfair. None of that is the question. The network does not adjudicate taste.
The winning posture is narrow: we made a specific promise, the customer agreed to it, and we delivered exactly that. Every sentence that drifts into "and it's a great product" dilutes the only argument that counts. A reviewer can't measure greatness. They can measure whether the spec sheet matches the delivery.
This is also why vague listings are expensive long after the sale. The thinner your original description, the more interpretive room a disappointed customer has, and the less you have to point back to. Specific, honest, slightly over-detailed product pages aren't just good for conversion — they are pre-written chargeback evidence. The merchant who writes "ships in a flat pack, assembly required, two-person job" almost never loses a not as described dispute about assembly.
Build the case before you need it
The quiet truth of not as described chargebacks is that most of the work happens before the dispute exists. The listing you publish, the terms you make customers accept, the photos you take of what ships, the support replies you keep — those are the evidence file. By the time the dispute lands, you're not building a case, you're retrieving one. Merchants who lose these usually didn't lose the argument; they never kept the record.
And the clock is short. Once Stripe notifies you, you have a narrow window — often about seven days — to gather the listing, the acceptance record, the logs, and the timeline into something a stranger can read in under a minute. That's a real scramble in the middle of a normal week, which is exactly why so many defensible disputes get conceded by default.
This is the part Argeback was built to carry. It ingests the dispute, recognizes a not as described claim for what it is, pulls the order and the evidence into a structured, reviewer-ready response, and files it before the deadline — from your phone, while the documents are still fresh. You keep writing honest product pages; it makes sure the honest record actually reaches the person deciding. If you'd rather not lose a winnable dispute to a busy Tuesday, see how it works at https://argeback.lumenlabs.works.