Your customer probably isn't lying. That's the hard part. They remember cancelling the order. They can picture it: the evening they changed their mind, the moment they decided they didn't need it. They will tell their bank, with total conviction, that they cancelled days before you shipped. And the cancellation request you'd need to honor that claim doesn't exist anywhere: not in your inbox, your order system, or your support history. They aren't inventing a story to get their money back. Their memory has filed something they intended to do under things they actually did.
If you've ever received a chargeback for a cancelled order you never knew was cancelled, you know the particular sting of it. It feels like an accusation. You did everything right and you're being called a thief in a form letter. Most merchants answer in one of two ways: they write an angry, defensive rebuttal, or they decide it isn't worth the fight. Both usually lose. What wins is understanding why the dispute exists in the first place, then building a response around the gap between what the customer remembers and what the record shows.
The memory error behind the dispute
Psychologists have a name for this: reality monitoring. The term comes from work by Marcia Johnson and Carol Raye, who studied how people tell memories of real events apart from memories of things they only imagined or planned. We don't store a neat label on each memory saying this happened or I only thought about this. Later, we work out where a memory came from by checking features like sensory detail, context, and how vivid it feels. Most of the time that works. Sometimes it fails, and an imagined or intended action gets remembered as one we performed.
Research on imagination inflation found something related: repeatedly imagining an event can make people more confident it really happened. Now think about your customer. They had second thoughts about the purchase. They probably pictured cancelling more than once, maybe while lying in bed or while telling a partner, “I'm going to cancel that.” Maybe they opened your site, got distracted, and closed the tab. Each rehearsal made the intention more vivid. A week later the package shows up, and their honest, sincere memory says: I cancelled this.
This is why a cancelled-order dispute is a different kind of fight. You are not catching a fraudster. You are giving a neutral third party (the issuing bank's dispute reviewer) a record that is more reliable than a sincere memory. Reviewers can't judge sincerity. They can judge timestamps.
What the dispute is actually asking
On Visa, these disputes often come under reason code 13.7, Cancelled Merchandise/Services. Other networks fold similar claims into their broader cardholder-dispute categories, and the label you see in Stripe depends on how the network's code maps across. Whatever the label, the cardholder's claim comes down to three statements:
- I cancelled.
- I cancelled in time, or in a way the merchant's policy allowed.
- The merchant charged me anyway and didn't refund.
Your job is to break one link in that chain, ideally the first. If you can show there's no record of a cancellation through any channel the customer could have used, the other two claims have nothing to stand on. If there was a cancellation attempt but it came after shipment or outside your stated policy, you go after the second link. If you accepted a cancellation and then failed to refund, the honest move is to refund and stop fighting. That's a dispute you should lose.
What you don't need to argue is that the customer is a liar. Leave their character out of it. A reviewer who reads “this customer is clearly trying to scam us” starts doubting you. A reviewer who reads “we have no record of any cancellation request, and here is every channel we checked” starts doubting the claim.
Proving a negative, which is less impossible than it sounds
The tricky part of this dispute is that you're proving something didn't happen. You can't attach a screenshot of an email that was never sent. What you can do is show that you looked everywhere a cancellation could have arrived, and show what the customer did do during the window they say they cancelled in.
That second part is often the strongest. Customers who believe they cancelled frequently left a trail that says otherwise:
- They opened the shipping confirmation email.
- They clicked the tracking link, sometimes more than once.
- They logged into their account after the supposed cancellation date and the order still showed as active.
- They wrote to support about something else, such as a delivery window or a sizing question, without mentioning a cancellation.
That last one matters a lot. Someone who had cancelled an order doesn't usually ask when it will arrive. A support message like that, timestamped after the date they claim to have cancelled, is the kind of evidence that settles the question for a reviewer without anyone having to call anyone a liar.
Stripe's dispute evidence form has fields for exactly this: your cancellation policy, how and where that policy was shown to the customer, and a cancellation rebuttal where you explain why the customer isn't entitled to a refund. Use the rebuttal field to tell the story as a timeline rather than an argument. Order placed on this date. Confirmation sent and opened on this date. Shipped on this date. Tracking viewed on this date. No cancellation request received through email, contact form, chat, phone, or the account dashboard. Dates do the persuading.
Your policy is only half the evidence
Many merchants attach their cancellation policy and assume that settles it. It doesn't, for the same reason a refund policy doesn't stop disputes on its own. A reviewer needs to see that the customer had a real, visible way to cancel and a clear statement of when cancelling stops being possible.
If your policy says orders can be cancelled until they ship, show the reviewer where the customer would have learned that: the checkout page, the confirmation email, the order status page. If your system has a cancel button that disappears once the order is fulfilled, take a screenshot of what the order page looked like at each stage. A reviewer who can see that the customer had an obvious, working way to cancel, and that no cancellation went through it, has little reason to side with the cardholder.
There's a quieter lesson here, too. If your cancellation process is hard to find, say a policy buried in a footer or a request that only works by email to an address nobody checks, the reality-monitoring problem gets worse. Friction is exactly what turns I meant to cancel into I thought I cancelled. The easier cancelling is, the more confidently you can say a cancellation that isn't on record never happened.
The emotional trap on your side
It's worth naming what these disputes do to you. Being accused of keeping money you weren't owed when you were careful the whole time triggers something close to moral injury. The instinct is to defend your integrity. That's why so many rebuttals for cancelled orders come out long, hurt, and full of adjectives.
The reviewer can't feel your hurt, and it doesn't help you. What helps is the same thing that helps with the customer's memory: a calm, external record that doesn't depend on anyone's feelings. Treat the rebuttal as an act of documentation. You're not pleading your case. You're giving someone the file.
Your next moves
- Search every cancellation channel today and screenshot the results. Check email (including spam and any shared inboxes), your contact form submissions, live chat logs, phone or voicemail records, and account-dashboard actions for the disputed customer. Capture each empty search with the date range visible.
- Pull the customer's post-purchase activity. Export email open and click data for the order and shipping confirmations, tracking-link views, and any login or support contact after the date they say they cancelled. Put it in a single timeline.
- Screenshot your cancellation flow end to end. Show where the policy appears at checkout, what the order page looks like before and after fulfillment, and the confirmation email wording. Store these with dates so you can reuse them in future disputes.
- Rewrite your rebuttal as a dated timeline of six to ten lines. Cut every sentence that describes the customer's motives. Keep only events, timestamps, and the channels you checked.
- Add one sentence to your shipping confirmation email this week: something like “This order has shipped and can no longer be cancelled. Reply here if anything looks wrong.” It gives the customer's memory a clear reference point and gives you evidence they were told.
Where Argeback fits
The hardest thing about a cancelled-order chargeback is that winning it means calmly reconstructing a timeline under a deadline, right when you feel most like defending yourself. Argeback was built for that. It pulls in your Stripe disputes, drafts an evidence-based rebuttal that leads with dates instead of indignation, and helps you file it before the response window closes, all from your phone. If a customer's sincere memory is about to cost you money you earned, let Argeback assemble the record and let the timeline make the case.