Months after a sale, a chargeback can still claw the money back, and the chargeback time limit is longer than you think

A sale you closed months ago is not always closed. Long after the refund window has shut and the payout has cleared, a customer can call their bank, dispute the charge, and pull the money back out of your account. That reach has a name. It is the chargeback time limit, and it runs far longer than most developers plan for.

On the App Store and Google Play, a refund request lives on a short clock. Google Play's self-service refund runs for 48 hours. Apple reviews requests case by case, usually within a day or two. A bank chargeback is a different instrument on a different timeline. Under Visa and Mastercard rules a cardholder commonly has 120 days from the transaction to dispute it, and some cases stretch to 540. That gap is why a quiet month can still become a clawback next quarter.

Here is how long the window really stays open, what starts the clock, and what one late dispute now takes from you, because since August 3, 2026 Google Play bills the developer for it.

What a chargeback time limit is, and why it outlasts every refund window

A chargeback time limit is the deadline a cardholder has to dispute a charge with their card issuer. It is set by the card networks, Visa and Mastercard, not by Apple or Google. A refund is the store handing money back under its own policy. A chargeback is the customer's bank reaching into the payment and reversing it, whether the store agrees or not. The two look similar on a statement and behave nothing alike.

A refund and a chargeback run on two different clocks

A store refund is fast and short. On Google Play a buyer can self-serve a refund for 48 hours after purchase, once per app, and after that they have to ask the developer. On the App Store the customer files at reportaproblem.apple.com and Apple decides, usually returning an answer in a day or two. Both windows are measured in hours and days.

A chargeback is slow and long. The customer does not go to the store at all. They go to their bank, and the bank works to the card network's calendar, which is measured in months. This is the part that surprises people. The door you thought closed after the refund window is still open to the bank for a long time after.

How long a customer has to file a chargeback

The 120-day window is the common case

For most disputes, Visa and Mastercard give the cardholder about 120 days to file a chargeback. The clock usually starts on the transaction date, or on the expected delivery date when the customer paid for something they had not received yet. For a normal in-app purchase that delivers instantly, read it as 120 days from the sale.

Certain cases stretch to 540 days

The 120-day figure is the common case, not the ceiling. For some fraud claims and future-delivery purchases, the window extends up to 540 days from the original transaction. A subscription billed ahead or a pre-order that ships later can sit inside that longer window, which means a charge can be disputed well over a year after it cleared.

There is no single deadline you can bank on

The exact limit and its start date depend on the dispute reason code and how the issuing bank reads the case. A quoted network maximum is not a promise, and your payment flow never sees the reason code in advance. Treat 120 days as a planning floor, not a guarantee, and assume a legitimate dispute can arrive any time inside it.

What a late chargeback actually costs you

The timing matters because of what a chargeback moves, and since August 3, 2026 it moves real money out of your pocket on Google Play.

On Google Play, the bill is now yours

Google Play used to absorb chargeback losses. For orders placed on or after August 3, 2026, it does not. Google's own policy now puts the cost on the developer: the purchase price less Play's service fee, plus the chargeback fee the bank charges. Payment-industry sources put that bank fee somewhere around $15 to $25 per dispute. On a $19.99 sale, a lost chargeback in month four reverses the roughly $17 you were paid and adds the bank fee on top, so a sale you counted as clean revenue in the spring becomes a net loss in the summer.

On the App Store, Apple takes the dispute

On the App Store the math is different, because Apple is the merchant of record and handles card disputes itself. A chargeback on an App Store purchase is resolved between the bank and Apple, and Apple does not bill you the bank's fee the way Google now does. You can still lose the sale if the charge is reversed, but the extra cost of the dispute is not passed to you. This is one of the few places where the two stores are not converging.

The delivery cost is already spent either way

Whichever store the sale came through, the money you spent serving that customer does not come back with the chargeback. The compute you ran, the API calls you paid for, the storage you held, and any payout already booked are gone. A late chargeback is worse than an early refund for a plain reason. More of that delivery cost has already been spent by the time the dispute lands. You are not just reversing a payment, you are eating months of service you already paid to provide.

The one window where your evidence still counts

Once a bank rules for the cardholder, the chargeback is final. There is no appeal, no store override, no second look. Your only leverage comes before that ruling, and it is narrow.

On Google Play, a disputed charge opens a chargeback review. You get 24 hours to respond through the Review Refund flow, orders.reviewrefund, with delivery state, consumption status, and usage evidence, which Google uses to contest illegitimate chargebacks on your behalf. Miss the 24 hours and the case is decided without your side. On the App Store, your equivalent input is the consumption request. When a refund is requested on a consumable or an auto-renewable subscription, Apple gives your server 12 hours to answer through Send Consumption Information. Note the difference. The Apple window is for refund requests Apple decides, not for bank chargebacks, which Apple handles on its own.

How to keep a late dispute from being a surprise

You cannot shorten the chargeback time limit. You can stop it from catching you flat.

• Keep evidence well past the refund window. A dispute can arrive up to 120 days out, and longer in some cases, so hold delivery and usage records far beyond the point where a refund is still possible.
• Watch for the void. On Google Play a chargeback lands in your Voided Purchases feed and real-time developer notifications. Treat that signal as the moment to revoke access, not a report to read later.
• Answer the 24-hour Google review every time. It is the only pre-decision input you get, and it is the difference between contesting a bad dispute and absorbing it.
• Reconcile late, not just at sale time. A payout that looked clean can be reduced by a chargeback weeks or months after the fact, so match disputes back to the original orders instead of trusting the first number.

This is how RefundHalt reads the long tail of a sale. Chargeback reviews surface first with their 24-hour clocks, a void on a months-old order is matched back to the transaction it reverses, and disputes that arrive long after the refund window are recorded against the right sale instead of a mystery line in a later payout.

The short version

A refund window is short and store-run. A chargeback window is long and bank-run. Under Visa and Mastercard rules a customer commonly has 120 days from the purchase to dispute a charge, and certain fraud and future-delivery cases reach 540. The exact clock depends on the reason code, so plan for the floor, not the average. When a late dispute lands, the bank decides and the decision is final, and since August 3, 2026 Google Play bills you the purchase price less its service fee plus the bank's fee, while Apple still handles App Store disputes itself. Keep your records long, watch the void, and answer the 24-hour review, because the chargeback time limit outlasts every refund window you were watching.