The kindest thing you did for that customer is about to be used against you.
You remember how it went. The first package had a problem. Maybe it was dented, maybe a part was missing, maybe it was just late. They emailed, a little sharp. You didn't argue or ask for photos. You shipped a new one at your own cost, said sorry, and felt something like pride, because that's the kind of business you wanted to run. Three weeks later, Stripe tells you they've disputed the original charge. They have the replacement, they may still have the first one, and now they also have their money.
That sting is more than financial. It feels like a judgment on you: being generous made you an easy mark. Before you start agreeing with that, here's the more useful truth. If you document it properly, the replacement is probably the strongest evidence you have.
Why the dispute happens even after you fixed it
It's tempting to call it theft, and sometimes it is. More often, though, something more ordinary is going on, and it's worth understanding because it changes how you argue.
Psychologists have a name for how people remember experiences: the peak-end rule, described by Daniel Kahneman and colleagues. We don't remember an experience as the average of every moment. We remember the most intense moment and the ending, and we mostly forget how long it all lasted. For your customer, the peak was opening a broken box. Your quick replacement was a calm, forgettable ending. When they scroll their card statement weeks later and see your charge, the memory that comes back is the bad one.
Richard Thaler's work on mental accounting adds to this. People sort money into separate mental accounts. In the customer's head, the original charge is filed under 'the order that went wrong.' The replacement, which you paid for, doesn't show up on their statement at all, so it never gets entered against that charge. From where they sit, the books look unbalanced, even though you've already paid more than once.
None of this makes the dispute fair, but it does tell you what to do. You don't need to prove the customer is a liar. You need to show the person reviewing the case the ending the customer forgot.
What the bank reviewer actually sees
The person who decides your case works at the cardholder's bank. They don't know you and they didn't see the email thread. They have the customer's claim, a reason code, and whatever you send them.
A dispute after a replacement usually arrives under one of three reason families: merchandise not received, not as described or defective, or credit not processed. Each one asks a slightly different question. Your replacement answers all three, but only if you make it answer the specific question asked.
- Not received? You show that the original was delivered, and then that a second item was delivered as well.
- Defective or not as described? You show that the defect was reported, acknowledged, and fixed with a replacement that arrived working, with no further complaint afterward.
- Credit not processed? You show that the agreed resolution was a replacement, not a refund, and that the customer accepted it.
Here's the mistake that loses these cases. Merchants send evidence about the original order: the first tracking number, the product page, the receipt. All of that is accurate, and all of it argues about the part of the story the customer already won. The bank reviewer sees a defective first shipment and sides with the cardholder. The case is decided by what happened second.
The one idea: tell the story as resolved, not disputed
The idea worth taking away is this. Your evidence needs to frame the transaction as a problem that was already solved, not a problem that's still open.
That changes what you put first. Your rebuttal shouldn't open by defending the product. It should open with the resolution, something like: The customer reported an issue on [date]. We shipped a replacement at no charge on [date], delivered on [date]. The customer has the replacement and did not report any further issue before filing this dispute.
That's three dates and one fact a reviewer can't easily wave away: the cardholder has the goods. Everything else you submit supports that paragraph.
The proof behind it has a clear order:
- The customer's original complaint. It sounds backwards, but their own email describing the problem is the anchor. It proves they contacted you and you responded, which already weakens any claim that you ignored them.
- Your reply offering the replacement, and ideally their response. A simple 'thanks, that works' is extremely valuable. It shows they accepted a resolution other than a refund.
- Shipping proof for the replacement specifically: a carrier tracking number showing delivery to the same address as the original order. Matching addresses matter, because they tie the second shipment to the same person.
- The silence afterward. If they never wrote again after the replacement arrived, say so plainly and give the date of their last message. A customer who got a broken item and then a working one, and said nothing more, has behaved like a satisfied customer.
- Whether they returned the original, if you asked for it back. If you requested the return and they didn't send it, that's relevant. If you told them to keep it, say that too, because it shows good faith rather than a hole in your case.
The point isn't volume. Five clear pieces that tell one coherent story beat thirty screenshots a reviewer has to puzzle over.
The quiet cost of being the nice one
There's a reason this kind of dispute sticks with people longer than a plain fraud chargeback. Researchers who study fairness describe sucker aversion: people really dislike being taken advantage of after cooperating, often more than they dislike losing the same amount some other way. You didn't only lose money. You lost it because you were generous, and that pushes you toward a bad conclusion: next time, demand photos, make them wait, protect yourself first.
It's worth resisting that. The generous move was the right one. What went wrong was that it lived in your inbox and a carrier portal instead of being recorded as evidence. Your policy doesn't need to get stricter. Your record-keeping needs to get better. You can keep being the business that ships first and asks questions later, as long as you keep a record of having done it.
Your next moves
- Search your inbox today for every replacement you've sent in the last 120 days. For each one, save the complaint, your offer, any acceptance, and the replacement tracking number into a single folder named by order number. Disputes on these orders can still arrive, and the records are easiest to find now.
- Ship every replacement as its own order in your system, linked to the original, even if it's a $0 order. That gives you a separate record with its own timestamp and tracking, rather than a note buried in a support thread.
- Add one sentence to your replacement emails: 'Just reply to confirm this works for you and we'll send it today.' That turns an assumed agreement into a written one, and that line is often what decides a credit-not-processed dispute.
- Pick a return policy for originals and write it down. Whether you ask for the damaged item back or tell customers to keep it, say it explicitly in the email so neither outcome looks like an inconsistency later.
- Draft your opening paragraph template now: issue reported on X, replacement shipped on Y, delivered on Z, no further contact. When a dispute arrives, you fill in three dates instead of writing under deadline pressure.
Where Argeback fits
Most merchants who lose these disputes didn't have weak cases. They had the right evidence spread across Gmail, a shipping dashboard, and their own memory, and they didn't have time to put it together before the deadline. Argeback is built for exactly that. It pulls in your Stripe disputes, helps assemble the replacement timeline into a response that opens with the resolution, and files it before the window closes, from your phone, between whatever else your day needs. If you've ever let one of these go because putting it together felt like too much, take a look at Argeback. Your generosity was the right call, and it should hold up when a dispute arrives.