Somewhere in your inbox there's a message that says this is exactly what I needed, thank you so much. Three weeks later the same person tells their bank they never got what they paid for. Both statements carry their name. Only one of them is true, and the one that hurts more is the one the bank is currently reading.
If this has happened to you, you probably know the feeling. It isn't anger at first. It's a small, quiet doubt: was I wrong about them? Was I wrong about my own work? You go back and reread the review, almost hoping you misremembered how warm it was. You didn't.
That doubt is worth setting down for a moment, because it gets in the way of the useful thing. A customer who praised you and then disputed the charge hasn't erased the praise. They've handed you a record, written in their own words, made at the moment closest to the experience itself. In a dispute, that record is often worth more than anything you could write in your own defense.
Why the earlier version of the story is the stronger one
Psychologists have spent decades showing that memory doesn't work like a recording. Elizabeth Loftus's research on reconstructive memory found that people rebuild past events each time they recall them, and that later information, mood, and suggestion can reshape the result. Nobody has to be lying for this to happen. The customer who disputes a charge a month later may really have come to believe a different version of events. Maybe money got tight. Maybe the product stopped feeling new. Maybe a statement line looked unfamiliar and the rest of the story filled itself in around that.
This is also why investigators, courts, and auditors have long given extra weight to contemporaneous records, meaning statements made at or near the time of the event, before hindsight had a chance to edit them. A review written two days after delivery belongs in that category. A dispute filed six weeks later does not.
You aren't trying to call the customer a liar. You're showing the reviewer two accounts from the same person and pointing out which one was written closer to the facts. Making the case that way keeps it calm and specific, and hard to argue with.
What the review actually proves, depending on the dispute
A positive review doesn't win every chargeback automatically. What it proves depends on what the customer claimed, so start with the reason code.
If they claimed fraud or an unrecognized charge, the review can show that the cardholder made the purchase. A person who never placed the order doesn't usually leave detailed praise for it. The catch is that you have to connect the review to the cardholder: same name, same email, a verified-buyer badge, an order number, or a review link sent only to that customer's address.
If they claimed the product never arrived, a review that mentions using it, describes how it fits or works, or includes a photo is direct evidence of possession. You can't really review a candle you never lit.
If they claimed it wasn't as described or was defective, the review shows the product matched their expectations when they first had it. It's especially useful when they named the specific feature they're now complaining about. "The color is perfect" carries a lot of weight against a later claim that the color was wrong.
If they claimed they cancelled or were promised a refund, the review helps less on its own. Pair it with the timeline. A glowing review posted after the date they say they cancelled undercuts that story.
In every case, the review supports the main evidence (delivery confirmation, usage logs, communication history). It strengthens your response a lot, but it doesn't stand in for the rest.
The link that makes or breaks it
This is where most merchants lose evidence they really had. The reviewer at the bank has never seen your website. If you submit a screenshot of a review signed "Jess M.", they have no reason to believe Jess M. is the cardholder. You need to close that gap for them.
The strongest links, roughly in order:
- A review platform record that ties the review to a specific order ID or the customer's email address
- A review request email sent to the cardholder's address, with a unique link, followed by a review submitted through that link
- A private message or support email where the customer praised the product, sent from the same address used at checkout
- A public review whose name, location, photo, or product details match the order closely enough that the reviewer can see the connection without straining
Private praise often counts for more than public praise here. A one-line "love it!" reply to your shipping confirmation email already arrives tied to the right address, timestamped, and in the cardholder's own words. Merchants tend to overlook these because they don't feel like "reviews." In a dispute they're often the cleanest evidence you have.
Presenting it without sounding wounded
The temptation, especially when the review felt personal, is to let some of that hurt into the response. This customer told us they loved it! The exclamation point is understandable. It also reads as emotion, and emotion is easy for a reviewer to skim past.
State it flatly instead. Put the dates in order. Quote the customer's exact words, short, in quotation marks, attributed by date and channel. Then name the contradiction once, plainly: the cardholder states the item was not received, but on a specific date, from the email address on the order, they wrote that it "arrived fast and fits perfectly."
That's the whole argument. Don't add commentary about the customer's character or speculate about why they changed their story. A reviewer who sees a clean timeline will draw the conclusion on their own, and a conclusion they reach themselves tends to stick better than one you push at them.
It also helps to remember that the person reading your response sees a huge volume of these. They're looking for something specific that settles the question. Your customer's own sentence, placed next to their own claim, does that.
The part you can fix before the next one
There's a reason this kind of evidence so often falls apart: it was never collected in a way that holds up. Reviews on third-party platforms get edited or deleted, and sometimes the customer deletes theirs once the dispute starts. Review widgets show a first name and a star rating with nothing tying them to an order. Support emails get archived and forgotten.
None of that takes much effort to prevent. It just takes deciding, ahead of time, that warm words from customers are records worth keeping and not only nice moments to enjoy.
Your next moves
- Search for the disputing customer today. Look up their name and email in your review platform, your support inbox, your social mentions, and replies to your transactional emails. Praise sometimes turns up where you'd never think to file it.
- Capture anything you find with its context. Screenshot the full page, including the URL, the date, and any verified-buyer badge. If the platform lets you export the record behind the review (order ID, reviewer email), export it now, before the customer has a chance to edit or delete it.
- Write a three-line timeline. Order date, the date and exact words of the praise, and the dispute date with the reason claimed. If you can't write those three lines clearly, the reviewer won't be able to follow them either.
- Change your review request flow this week. Send review requests only to the checkout email, with a unique link per order, and make sure your review tool stores the order ID with each submission. Future reviews will then be linked to orders automatically.
- Make a "kind words" folder or label in your inbox. Every time a customer writes something warm, file it there. It takes two seconds, and it doubles as something to reread on the days a dispute makes you doubt your work.
Letting the record speak
The hardest part of a dispute after a positive review is the doubt it plants about the relationship and about whether your work was as good as you thought. Usually it was, and the customer said so at the time. Argeback is built for that moment. It pulls in your Stripe disputes, helps you put together a response that sets the customer's earlier words next to their later claim, and files it before the deadline, from your phone, so the record gets heard even in a week when you don't have time to sit down and argue. If you'd like a hand with the next one, you can see how it works at argeback.lumenlabs.works.