Somewhere right now, a merchant is looking at a photo of their own product with a crack running through it, and their stomach has dropped. They packed that box themselves. They remember wrapping it twice. And the notification under the photo doesn't say something went wrong in transit. It says, in effect, you sent me junk and I want my money back from the bank, not from you. The broken item hurts less than what the dispute implies: that you're the kind of person who would do that.

The thing worth knowing first is that a damaged-item chargeback is almost never decided by whether the item broke. It usually did. It's decided by what happened after.

Why it feels like an accusation (and why that feeling misleads you)

When something goes wrong, people explain it differently depending on where they're standing. Psychologists call this the actor–observer asymmetry, a close cousin of the fundamental attribution error. We blame our own setbacks on circumstances, and we blame other people's on their character. The customer opening a shattered box doesn't see a forklift, a dropped pallet, or a hot truck. They see you. And when you read the dispute, you do the same thing in reverse. You don't see a disappointed person holding broken glass. You see someone trying to scam you.

That reflex, they're lying, I'll prove it, produces the weakest responses a dispute reviewer ever reads: long, wounded letters arguing that the product was perfect when it left. The reviewer may believe you completely. It changes nothing, because "it was fine when I shipped it" and "it arrived broken" can both be true at once. Damage in transit is common. Nobody has to be lying.

So the question the reviewer is actually weighing isn't who's honest? It's closer to: when this went wrong, did the merchant give the customer a reasonable way to make it right, and did the customer use it?

The real battleground: the remedy path

On Stripe, these disputes usually come in under the reason product_unacceptable, the bucket for goods that are defective, damaged, or not as described. Card network rules for this category generally expect the cardholder to have tried to resolve the problem with the merchant first, often by returning or attempting to return the item. The exact requirements vary by network and situation, but the logic underneath is consistent. A chargeback is supposed to be a last resort, not a replacement for customer service.

That gives you two very different kinds of case, and you need to know which one you're in.

Case one: the customer told you, and you responded well. They emailed a photo, and within a day you offered a replacement, a refund on return, or a partial credit. Maybe they ignored it. Maybe they accepted the replacement and disputed the original charge anyway. Your evidence here is the conversation itself: the timestamped offer, the shipping label you generated, the replacement's tracking number. You aren't arguing the item was undamaged. You're showing that you made the damage right, or tried to, and the customer went to the bank instead.

Case two: the customer never told you at all. No email, no chat, no return request. The first you heard of the damage was the dispute. Here your evidence is the silence, backed by proof that a path existed and was easy to find: your posted return and damage policy, the support address on the order confirmation, the "report a problem" link in the shipping email. You're showing that a reasonable remedy was one message away and was never asked for.

The case merchants lose most often is the third one, the one they create themselves. The customer did reach out, and the reply was slow, defensive, or demanded something unreasonable, like "ship it back at your own cost and we'll inspect it in four to six weeks." Then the dispute shows a person who tried to resolve it and got stonewalled. No packing photo saves that.

What actually counts as evidence

Once you've identified which case you're in, build the response around it. A strong damaged-item submission usually includes:

  • The order record and delivery confirmation, so the reviewer knows the item arrived and when.
  • The customer communication timeline, with timestamps, showing when damage was reported (or that it never was) and how fast you answered.
  • Your remedy offer in writing: replacement, return label, refund on return, or partial credit.
  • Your damage and returns policy as it appeared at checkout, plus how the customer saw it, such as a checkbox, a link in the confirmation email, or a line on the product page.
  • Pre-shipment documentation, if you have it: a packing photo, the packaging spec, a weight that matches the order. This is supporting evidence, not the core of the argument. It shows care, but it doesn't prove the item survived the trip.
  • Any carrier damage claim you filed. This is underrated. A claim shows you treated the damage as real and pursued it with the party responsible, which is the opposite of how a merchant trying to dodge a legitimate complaint behaves.

Then write a short rebuttal that tells this story in plain sentences: The customer reported damage on this date. We offered a free replacement the same day. The customer did not respond and filed a dispute eleven days later. Three sentences a tired reviewer can verify against the attachments are worth more than three pages of feeling.

The part nobody says out loud

There's a quieter cost in these disputes. When you make physical things, or even just choose them carefully and pack them by hand, a damage complaint lands somewhere personal. It can feel like a verdict on your competence. Some merchants respond by over-explaining, others by refunding everything immediately just to make the feeling stop, and a few by going cold toward every customer who mentions a scratch.

None of these protect you. What protects you is a process you decided on before the next broken box shows up, so that when it does, you're following a plan instead of reacting to an insult. Behavioral scientists call these implementation intentions: if-then plans ("if a customer reports damage, then I reply within 24 hours with two options") that hold up under stress far better than good intentions do. The plan does the work your bruised ego would otherwise do badly.

And it pays off twice. A fast, generous remedy turns most damage complaints into replacements instead of disputes. When a dispute comes anyway, that same fast response is the evidence.

Your next moves

  • Write your damage reply today and save it as a template. Two sentences of empathy, then two concrete options, such as "We can send a replacement right away, or refund you in full once the item is on its way back. We'll cover the return label." Commit to sending it within 24 hours of any damage report.
  • Add a visible "arrived damaged?" line to your shipping confirmation email with a direct link or address for reporting it. Every customer who uses that link is a dispute that doesn't happen, and every one who doesn't is evidence that a path existed.
  • Start photographing fragile or high-value orders before sealing the box, with the order number visible in the frame. It takes ten seconds, and it supports your case without being the whole case.
  • Look up your carrier's damage-claim window and process now, before you need it, and file a claim every time a customer reports transit damage, even for small amounts.
  • Pull your last three damage complaints and check your response times. If any reply took more than a day or put the burden on the customer, that's the gap a future chargeback will go through.

Where Argeback fits

The hardest part of a damaged-item dispute is rarely the argument. It's assembling it in time, while you're still stung by the photo: finding the support thread, the timestamps, the policy as it read at checkout, the carrier claim, and turning them into a calm three-sentence story before the deadline passes. Argeback was built for that moment. It pulls in your Stripe disputes, drafts a response organized around the evidence that actually decides these cases, and files it from your phone so the response doesn't wait until you're back at a desk. If broken boxes are part of your business, and for anyone who ships physical goods they eventually are, you can see how Argeback handles it here.