Somewhere tonight, a person is telling a bank representative, with complete sincerity, that they mailed a package back to you. They can picture it. The tape, the label printed at the library, the box on the passenger seat. They are not lying. And the package is still sitting in their hallway closet, under a winter coat, where it has been for three weeks.

You'll never see that closet. What you'll see is a dispute notification, a frozen balance, and a claim that you kept both the money and the merchandise. It's a strange thing to be accused of stealing by someone who believes it, and it lands harder than ordinary fraud because there's no villain to be angry at. Just a person, a memory, and a gap between them.

This article is about that gap: why it forms, why it's so convincing to the people deciding your case, and how to close it with evidence instead of indignation.

The return that happened only in someone's head

Memory researchers have a name for confusing what you planned with what you did. Marcia Johnson and her colleagues called it reality monitoring: the brain's process for sorting memories that came from outside (things you perceived) from memories you generated yourself (things you imagined, planned, or rehearsed). Usually the sorting works. Perceived memories tend to carry more sensory detail; imagined ones carry more traces of the effort it took to think them up.

But the line blurs, especially for routine actions. Printing a return label is vivid. Taping a box is vivid. The final step, actually handing it to a carrier, is easy to postpone and easy to imagine. Later, when the customer reaches for the memory, the planning and the doing have fused into one confident story.

There's a related finding that matters even more for chargebacks. In the 1990s, Maryanne Garry and colleagues documented what they called imagination inflation: simply imagining an event makes people more confident it really happened. Every time your customer rehearses the story, to a partner, to themselves, to the bank, their certainty grows. By the time a dispute is filed, it's no longer a hazy maybe. It's a fact they'd swear to.

This is why returns disputes feel so unwinnable to merchants. You're up against a narrative that grew more confident with every retelling. Arguing with the person won't help. What helps is showing a neutral third party what actually happened to the package.

What the bank is actually asking

When a customer disputes a charge because they returned the goods, the card networks treat it as a cancellation or refund problem rather than fraud. On Visa it typically falls under reason code 13.7, Cancelled Merchandise/Services. On Stripe it often shows up as credit not processed, and the customer's claim is simple: I sent it back, they didn't refund me.

The issuer reviewing your response has one practical question. Did the merchandise actually come back to the merchant, in a state the return policy accepts? Everything you submit should answer that question and nothing else.

That means your rebuttal isn't about whether the customer is a good person, whether they were rude to support, or how much you hate dishonest disputes. It's about the package's physical journey. Banks can't open a closet, but they can read a tracking history.

The evidence that tells the package's real story

The label-created-but-never-scanned record

This is the single strongest piece of evidence in a returns dispute, and many merchants don't realize they have it. If you issued a prepaid return label, the carrier's tracking page shows two separate events: when the label was created, and when the package was first scanned into the network.

A customer who printed a label and never shipped will leave a tracking history that stops at something like Label created, not yet in system, or Shipping label created, USPS awaiting item. That one line is the reality-monitoring gap made visible. The plan happened; the action didn't. Screenshot it with the date and the tracking number, and put it near the top of your response.

The receiving record on your side

If you have a warehouse, a fulfillment partner, or even just a spreadsheet where you log returns, that log matters. A dated record of the returns you did receive during the window, with this order's absence, supports the tracking evidence. It shows you have a process and the package isn't in it.

The policy they agreed to

Issuers want to know what the customer was told. Include your return policy as it appeared at checkout or in the order confirmation: the return window, any requirement to use the provided label or a trackable method, and when refunds are issued (on receipt, after inspection, and so on). If your policy says refunds go out once the item arrives, a missing arrival is the end of the argument.

When something did come back

Sometimes the package arrives, just not the right one. An empty box, a different product, a used item where a new one was promised. Here, photos taken on arrival, before anyone handles the contents, are your evidence. Show the box, the label, the contents, and the timestamp. A receiving photo taken that day is far more credible than one taken after the dispute lands.

Your messages, quoted honestly

If the customer emailed asking for a label, or support reminded them the return hadn't arrived yet, include those messages. A short, polite note like We haven't received your return yet; here's the tracking link does two jobs. It shows good faith, and it shows the customer was told about the problem before they went to the bank.

Write the response like a timeline, not an argument

The reviewer has minutes, not hours. Give them a sequence they can follow at a glance:

Order placed and delivered on this date. Return requested on this date. Prepaid label issued on this date. Label created, no carrier scan ever recorded. Reminder sent to the customer on this date. No package received as of today. Per the policy shown at checkout, refunds are issued on receipt.

Then attach the proof for each line. Resist the urge to editorialize. You don't have to call the customer a liar, and you shouldn't. In plenty of cases they honestly believe they shipped it, and the evidence speaks better without you raising your voice. Calm documentation reads as credible; outrage reads as a merchant who knows they're on thin ice.

The quiet cost of not checking

A lot of merchants accept these disputes without a fight. Part of it is time, but part of it is something softer: the discomfort of contradicting a customer who sounds so sure. When someone tells a confident story, it's natural to start doubting your own records. Maybe we lost it. Maybe the warehouse missed it.

That self-doubt is worth noticing, because it's the same mechanism working on you. Confidence persuades people, including the person it's aimed at. The cure is the same on both sides: look at the record before you trust the feeling. Sometimes the record will show the return really did arrive and slipped through your process, and then the right move is to refund quickly and fix the leak. More often it will show a label that never moved.

Your next moves

  • Pull the tracking history for every open returns dispute today and look specifically for the gap between label created and first carrier scan. Screenshot any history that stops at label creation.
  • Switch to issuing prepaid, trackable return labels tied to the order number, so every return creates a carrier record you can retrieve later, instead of letting customers ship however they like.
  • Start photographing returned packages the moment they arrive: outside label, then contents, with the date visible. Five seconds per box now saves a lost dispute later.
  • Add an automated nudge that emails the customer if their return label hasn't been scanned within a few days of creation, with the tracking link included. It gets more returns actually shipped, and it puts a dated record in your inbox.
  • Reread your return policy and confirm it states, in plain words, that refunds are issued once the item is received. If it doesn't, rewrite that line this week.

Where Argeback fits

The hardest part of a returns dispute usually isn't the argument. It's pulling the tracking screenshot, the policy, and the support thread together into a clean timeline before the deadline passes, often while you're doing everything else. Argeback was built for exactly that moment: it ingests your Stripe disputes, assembles the evidence into a response a reviewer can follow, and files it before the clock runs out, all from your phone. If you've been letting returns disputes go because building the case felt like too much, it's worth a look at argeback.lumenlabs.works.