The question every merchant asks at the wrong moment
The email arrives on a Tuesday afternoon: a customer has disputed a charge. Somewhere between the small jolt of irritation and the urge to open Stripe and figure out what happened, almost every merchant asks the same thing — how long is this going to take?
It feels like one question. It's actually three, and they run on very different clocks. There's the clock the bank started months ago, the clock you have to beat this week, and the clock that decides when money actually moves. Most of the stress around chargebacks comes from confusing the slow clocks with the fast one. Understand which is which, and the whole process stops feeling like a black box.
The long clock: how a dispute even reached you
By the time a chargeback lands in your inbox, it has already been traveling for a while. The cardholder noticed something on their statement — a charge they didn't recognize, a product that never arrived, a subscription they thought they'd canceled — and called their bank. The card networks give cardholders a generous window to do this. Under Visa and Mastercard rules, a customer can typically open a dispute up to 120 days from the transaction (or, for undelivered goods, from the date delivery was expected).
That's why a chargeback can feel like it comes out of nowhere. The sale closed in February; the dispute surfaces in May. Nothing went wrong on your end in the meantime — the cardholder simply had months of runway, and they used some of it. This long clock is entirely outside your control, and there's no point resenting it. It's the cost of a payment system built to make customers feel safe enough to type their card number into a stranger's checkout.
The fast clock: the one that actually decides the outcome
Here is the part that matters, and the part merchants routinely get wrong. The moment a dispute reaches you, a much shorter timer starts — your window to submit evidence, called representment. The card networks allow the issuing bank a set period to respond, but Stripe sets its own, earlier deadline so it has time to package your evidence and pass it along before the network cutoff. In your dashboard, that due date is printed plainly on the dispute. It is often far tighter than people expect — a matter of days, not weeks.
This is the only clock you have any power over, which is exactly why it deserves your attention and rarely gets it. There's a well-documented quirk of human behavior here: present bias, our tendency to weigh the discomfort of doing something now far more heavily than a consequence that lands later. Writing a rebuttal is annoying today; losing the money is abstract and weeks away. So the dispute gets a mental bookmark — I'll deal with it this weekend — and the weekend fills up. Parkinson's law does the rest: the task quietly expands to fill whatever time you give it, until there's no time left.
And missing this deadline isn't a partial loss. If you submit nothing, the dispute resolves against you by default — not because your case was weak, but because no one made it. A merchant who would have won on the evidence loses for the most preventable reason there is: the clock ran out while the response sat in the someday pile.
The patient clock: waiting for the verdict
Once you submit your evidence, the process slows down dramatically, and this is where the second wave of anxiety hits. You've done your part. Now nothing seems to happen.
That silence is normal. The issuing bank reviews your representment on its own schedule, and card network rules give it a substantial window to decide — commonly several weeks, and the full arc from dispute to final ruling can stretch across two to three months. There's no progress bar. The status in your dashboard sits at under review for what feels like an unreasonable length of time, and then one day it simply flips to won or lost.
It helps to reframe this stretch. The waiting isn't a sign that something is wrong or that you've been forgotten; it's just the speed at which banks move when there's no deadline pressing on them. Your job ended when you submitted strong evidence on time. The verdict is now a matter of patience, not effort.
When the verdict isn't final
Winning the representment usually ends things. But a determined issuer can escalate to pre-arbitration, and from there to arbitration, where the card network itself makes the final call. This is rarer, and it raises the stakes — arbitration carries fees that can exceed the disputed amount, so it's a path nobody walks lightly. For most merchants, most of the time, the story ends at representment. It's worth knowing the later stages exist, mostly so you're not blindsided if a dispute you thought was settled comes back for a second round.
What the timeline is really telling you
Line the three clocks up and a clear lesson falls out. The long clock and the patient clock — the months before the dispute arrives, the weeks after you respond — are entirely out of your hands. You can't speed them up, and worrying about them is wasted energy. The only stretch of this entire timeline you control is the fast clock: the few days between the alert landing and the evidence being due.
That's a strangely liberating thing to realize. The outcome of a chargeback isn't decided over the three-month sprawl it appears to occupy. It's decided in a narrow window early on, by whether anyone actually responded — and responded well — before the deadline. Everything else is just waiting.
Which means the practical question was never really how long does a chargeback take. It's will I still remember to act inside the one window that counts? The honest answer, for a busy merchant juggling a hundred other things, is often no — not out of laziness, but because the alert arrives mid-task and the deadline is quiet and the weekend is full.
Closing the gap between the alert and the deadline
That gap — between knowing a dispute exists and actually filing a response before the timer expires — is the entire problem Argeback was built to close. It ingests your Stripe disputes the moment they land, drafts an evidence-backed response from your transaction records, and files it well before the deadline, all from your phone. The fast clock stops being something you have to remember to beat and becomes something that's simply handled while you get on with running your business.
If the part of the chargeback timeline that keeps slipping past you is the only part that matters, it might be worth letting something else watch that clock. You can see how it works at argeback.lumenlabs.works.