The notification arrives at 4:47 on a Friday, while you're standing in a parking lot holding a bag of groceries. You have received a dispute. The amount is $312. Your laptop is on a desk forty minutes away. Your next free evening is Sunday, and Sunday already has plans.

So you do what most of us do. You swipe the notification away and promise yourself you'll deal with it Monday.

That is how most disputes are lost, and the reason is not the evidence. The evidence is usually fine. What fails is the moment the dispute arrives, because it almost never arrives when you're ready for it.

The deadline is not on your schedule

A Stripe dispute comes with a due date for your evidence, and the window can be short. Depending on the card network and the dispute type, it is sometimes about a week. It is shown on the dispute itself, and you should read that date rather than assume one.

Stripe also lets you submit evidence once. We've covered that rule elsewhere, and the consequence here is simple: you can't send a rough draft now and polish it later. You get one pass, and it has to happen before the clock runs out. If you miss the date, you lose by default, whatever your records say.

So the real question is not whether you have a good case. It's whether you can turn a good case into a finished submission in the time and place you actually have.

Why "I'll do it when I'm at my desk" fails

Behavioral scientists have a name for our habit of underestimating how long tasks take: the planning fallacy, described by Daniel Kahneman and Amos Tversky. We picture the best-case version of Monday. In that version, the evidence is easy to find and nothing else comes up.

The real Monday has a customer emergency, a payroll question and a dead calendar invite. The dispute sits there, and each day it sits, the deadline gets closer while your sense of urgency stays flat. Then it's the last afternoon and you're assembling a case from scratch under pressure.

There's an emotional layer too. A dispute feels like an accusation. Someone is telling their bank you didn't deliver, or that you took money you shouldn't have. Many people put off opening it for the same reason they put off opening a letter from a lawyer. Avoidance feels like relief for about a day.

The fix is not more willpower. It's making the task small enough, and prepared enough, that the avoidance has nothing to feed on.

The idea: pre-decide everything except the facts

Psychologist Peter Gollwitzer's research on implementation intentions shows that people follow through far more reliably when they decide in advance exactly when, where and how they'll act. "If X happens, I will do Y" beats "I'll get to it."

Apply that to disputes. When a dispute lands, the only parts that should require thought are the facts of that specific case: what this customer bought, what they received and what they said. Everything else should already be decided. That includes what you submit, in what order, and in what format.

That's the dispute kit. It is a small set of things you prepare once, while no deadline is running, so that any future dispute becomes a ten-minute job you can do from a phone.

What goes in the kit

A one-paragraph business description. Reviewers see thousands of cases and know nothing about you. Two sentences on what you sell, who buys it and how it's delivered give every response its footing. Write it once and keep it somewhere you can paste from.

Your policies as plain, linkable text. Your terms, refund policy and cancellation rules should each have a stable URL. If a customer agreed to them at checkout, you want to point to the page and the moment, not describe it from memory.

A map of where proof lives. For each thing you sell, write down where the delivery evidence is. For physical goods it's the carrier tracking page. For software it's login and usage records. For services it's the email thread or the signed scope. When a dispute arrives, you shouldn't have to remember that the proof exists. You should only have to open it.

A skeleton for the response. Reviewers read quickly. A short, consistent structure helps them: what happened, what the customer agreed to, what you delivered, and what you're asking for. Fill in the blanks and send.

A rule for what you leave out. Piling on every document you own can weaken a response. Decide ahead of time that you'll include only the evidence that answers the dispute's actual reason.

Make the phone the real tool

A phone-friendly workflow has one hard requirement: the work cannot depend on a keyboard, a second monitor or a desk. That changes what you prepare.

  • Screenshots should be legible at phone size, since the reviewer's own screen may not be much bigger. Crop to the relevant lines.
  • Your key links should sit in one note you can open instantly.
  • The decision about whether to fight should be made against a rule you wrote when you were calm, not in the parking lot.

On that last point, the order matters. Stripe's own notification tells you a dispute exists. It does not tell you what's worth contesting, and it doesn't assemble anything.

Your next moves

None of this takes long. Do it today, before a dispute does it to you.

  • Turn on dispute notifications where you'll actually see them. In your Stripe settings, make sure dispute alerts reach your email and your phone, not only a dashboard you check weekly.
  • Write your two-sentence business description and save it in a note you can paste from on a phone.
  • Open your terms and refund policy on your own site and copy the exact URLs into that same note. If either page is hard to find, fix that first.
  • Write one line per product or service saying where the delivery proof lives: the tracking system, the usage log, the email thread. Then check that you can reach each one from your phone.
  • Pick your fight-or-fold rule now. For example: "I contest anything over $X where I have proof of delivery or use." You can change it later, but a default stops a bad Friday from deciding for you.
  • Put the deadline on your calendar the moment any dispute arrives, with a reminder two days before it's due, not on the day.

Where this leads

We built Argeback around this exact gap between a dispute landing and a response actually going out. It ingests your Stripe disputes, drafts an evidence-backed response from your records, and gets it filed before the deadline, all from your phone. That means the parking-lot version of you can say yes and move on with the groceries. If you'd rather not build the kit by hand, you can see how it works at argeback.lumenlabs.works. If you do build it by hand, the list above will still serve you well.