Every App Store and Google Play refund window is a countdown, and here's how many hours each one gives you

Every App Store and Google Play refund starts a clock somewhere, and most of those clocks run without you. A refund window is just the time a deadline gives you to act before the store decides on its own. The shortest one Apple runs is 12 hours. The shortest one that costs you real money is 24. Miss either and the refund is usually granted by default, and on Google Play from August 3, 2026, a missed chargeback window can now cost you the purchase price and the bank's fee on top. Here is every refund window that touches your account, how long each one gives you, and what it costs when it closes.

The two windows that actually ask for your evidence

Out of every refund flow on either store, only two ever pause to ask what you know. Both are short, both are easy to sleep through, and both hand the decision to the store the moment they close. If you build refund handling around anything, build it around these.

Apple gives you 12 hours to send consumption information

When a customer requests a refund on a consumable or certain non-renewing purchases, Apple sends your server a CONSUMPTION_REQUEST through App Store Server Notifications V2. From that moment you have 12 hours to reply through the Send Consumption Information endpoint with the signals Apple asks for. Answer in time and your data feeds the decision. Stay silent and, as Apple's own tooling partners put it plainly, Apple often grants the refund by default. The clock does not care that the notification arrived at 3 a.m. your time.

Google Play gives you 24 hours to review a chargeback

When a buyer disputes a charge with their bank, Google Play can ask you to weigh in before it fights the chargeback. Google's guidance is exact: evaluate the request and respond within 24 hours of the notification by calling orders.reviewrefund. There is one more catch in the mechanics. Google records your first API call in response to a notification and ignores subsequent calls, while still returning an OK status. You do not get a draft and a revision. Your first answer is your only answer.

The windows that close without ever asking you

The rest of the refund clocks are not invitations. They run on their own, and by the time you can see them the outcome is already fixed. Knowing them matters anyway, because each one still moves money out of your account.

The 48-hour self-service refund

On Google Play a buyer can refund most app and in-app purchases themselves, straight from the store, within 48 hours of buying. The fastest cases clear in about 2 hours. Google grants these automatically, and in most of them the developer is never contacted at all. There is no window here for you to contest, because the window was never yours. It is the buyer's.

The 3-day acknowledgment deadline

This one is easy to forget because it looks like an engineering detail, not a refund. If you use Google Play Billing and do not acknowledge a purchase within 3 days, Google refunds the buyer and revokes the purchase for you. A shipped feature you forgot to acknowledge on the backend becomes an automatic refund on day four. The clock runs on your server's behavior, which means a quiet bug in your acknowledgment path is quietly handing money back.

The 30-day voided purchases window

When a purchase is refunded or revoked, the Voided Purchases API is how your backend learns about it after the fact. That list has a memory of 30 days. Its startTime cannot be set to a value older than 30 days ago, and records are filtered by when Google saw the purchase as voided, not by when it was bought. If your server stops polling for a month, the refunds from that gap fall off the end and you never learn they happened.

The one clock you control, and it runs for three years

There is exactly one refund window you own end to end. Using orders.refund, you can refund a Google Play order yourself, on your own schedule, for 3 years after the purchase. Google will not ask why. After the third year the order is permanently out of reach, so even the clock you control has a hard stop. This is the window to reach for when you already expect to lose an order, because a refund you issue is cheaper than a chargeback you lose, a point the next section puts in numbers.

What a missed window costs in money

A refund is never just the sale price coming back out. By the time one lands, you have usually already spent money serving that purchase. The GPU minutes behind a generated image, the model API calls, the storage for what the user saved, the payout you sent a creator: that spend is gone and does not return with the refund. The window is what decides whether you also lose the sale price on top, and whether a bank fee rides along with it.

The 24-hour chargeback window is the one where the number changed. Google Play's help documentation is direct about the new split: for orders placed on or after August 3, 2026, when a chargeback goes through, the developer covers the purchase price less Play's service fee, plus the associated chargeback fees from the financial institution, while Google keeps covering only its own service fee. Before that date the loss was the sale. After it, a chargeback you did not contest is the sale plus the bank's fee.

Every refund window on one screen

Six clocks, three you can act inside, three that act on you. Kept in one place, they are easy to hold in your head, and the pattern is clear: the windows that give you a say are measured in hours, and the ones measured in days have already decided.

How to make sure you never miss the two that matter

You cannot win the windows that were never yours, so spend your effort on the two that are. Both come to you as a notification, and both punish a slow reply, so the whole game is turning a notification into an automatic response before a human is even awake.

Catch the CONSUMPTION_REQUEST within 12 hours

• Subscribe to App Store Server Notifications V2 and treat CONSUMPTION_REQUEST as urgent, not as another event in the queue.
• Have the consumption signals Apple asks for ready to assemble on demand, so replying is a lookup, not a research project.
• Answer through Send Consumption Information well inside the 12 hours, and log the response, because a silent miss is indistinguishable from a granted refund later.

Catch the chargeback within 24 hours

• Listen for the chargeback notification and route it somewhere a response can fire day or night, since the 24 hours run on the clock, not on your office hours.
• Call orders.reviewrefund once, with your refund preference and any purchase-usage evidence, and get it right the first time, because Google keeps only your first call.
• Record that you responded, so a lost chargeback later is a decision you can review, not a mystery.

The stores will keep running these clocks whether or not you are watching. The only choice you get is whether the two windows that ask for your side find an answer waiting, or find silence and decide without you.