The box is on the porch right now. It arrived on a Tuesday, eleven days after the customer stopped believing it would. By then they had already called their bank, because calling their bank was the only thing that made them feel like someone was listening. The dispute landed in your Stripe dashboard three days before the delivery scan. So now you are holding a chargeback for a product the customer owns, may already be using, and has no plan to send back. And the part that makes it hard to argue is this: somewhere in the middle of that wait, they weren't wrong.

A late delivery chargeback is not a fraud case. It is not even really a dispute about the product. It is a dispute about a promise, and about how it feels to be the person waiting on the other end of one.

The wait is the product

In 1980, the marketing researcher Richard Oliver published what became known as expectation disconfirmation theory, and it has held up remarkably well since. The idea is simple and a little uncomfortable for anyone who sells things: satisfaction is not driven by how good the outcome is. It is driven by the gap between what the customer expected and what they perceived. Beat the expectation and you get delight. Miss it, even slightly, and you get a dissatisfaction that is out of proportion to the actual harm.

Now apply that to a package. The customer did not buy a lamp. They bought a lamp that arrives by Friday, because that is what the checkout page said, or what the confirmation email implied, or what the tracking link promised. Friday comes. Nothing. The expectation is now disconfirmed. But it does not stop there. They check tracking on Saturday. The expectation has quietly reset to Saturday, and Saturday breaks too. A tracking page that does not move is a machine for manufacturing one broken promise per day.

By day eight, the feeling has stopped being about the lamp. It is about being forgotten. Nobody wrote to say the shipment was stuck. Nobody acknowledged the thing that was obviously happening. And then the customer discovers that their bank will respond to a tap on a screen within the hour, while you have not responded at all. The dispute is not an act of theft. It is the only lever in reach that produces a human reaction.

Understanding this does not mean you concede. It means you know exactly what you are rebutting, which is not 'I never got it.' It is 'nobody told me.'

What the reason code actually says

On Stripe, this arrives as a product_not_received dispute. Underneath, the card networks are more specific. Visa's reason code 13.1, Merchandise or Services Not Received, covers two situations, not one: the cardholder never received the goods, or the cardholder did not receive them by the agreed-upon delivery date. Mastercard's 4853 cardholder dispute family includes the same 'not provided' claim. That second clause is the one most merchants miss. If you displayed a delivery date and missed it, the customer had a technically valid basis on the day they filed.

Here is what changes the picture. The issuing bank's reviewer evaluates the dispute at the time you respond, not at the time it was filed. If the merchandise has since been delivered to the address on the order, and the cardholder has kept it, the dispute has lost its footing. The remedy the networks contemplate for a late delivery is a return and a refund, or a negotiated partial credit. It is not keeping the goods and the money. A reviewer does not want to endorse that outcome, and your job is to make it impossible for them to miss that this is what they would be endorsing.

The evidence that wins is a timeline, not a tracking number

Most merchants respond to this dispute by pasting a tracking number and a delivery confirmation. That proves the second half of the story and ignores the first. The reviewer still sees a customer who was promised Friday and got a box on the following Tuesday week, and a merchant who looks like they were absent for the whole stretch in between. You need three pieces, in order.

First, the promise as it was actually made. Pull the exact words from your checkout page and order confirmation. 'Ships in 3 to 5 business days' is a shipping window, not a delivery date, and the distinction matters enormously. 'Arrives by December 20' is a delivery commitment you own outright. Screenshot the page, dated, and include the confirmation email. If your promise was a shipping window and you met it, the carrier's delay is not a disconfirmation of anything you said. Say so plainly.

Second, the communication during the wait. This is the piece that decides most of these disputes, and the one most merchants cannot produce. Did you email the customer when the shipment stalled? Did they email you, and did you answer? A delay notice with a timestamp, sent before the customer filed, is proof that you did not go silent. It also quietly reframes the customer's claim: they were told, they chose to wait rather than cancel, and they then disputed anyway. If you have nothing here, say nothing about it. Do not invent it, and do not draw attention to its absence.

Third, the delivery and the aftermath. The carrier's delivered scan with the address matching the order. A photo or signature if the carrier provides one. Then the part that closes the door: no return request, no contact after delivery, and, for anything with an account or activation, evidence that the product has been used. Finish by citing your return policy and the fact that the customer agreed to it at checkout, with the window still open or recently closed. The reviewer now sees a customer who has a path to a refund that does not involve the bank, and chose not to take it.

The narrative that ties it together is short. The expected date was this. We notified the customer of the delay on this date. The item was delivered on this date to the address on file. The customer has kept it and has not requested a return under a policy they accepted. We ask that the dispute be reversed.

Contact the customer anyway

There is a version of this where you win the dispute and the customer still hates you, and that version costs more than it looks. Before you file, write to them. Acknowledge the delay without hedging. Offer a return and full refund if they genuinely no longer want the item, or a partial credit if they are keeping it. Some will take the return, which is a clean end. Some will withdraw the dispute, which you should still back up with your own response, since a withdrawal does not always reach the issuer in time. And a few will keep the item and ignore you, which is precisely the behavior your evidence now documents.

The gap you can close before the next order

Oliver's theory has a practical corollary: an expectation that is reset before it breaks does not produce the dissatisfaction spike. A delay email sent on day four, before the customer has noticed, is not an apology. It is a new promise replacing the old one while the old one is still intact. The customer who gets it is annoyed. The customer who does not get it is wounded. Only one of them calls the bank.

Your next moves

  • Open your checkout page and your order confirmation email right now and copy the exact sentence about delivery timing. If it says 'arrives by,' either change it to a date you hit nearly every time or change it to a shipping window you control.
  • Set up one automated email that fires when a shipment shows no carrier movement for three business days. Two sentences: what happened, what you are doing, how to cancel if they would rather not wait.
  • Pull your last three product-not-received disputes and compare the delivery scan date to the dispute-filed date. If the scan came after the filing, those were late delivery disputes, and you now know what evidence they needed.
  • Save a dated screenshot of your checkout page's delivery language and your return policy to your evidence folder today, so the version the customer saw is the version you can show.
  • For any late delivery dispute currently open, email the customer this afternoon with a return offer, then assemble the three-part timeline above before the deadline, not after.

The reason these disputes get lost is rarely the evidence. It is that the timeline lives in four places, the checkout page, the inbox, the carrier portal and Stripe, and the seven-day window closes while you are still gathering it. Argeback pulls your Stripe disputes in, drafts the evidence-backed response around the delivery timeline and your policy, and files it before the deadline, from your phone, so a package that finally arrived does not turn into a refund you never agreed to. If late deliveries have been quietly costing you, you can see how it works at argeback.lumenlabs.works.