Somewhere in a spare room, a person is waiting for a package that is sitting on a stranger's porch three streets away. They did not make a typo on purpose. They were on their phone, probably walking somewhere, and "Maple Court" became "Maple Street" under a thumb. Weeks later they're angry, and the quickest route to getting their money back is a button in their banking app. You get a dispute notice with the words product not received, and a sinking sense that you're being punished for someone else's thumb.

The unsettling part is that the bank didn't make a mistake either. From the cardholder's side, the story is true: they paid, and they never got the thing. Whether you lose depends on one question that has little to do with who feels more wronged. Can you show that you shipped exactly where you were told to ship?

Why this dispute is different from a lost package

Most "not received" disputes turn on whether the parcel arrived. A wrong address dispute is odder, because the parcel often did arrive, just not at the place the customer intended. Tracking says delivered. The customer says it never came. Both are telling the truth.

That splits the argument into two questions the reviewer is really asking:

  1. Did the merchant ship to the address the customer provided?
  2. Did the merchant get any chance to fix a problem before the goods left?

The first is about records. The second is about the timeline, and it is where many merchants who think they have an airtight case quietly lose.

The record that carries the case: what the customer actually entered

The address on your shipping label proves almost nothing alone, because you wrote it. What matters is the address the customer submitted, preserved as it looked at the moment they submitted it.

Three pieces of evidence do most of the work:

  • The order confirmation email, which typically echoes the shipping address back to the buyer. If the confirmation went to the cardholder's email and displayed the wrong address, they had a moment to notice. Showing that the email was sent to the same address that appears on the payment is stronger than showing it exists.
  • A checkout record showing the address field values as submitted, with a timestamp. Many platforms store this in the order object. Export it before anyone edits the order, because an edited order often overwrites the original.
  • The billing details on the payment, shown next to the shipping address. This gives context. Cardholders sometimes ship gifts or ship to offices, so a mismatch isn't suspicious by itself, but a pattern of previous orders to the same address is helpful.

A word of caution about AVS, since people reach for it here. Address Verification compares the billing address to what the card issuer has on file. It says nothing about whether the shipping address is right. It can support that the buyer is the real cardholder, but it will not rescue a typo in the delivery field. Use it as background, not as the headline.

The timeline that decides whether you win

Here is the uncomfortable part. If the customer wrote to you before you shipped, saying "I made a mistake on my address, can you change it?" and you shipped to the original anyway, the reviewer will likely side with the customer. You were told, and you had time. Your own inbox becomes their exhibit.

The reverse is just as powerful. If the first sign of trouble came after delivery, and the customer's message arrived only once the package was marked delivered, you can show the sequence plainly: order placed, address entered, confirmation sent, label created, package delivered to that address, first complaint days later.

That is why a one-page chronology matters so much in this dispute. The reviewer doesn't want to reconstruct events from screenshots. They want a short, dated list in which every line is something they could verify. If you have already read our piece on building a chronology, this is the same discipline applied to a case where the sequence is the whole argument.

What the carrier can add

Tracking that says "delivered" is thin on its own. Ask what more the carrier can give you:

  • Delivery confirmation with the delivery address as the carrier recorded it, matching the label.
  • A delivery photo or GPS point, where the service offers one. A photo of a front door with a house number is concrete in a way a status line is not.
  • Signature records, if signature was required and obtained.
  • Any address correction notice. Some carriers flag when a label address looks wrong and correct it. If the package was redirected, that note can help or hurt, so read it before you cite it.

If the carrier can't produce much, don't pad. A short, honest submission that points to the customer's own entry and a clear timeline beats a pile of generic tracking pages.

When you probably shouldn't fight

It would be dishonest to pretend every wrong address case is winnable. A few signs the dispute leans against you:

  • The customer asked for a change before shipment and you didn't act on it.
  • The address you shipped to differs from what the customer entered (a system auto-"corrected" it, say), and you can't show they approved it.
  • Your own checkout didn't display the address back to the buyer before payment, and no confirmation went out.

In those cases, the better move may be to take the loss, fix the process, and consider offering the customer a reship at cost or a goodwill gesture before the dispute closes. You are not obliged to fight everything. You are obliged to know which fights are real.

Your next moves

Do these today, before the next dispute arrives.

  • Open your last wrong-address complaint and find the first message. Note whether it arrived before or after the label was created. That single date tells you whether you'd have won, and it shows where your process leaks.
  • Check what your confirmation email displays. Make sure the full shipping address appears in the email, not just "your order is confirmed." If it doesn't, change the template this week.
  • Add an address review step at checkout. A final summary screen showing the address as typed, or a basic autocomplete or validation tool, catches a surprising share of typos before they cost you anything.
  • Create a rule for change requests. Decide who watches the inbox for "wrong address" messages in the hours before dispatch, and put the label-hold step in writing.
  • Save the original order record when a dispute opens. Export the checkout entry and the confirmation email send log to one folder before anyone edits the order. Stripe lets you submit evidence once, so assemble it fully before you press send.

Fighting calmly, from wherever you are

The reason merchants lose cases like this is rarely the evidence. It is the 7-day clock, a busy week, and the fact that the records are scattered across a shipping dashboard, an inbox, and a payment platform. Argeback was built for that moment: it pulls the dispute in, gathers what your records show about the order, drafts a response that tells the sequence plainly, and files it before the deadline, all from your phone. If you want a steadier way to handle the next one, you can see how it works at argeback.lumenlabs.works.