You will remember the first one. The email arrives on an ordinary afternoon, subject line flat and bureaucratic: a customer has disputed a payment. Nothing about the words is cruel. Your stomach drops anyway, as if someone had read a private note about you aloud in a quiet room.

You open it, scan it, and close it. Maybe you tell yourself you'll deal with it tomorrow. Maybe you start composing, in your head, the long and wounded paragraph explaining everything you did right.

Both reactions have the same root. Somewhere between the notification and your pulse, a transaction turned into a judgment.

The sting is real, and it has a source

If you built the thing yourself, the product carries some of your identity. Psychologists have long described how people fold their work into their self-concept, and for a solo founder or a small shop the fold is tight. A refund request reads as feedback. A chargeback reads as something harsher: not "I'm unhappy," but "I'm calling your bank to take it back."

The structure of the event adds to it. A dispute is a move made around you. The customer didn't write to you, argue with you, or give you a chance to fix anything. You learn about it second-hand, from a platform, with a clock attached. Being accused in your absence is a particular kind of unpleasant, and your mind fills the silence with the worst available story: they think I scammed them.

That story is usually wrong, and the rest of this piece depends on seeing why.

What the customer actually did

Picture the other side of the screen. Someone scrolls their banking app, sees a charge they don't instantly place, feels a flicker of unease, and taps it. The app offers a short menu of reasons. They pick the closest one and confirm. Often the whole thing takes a couple of minutes.

There's no courtroom in that scene and no accusation in the usual sense. The menu forces a choice, and the choices are blunt. "Fraudulent" or "not received" may be the nearest option for someone who is merely confused, forgetful, or embarrassed to admit they forgot a subscription. Chargeback reason codes describe the category a bank filed the dispute under. They do not describe your character.

This is the first reframe worth holding: the dispute is a form field, not a verdict. Sometimes the person is lying. Often they are confused, hurried, or avoiding an awkward email. You don't have to decide which, because the process doesn't ask you to. It asks for evidence.

Why feeling attacked makes you lose

The emotional reaction isn't only unpleasant. It changes what you do, and almost always for the worse. It tends to push merchants in one of two directions.

The first is avoidance. The notification feels bad, so you delay opening it, and the response window narrows while you aren't looking. This is the cheapest way to lose a dispute you could have won, because an unanswered dispute is lost by default.

The second is the wounded essay. You write a long, defensive rebuttal that argues about the customer's motives instead of laying out what happened. Reviewers read a great many of these. A narrative about betrayal gives them nothing to check, while a clean sequence of dated facts does.

Both responses protect your feelings and neglect your case. Neither is a character flaw. They are what a mind does when it treats a procedural event as a personal threat.

A tool from the research: change the frame, not the facts

Emotion researchers describe a strategy called cognitive reappraisal: reinterpreting what a situation means before the emotion fully sets in. James Gross's work on emotion regulation compares it with suppression, where you grit your teeth and push the feeling down. Reappraisal tends to work better because it changes the feeling at its source instead of managing its symptoms.

A second, related tool is self-distancing, studied by Ethan Kross and colleagues. When people think about a distressing event from the viewpoint of an observer, or address themselves by name instead of "I," they often reason about it with less emotional flooding. It sounds like a parlor trick. It's a simple way to put a few inches between you and the sting.

Applied to a dispute, it looks like this. Instead of "They're accusing me of stealing," you think: "A cardholder filed a dispute under a reason code. The question on the table is whether the evidence shows the service was delivered as agreed. That's a records problem." The facts are the same. The feeling is smaller, and you can act on it.

There's one more piece, from Peter Gollwitzer's research on implementation intentions: plans shaped like "when X happens, I will do Y" make follow-through more likely than vague resolve. They also help most when motivation is shaky, which is exactly how you feel when the notification lands.

Your next moves

None of these require you to feel better first. They work around the feeling.

  • Write your if-then rule today. Put it somewhere you'll see it: "When a dispute notification arrives, I open it within one hour, note the response deadline on my calendar, and do nothing else yet." Opening and dating it is the whole job for the first hour. The point is to remove the decision about whether to look.
  • Hold a fixed cooling-off window, then switch to a checklist. Give yourself a short, set period to feel whatever you feel, then work from a written list: the payment details, the customer's account history, the delivery or usage records, any support emails, and the policy they agreed to. A list turns a personal injury into a task with edges.
  • Say the reframe out loud, in the third person. Literally: "[Your name], this is a form a stranger filled out in a banking app. Your job is to show what happened." It feels silly for about four seconds.
  • Write your response as a dated sequence, not a defense. First draft, facts only: what was purchased, when, what the customer received or used, what you communicated. Delete every sentence that guesses at their motives or defends your honor. If a sentence couldn't be checked against a record, it doesn't belong.
  • Decide in advance who reads your drafts when you're upset. If you're prone to the wounded essay, send the draft to a trusted person, or leave it overnight, and edit it the next morning. Sleeping on a draft costs nothing as long as you have already noted the deadline.

What it looks like when the sting fades

The merchants who handle disputes best aren't the ones who stop caring. They're the ones whose caring has been routed into process. A dispute arrives, they date it, they pull the records, they write down the sequence, and they file. Win or lose, they run the same motions and move on to the next customer.

There's a quiet freedom in that. If the outcome depends on evidence, then losing one doesn't mean you failed as a person. It means a record was missing or a deadline was tight, and both of those can be fixed. And a customer who made a hurried tap in a banking app has told you almost nothing about your worth.

Where a tool earns its place

The hardest part of a dispute is often not the logic. It's opening the thing at all. Argeback exists for that moment: it pulls your disputes in, drafts an evidence-backed response from your records, and gets it filed before the deadline, all from your phone. The draft arrives as a starting point already built from facts, so you aren't staring at a blank page while your stomach is in knots. If the sting is what keeps you from fighting, it's worth seeing what it's like to have the first draft done for you at argeback.lumenlabs.works.