The 7-Day Clock Inside the 30-Day Window

The acquirer's response window is a third of the network's.

The number quoted in most introductions to chargeback management is 30: thirty calendar days from the dispute processing date is, on Visa's books, the merchant's window to respond. For a working merchant on Stripe, Shopify Payments, Adyen, or Chase Paymentech that number is also almost completely irrelevant to operational practice. The deadline that matters is the one set by the acquirer, and it is a fraction of the network's.

Acquirers transmit dispute responses upstream through dedicated systems and need time to do so, which lands their internal deadlines well inside Visa's 30-day ceiling. Adyen has documented a 9-day window for US and Canadian merchants since 21 July 2025. Chase Paymentech runs day-24 cut-offs for Collaboration cases and day-18 for Allocation. Stripe, on the dispute categories most relevant to small online merchants, expects responses with at least a week of buffer in hand. The figure published by the card network is a ceiling, but the figure that determines whether the case is even submitted comes from the acquirer.

Almost no one misses the deadline because they decided the case was not worth fighting. The far more common failure is administrative: the notification arrives during a busy week, sits in a finance inbox that nobody reads daily, surfaces on day 5 when the team finally checks it, and reaches the expert who actually handles disputes on day 8, by which point the acquirer's window has closed and the case is forfeited without ever being argued on the merits.

A merchant who treats the 30-day rule as the operating window will lose disputes on procedural grounds even when the underlying case is strong. The working assumption is the inverse: the response is due by the end of the first week and the evidence has to be in hand before that, because the buffer between the acquirer's cut-off and the network's deadline exists for the acquirer and not the merchant. A response that misses the acquirer cut-off is not submitted to the network, because the acquirer is the channel and the channel has closed.

A dispute notification, when it arrives, should trigger an entry on whichever shared calendar the team actually watches, with the deadline set to the acquirer's internal cut-off rather than the network's. The order record gets pulled the same day; the decision to contest or refund is made by day 2 and the response drafted by day 4. None of this requires special tools or extra staff. The dispute clock has already started when the notification is sent, and a merchant who reads it on day 5 has already used a third of the working window.