Chargeback Time Limits: The Deadlines Merchants Can't Miss

Chargeback deadlines are unforgiving. Unlike most business paperwork, there is no grace period and no one to call for an extension, and a single missed date hands the cardholder a win regardless of how airtight your evidence is.

There are two separate clocks running in every chargeback, and confusing them costs merchants money. One controls how long a cardholder has to dispute a charge. The other controls how long you have to fight back. This guide breaks down both, network by network, and explains why the deadline in your processor’s dashboard is the only one you should be watching.

The two clocks: filing vs. response

When people say “chargeback time limit,” they usually mean one of two very different things:

• The cardholder filing window — how long after a transaction a customer can dispute it with their bank. This is measured in months (120 days is the common figure, up to 540 days for specific reasons).
• The merchant response window — how long you have to submit evidence once the chargeback is filed. This is measured in weeks (roughly 20 to 45 days).

You have no control over the filing window; it is set by the networks and the issuing bank. The response window is the one that determines whether you win or lose, because it is the one you can actually blow.

Cardholder filing windows by network

The card networks set the outer boundary for how late a cardholder can file. The clock does not always start at the purchase date. For fraud, it typically starts at the transaction date. For “goods or services not received,” it often starts at the expected delivery date or the date services were supposed to be provided, which is why a customer can sometimes dispute a months-old charge legitimately.

The 540-day cases are the ones that surprise merchants. If you sell event tickets, pre-orders, subscriptions, or anything delivered well after purchase, a cardholder can file long after you have mentally closed the books on that sale. Keep records accordingly.

For a deeper breakdown of how these windows map to specific dispute reasons, see our guide to chargeback reason codes.

Merchant response windows by network

This is the deadline that matters day to day. Once a chargeback is filed, you have a fixed window to respond with evidence (a process the networks call representment). Miss it and the dispute is automatically resolved against you.

These are network-level figures. Your actual deadline is almost always shorter, and here is why.

Why the processor deadline is the real one

The card network sets an outer limit, but your processor or acquirer sits between you and the network and needs time to package your evidence and transmit it before the network’s cutoff. So they impose their own internal deadline, which is earlier.

If Mastercard allows 45 days, your processor might give you 30 or fewer, because they need the remaining time to review and forward your submission. The date shown in your Stripe, PayPal, Braintree, or PayArc dashboard is the one that governs your case — not the theoretical network maximum you read in an article.

Treat the processor deadline as hard. Build your evidence to be submitted several days before it, not at the last minute, because uploads fail, evidence turns out to be incomplete, and time-zone cutoffs are rarely in your favor.

What happens if you miss the deadline

Missing a response deadline is the most avoidable loss in the entire chargeback process, and it is depressingly common. Here is what happens:

• The dispute is forfeited automatically. The funds are returned to the cardholder and stay there.
• There is no appeal. A missed deadline cannot be reopened by arguing your case was strong. The window closing is the decision.
• You still eat the fees. The chargeback fee and any ratio impact land regardless of the outcome, so a missed-deadline loss costs you the sale, the fee, and a mark against your chargeback ratio.

The one narrow exception is that some networks allow a later pre-arbitration stage after an initial representment, but you only reach that stage if you responded to the first dispute on time. Miss the first deadline and there is no later round to reach.

How to never miss a deadline

Deadlines get missed for boring, structural reasons: the notification landed in an inbox nobody watches, the person who handles disputes was on vacation, or the case sat in a queue until the window closed. The fixes are equally boring but effective:

1. Centralize dispute notifications. Every processor should route new-dispute alerts to a monitored channel, not a personal inbox.
2. Log the processor deadline the moment a dispute appears — not the network limit, the processor’s.
3. Work backward from the deadline. Set an internal target several days earlier to leave room for gathering evidence and handling upload problems.
4. Track every open dispute in one place so nothing sits forgotten in a per-processor dashboard you rarely open.
5. Gather evidence continuously, not reactively. The order data, tracking numbers, AVS/CVV results, and customer messages you need already exist at the moment of sale.

This is exactly the failure mode automation eliminates. DisputeDash detects a dispute the moment your processor reports it, pulls the reason-code-specific evidence automatically, builds the rebuttal, and submits it well before the deadline — so a case never dies in a queue because someone was out that week.

The bottom line

Two clocks, one that matters. The cardholder’s filing window (120 days, up to 540 for delayed delivery) is out of your hands. The merchant response window (roughly 20 to 45 days at the network level, shorter at your processor) is entirely within your control, and it is the one that decides your case. Watch the processor deadline, build your evidence early, and never let a dispute sit in a queue. For a fuller picture of how the whole timeline unfolds, read how long a chargeback takes.