The message says Stripe, but Stripe isn't the judge
When a dispute lands in your dashboard, the email comes from Stripe, the money leaves a Stripe balance, and the deadline ticks down inside a Stripe screen. So it's natural to picture a Stripe employee reading your case and deciding whether you were wronged.
That picture is wrong, and the error is expensive. Stripe is the messenger and the mailroom. It collects your evidence and forwards it. It does not rule. The decision that determines whether you keep your money is made somewhere you can't see, by someone you'll never email, working from rules written by a card network. If you understand who that person is and what they're allowed to look at, you stop writing for the wrong audience.
The four parties on the field
Every card payment, and therefore every dispute, runs through four roles. Learn them once and the whole process stops feeling arbitrary.
The cardholder is your customer. The issuer is the bank that gave them the card — Chase, Capital One, a credit union, whoever. The acquirer is the bank that lets you accept cards; for most Stripe merchants, Stripe acts as the acquirer or works directly with one behind the scenes. And the card network — Visa, Mastercard, Amex, Discover — is the rulebook and the referee that sits between the two banks.
Notice who's missing from the moment of decision: you, and Stripe. A chargeback is fundamentally a fight between two banks, conducted in the network's language, over your money. You are a witness who gets to submit a written statement. That reframing is the whole point.
How a disputed dollar actually moves
Here is the path, in order, because the order is what creates the deadlines that catch merchants off guard.
Your customer calls their issuer — or just taps "dispute this charge" in their banking app. The issuer doesn't investigate you; it has no relationship with you at all. It typically issues the cardholder a provisional credit, effectively fronting them the money, and then files the dispute with the card network under a specific reason code that classifies the complaint: fraud, product not received, subscription canceled, and so on.
The network routes that dispute to the acquirer. The acquirer — Stripe — pulls the funds back out of your balance and notifies you. This is the moment you feel it. But by the time you feel it, the issuer has already taken a position and already moved money to your customer. You are not opening a case; you are answering one that's been open for days.
Now you respond. In network terms this is called representment — you are re-presenting the charge, arguing it was valid. Stripe packages your evidence and sends it back through the network to the issuer. And here is the quiet truth of the entire system: the issuer decides. The same bank that sided with your customer reviews your rebuttal and chooses whether to reverse its own provisional credit. The referee for this round is the institution with the least incentive to rule for you.
Why the issuer's analyst is your real reader
This changes how you should write. Your evidence is not read by Stripe, by a neutral arbiter, or by anyone who knows your business. It's read — often briefly — by an analyst at your customer's bank who has a queue of these and a reason code that already frames the story against you.
That person can't click your website. They won't watch a screen recording for two minutes. They're matching the contents of your submission against the requirements the network attaches to that specific reason code. If the code is "product not received," they're looking for proof of delivery or access. If it's "subscription canceled," they're looking for your cancellation terms and the date the customer agreed to them. Anything that doesn't speak to the code is noise that buries your one good point.
The networks have formalized this. Visa's dispute process and Mastercard's equivalent define what counts as compelling evidence for each category — prior undisputed transactions, matching device or IP data, delivery confirmation, signed agreements. You're not persuading a human with a narrative. You're satisfying a checklist a human is holding. Write to the checklist.
The decision isn't always final
If the issuer rules against you on representment, the game isn't necessarily over — and if it rules for you, your customer's bank can still push back. Beyond representment lies pre-arbitration and then arbitration, where the card network itself finally steps in to break the tie between the two banks.
Most merchants never go there, and usually shouldn't. Arbitration carries fees that can dwarf the original transaction, and losing means paying both the chargeback and the cost of the fight. The practical lesson isn't to escalate everything; it's that your representment is your best and cheapest shot. The further down this road a dispute travels, the more it costs everyone, which is exactly why the issuer's first read of your evidence matters so much. Get it right there.
Why the clock is so unforgiving
Every handoff in that chain has a deadline set by the network, not by Stripe and not by you. The cardholder has a window to dispute. The issuer has a window to file. And you have a window — short, and counted from when the dispute lands, not when you notice it — to submit representment. Stripe's interface often gives you around a week, and that compression is deliberate: the networks run this as a timed process so funds settle predictably.
Miss the window and there is no judge to appeal to, because the structure assumed your silence was a forfeit. A surprising share of lost chargebacks are never actually contested. The merchant didn't lose the argument; they lost the calendar. The dispute expired in an inbox during a launch week or a vacation, and the default ruling — for the cardholder — simply stood.
What this map changes about your next dispute
Once you see the four parties, your job clarifies. You are not pleading your case to a sympathetic platform. You are assembling a network-compliant evidence packet, matched to a reason code, addressed to a skeptical analyst at a bank that has already paid your customer, and delivered before a clock you didn't start runs out. Everything that wins follows from that sentence.
It also explains why merchants who "feel obviously right" still lose. Being right isn't a category the system evaluates. Submitting the right artifact, for the right code, in the right window, is.
Where Argeback fits
This is the part of the process that's easy to understand and hard to execute under deadline pressure. Argeback ingests the dispute the moment it arrives, reads the reason code, and drafts the representment as the issuer's analyst actually needs to read it — the matching evidence, framed to the checklist, assembled and filed before the network's window closes. It's built around the truth this article is about: you're not arguing with Stripe, you're answering a bank on a timer, and most lost chargebacks were simply never answered in time.
If you'd rather not let another winnable dispute expire in your inbox, you can see how it works at argeback.lumenlabs.works.