The notification arrives at 9:42 on a Tuesday night. A customer you helped, patiently, over four emails, has told their bank that you stole from them. You read the dispute reason twice. Your face goes hot. You open the response form and start typing, and every sentence you write is true, and almost none of them will help you win.

This is the part of chargebacks nobody puts in the how-to guides. The process is procedural. The experience is not. A dispute can feel like an accusation of dishonesty, and your first instinct is to answer the accusation instead of the case.

That instinct is human. It is also the most expensive thing in the process.

The reader you're really writing for

Somewhere downstream, a person or a queue works through your response. They did not meet your customer. They have not read the four emails. They are looking for specific things: did the cardholder authorize this, was the product delivered, does the evidence match the claim.

Anger gets in the way of that reader. A paragraph about how the customer "clearly never intended to pay" is a claim about someone's mind, and you cannot document it. A line like "this is obviously fraud by the customer" asserts intent that your records can't show. To a neutral reader, a sentence that can't be checked doesn't add weight. It makes the checkable sentences around it look less careful.

Your records are strong precisely because they have no feelings. A delivery confirmation doesn't care how you feel. A login log doesn't either. The job is to let those documents speak and keep your voice out of their way.

Why it feels personal (and why that's partly a trick of the mind)

Two well-documented tendencies explain much of the heat.

The first is the fundamental attribution error, described by Lee Ross in the 1970s: when someone else does something that harms us, we tend to explain it by their character ("they're dishonest") rather than their circumstances ("they didn't recognize the charge," "they panicked about money," "they forgot signing up"). Many disputes come from circumstances like those. Your brain, though, hands you a villain.

The second is hostile attribution bias, studied extensively by Kenneth Dodge and colleagues in research on social information processing. When an event is ambiguous, people who feel threatened read hostility into it. A chargeback is an ambiguous event. It might be fraud, a misunderstanding, a billing-descriptor mix-up, or a customer who never contacted you first. Your threat response resolves the ambiguity toward "they did this to me."

Neither tendency makes you foolish. They make you a person with a nervous system. But they do mean that the story you feel in the first hour is an unreliable draft of what happened.

What to do with the heat

Psychology offers a few tools with real support behind them, and they're cheap.

Name the feeling. In a 2007 study by Matthew Lieberman and colleagues, participants who put emotions into words ("affect labeling") while viewing emotional faces showed reduced amygdala activity compared with those who did not. The effect is modest and context-dependent, but the practical version is easy: before you write anything, type or say one sentence, "I feel insulted and I want to be believed." It sounds silly. It moves the feeling out of your drafting hand.

Reappraise. James Gross's work on emotion regulation separates two strategies: suppression (clamping down on the expression) and cognitive reappraisal (changing how you interpret the event). Reappraisal tends to work better, with fewer physiological costs. For a dispute, reappraisal looks like swapping "they're accusing me" for "the bank is asking me a question, and I have the receipts." The facts haven't changed. The job has.

Create a short delay. You don't have time for days of reflection; the clock is real and the deadline typically leaves about a week. But you almost always have time for a twenty-minute gap and one night's sleep. Treat the first draft as private. Write the furious version into a separate note, get it all out, then close it.

Converting rage into a checklist

Once the heat has dropped, the angry draft is useful in one way: it tells you what you most want the reviewer to understand. Mine it for facts and discard the adjectives.

Suppose your furious draft says: "This customer used the product for three weeks, never complained, and is now lying to get free stuff." Strip it down.

  • "Used the product for three weeks" becomes a dated usage or delivery record.
  • "Never complained" becomes a statement that no support contact appears before the dispute, and you attach the empty inbox export.
  • "Lying to get free stuff" becomes nothing. You delete it. The evidence implies it; your sentence only risks it.

The result is a response that reads, in effect, "Here is what happened, in order, with proof." It lacks the satisfaction of the angry version. It has far more persuasive force, because the reader can verify every line.

The decision you're also making

Anger distorts one more choice: whether to fight at all. Two bad versions show up. One is the merchant who fights every dispute out of principle and burns time on cases with no evidence. The other is the merchant so stung that they let the deadline slide to avoid the feeling, which is how disputes get lost by default.

Both are avoidance of the same thing. In the first, you avoid feeling powerless. In the second, you avoid feeling the sting at all. A calm look at the evidence replaces both with a plain question: does my record support the claim I'd make? If yes, file. If no, you've saved yourself an afternoon, and you can let it go without the story that it was a verdict on your honesty.

It wasn't. Most disputes are an administrative event that happened to land on your name.

Your next moves

  • Write the angry version, then park it. Open a blank note, type every furious thing you want to say, and close it. Don't paste any of it into the response form. Set a timer for 20 minutes before you open the dispute again.
  • Name the feeling in one sentence. Write "I feel ___ and I want ___" at the top of the note. It takes ten seconds and helps separate the feeling from the filing.
  • Highlight every claim you can attach a document to. Go through your draft. Keep only sentences that point to a record: a timestamp, a delivery confirmation, a signed agreement, a message thread. Delete the rest.
  • Replace every mind-reading line with a dated fact. "They knew what they were buying" becomes "Customer accepted the terms on [date] at [time], see attached."
  • Check the deadline and calendar your real cutoff. Find the response due date in your dashboard, set a reminder for the day before, and decide now when you'll do the final read, so the cooling-off period never becomes the reason you miss it.

Where a tool earns its place

The uncomfortable fact is that the hardest part of a dispute isn't the evidence. It's the person assembling it, at night, a little hurt. That's the reason we built Argeback to do the cold part for you: it pulls the dispute in, drafts a response from the records instead of from the feeling, and lets you review and file from your phone before the 7-day deadline. You still make the call. You just make it from the calmer version of yourself. If you'd like to see how that works, you can look at Argeback whenever the next one lands.