Somewhere right now, a small business owner is on a beach, a hospital ward, or a long flight, and a Stripe dispute has just opened with their name on it. Nobody else knows it exists. Nobody else can see it. The clock started the moment the email landed in an inbox that only one person reads.

That owner will not lose the dispute because the evidence was weak. They will lose it because the business had exactly one pair of hands, and those hands were somewhere else.

This is the least discussed way merchants lose chargebacks. It isn't fraud, a bad product or a clever cardholder. It's a staffing problem that looks like a deadline problem.

The single point of failure you never designed

Engineers have a blunt phrase for this: the bus factor. It's the number of people who could get hit by a bus before a project stalls. For most small online businesses, the bus factor of the dispute process is one.

It happens by accident. You set up Stripe on day one, and the notification emails go to you. You learn where the Disputes tab is. You gradually become the only person who knows how any of it works. Nobody decided this, so nobody ever reviewed it.

The cost is easy to underestimate because disputes feel rare. But a response window is short. Evidence is typically due in roughly a week, and the exact date is on the dispute itself. Stripe also lets you submit evidence once, so a rushed or missing response can't be patched up later. One week without you can be enough.

Why "I'll just check my phone" isn't a plan

Most owners reassure themselves that they'll handle it from wherever they are. Sometimes that's true. Often it isn't, for reasons that have little to do with willpower.

A dispute response asks you to gather records, write a clear account, and attach the right files. That's real cognitive work, and it's the first thing to slide when you're sick, grieving, travelling or buried in a launch. Psychologists describe a related pattern as present bias: we overweight what's pressing now and discount a deadline that's a few days out. A dispute is the perfect target. It's unpleasant, it isn't urgent today, and it can wait until tomorrow, until it can't.

There's also a social dimension. Research on diffusion of responsibility, associated with the work of John Darley and Bibb Latané on bystander behavior, shows that when several people could act and nobody is clearly assigned, action often doesn't happen. A vague "someone on the team will probably see it" is the business version of a crowd watching an emergency.

The fix for both problems is the same: name one person, give them a defined job, and make the job small enough to actually do.

Delegate the task, not the account

The instinct when handing something off is to hand over everything. Share the login, share the password, and let them figure it out. Please don't.

Your Stripe account holds payouts, bank details, customer data and refund power. A person who only needs to answer disputes doesn't need any of that. Sharing a password also removes accountability, because you can no longer tell who did what, and it tends to break the moment two-factor authentication prompts your phone while you're unreachable.

Stripe's dashboard lets you invite team members under separate logins with different roles. The exact roles and what each can see or do change over time, so check the current options in your account's team settings rather than relying on memory, including mine. The principle is stable, though: give the least access that lets the person do the job, and give each person their own login.

A useful test is to ask what the worst outcome would be if this person's account were compromised or if they made a mistake. If the answer is "they could move money out," the role is too broad for a dispute helper.

What a good handoff actually contains

A backup who has access but no context will still struggle. Disputes are a judgment call, and the person helping needs to know your standards without calling you.

The handoff doesn't need to be a manual. One page does the job:

  • Where the evidence lives. Order records, delivery proof, customer emails, usage logs, signed agreements. If it's scattered across five tools, say which tool holds which.
  • Your policy on fighting. Do you contest everything, or only above a certain amount? Do you ever concede on purpose? Decide it once so nobody has to guess.
  • Your tone. A short, factual, unemotional response reads better to a reviewer than an angry one. Tell your helper that.
  • What they must never do. Issue refunds above a limit, contact the customer in a heated way, or promise anything.
  • When to wake you. Define the exceptions, like unusually large amounts or a disputed charge from a long-term client, so they escalate the rare case without escalating everything.

That last item matters most. A delegate who has to ask permission for everything is just a slow messenger.

The deadline is the shared enemy

Who handles it matters less than whether anyone is watching the date. Make the date visible to more than one person.

The simplest version is a shared calendar entry created the day a dispute opens, with the evidence due date on it and a reminder two days earlier. Another is a dedicated email alias for Stripe notifications that forwards to both you and your backup, so a notice can't get stuck in one inbox.

The point is to remove "I didn't know it was there" from the list of ways to lose. You can still lose a dispute on the merits. You shouldn't lose one on logistics.

Your next moves

You can finish most of this in an afternoon.

  • Open your Stripe notification settings today and check which email address receives dispute alerts. Add a second address (a partner, cofounder or bookkeeper) or set up a shared alias that reaches two people.
  • Name your backup in writing. Pick one person, tell them, and ask them to say yes. An unspoken assumption is the diffusion-of-responsibility trap.
  • Invite them as a team member with their own login under the narrowest role that lets them see and respond to disputes. Check Stripe's current role descriptions first, and turn on two-factor authentication for them.
  • Write the one-page handoff covering where evidence lives, your fight-or-concede policy, tone, hard limits, and when to call you. Save it where your backup can find it without asking.
  • Run a ten-minute dry run. Ask your backup to open the Disputes tab, find a past dispute, and tell you what evidence they would attach. The gaps show up immediately, and it's far better to find them now than with a live deadline.

The quiet relief of not being the only one

There's an emotional side to this that rarely gets named. Owners who are the sole defenders of the business carry a low hum of dread: what if something lands while I'm away? That background worry is itself a cost, and it's why people check their phones on holiday and resent it.

Handing off a defined task, with limits and a deadline both of you can see, lets you actually be somewhere else. A business that can survive your absence for a week is also easier to run when you're present.

That's the gap Argeback was built for. It ingests your disputes as they open, drafts an evidence-backed response, and files it before the deadline, all from your phone. Many owners use it as a reliable backup for the weeks when they can't be the one at the desk. If a vacation, a launch, or a rough month has you wondering who would catch the next dispute, you can see how it works at argeback.lumenlabs.works.