The real app refund time limit isn't 48 hours, it's the months your revenue stays reversible

Ask a developer how long a customer has to get a refund and most will say 48 hours. That is the number Google Play puts in front of buyers, and it is the one that sticks. It is also the smallest clock in the room. The real app refund time limit is not one window, it is a stack of them, and the tallest reaches months past the sale. Apple will take a refund request for up to 90 days. A bank can reverse a Google Play charge for up to 120 days after it clears. Until every one of those clocks runs out, the money in your payout is not final, it is reversible. Here is each clock, who controls it, and what the long tail costs you.

What the app refund time limit really is

There are two questions hiding inside app refund time limit, and mixing them up is where the trouble starts. One is how long a customer has to ask for their money back. The other is how long your money stays exposed to being taken back. The first is a short, friendly number the store advertises. The second is a much longer number the store does not put on a poster.

The 48-hour number everyone quotes

Google Play's self-service refund runs for 48 hours from purchase. Inside that window a customer taps a button and Google decides, with no developer involved. Google is blunt about the limits around it. In its own words, Google doesn't give refunds for most Google Play purchases, you can only return an app or game once, and issuing a refund removes the customer's access to the item. Apple has no equivalent self-service button at all. So the 48-hour figure people quote is a Google-only, self-service-only number, and it is the start of the story, not the whole of it.

The clocks that keep running after 48 hours

Once the self-service window closes, three longer clocks are still ticking. On Google Play the request routes to you, the developer, and you can refund an order for up to three years through the orders.refund API. On the App Store a customer can still file a request with Apple for up to 90 days from purchase. And underneath both stores sits the bank, which can reverse a card or PayPal charge for up to 120 days after it cleared. The table below lines them up.

Apple runs no self-service, just one long request window

Apple keeps every refund decision in-house. A customer does not get a self-service button, and they cannot come to you for a refund either, because you have no way to issue one. They go to Apple, and Apple rules.

A customer files, Apple decides

The path is always the same. A customer opens reportaproblem.apple.com, picks the purchase, and gives a reason. Apple reviews the request against its own signals and emails a decision, usually within 24 to 48 hours. Apple accepts these requests for up to 90 days from the purchase date, and eligibility can vary by country under the Apple Media Services Terms. You are not asked to approve anything. Your server learns the outcome only after the fact, as a REFUND, REFUND_DECLINED, or REFUND_REVERSED notification.

The one clock that is yours, 12 hours

There is exactly one moment Apple asks for your side, and it is short. When a refund is in question for an eligible purchase, Apple sends your server a CONSUMPTION_REQUEST and gives you 12 hours to answer through the Send Consumption Information endpoint. You send consumption data and a refundPreference. Apple treats it as one of several factors, not a verdict, and then decides. Miss the 12 hours and Apple decides with nothing from you. That window sits inside the customer's 90-day window, but it opens on Apple's schedule, not yours, so it has to be automated to be caught.

Google Play stacks three windows on top of each other

Google Play is where the layering is easiest to see, because each stage hands off to a different decider.

48 hours for the customer, then it comes to you

For the first 48 hours the customer self-serves and Google decides. After that, Google's guidance is to contact the developer, and the ball is in your court. You can issue a refund yourself through orders.refund on any order less than three years old, with or without revoking access. This is discretion, not obligation, but it is also the stage where a shaky order is cheapest to close, because a refund you issue returns the purchase price and nothing more.

The unauthorized-charge window runs to 120 days

Separate from the refund flow, Google runs a dispute channel for charges a customer does not recognize. Google states it can only act on credit, debit, or PayPal transactions within 120 days of the transaction, and on carrier billing within 60 days. A customer who spots your line item on a statement two months later still has a live path to reverse it. This is the quiet clock most revenue models ignore.

24 hours to defend a chargeback

When a customer goes past Google entirely and disputes the charge with their bank, Google sends a chargeback review and gives you 24 hours to respond through the orders.reviewrefund API. Like Apple's consumption reply, it is evidence, not a veto. It is also the single Android refund flow that asks for your input, the direct counterpart to Apple's CONSUMPTION_REQUEST.

The chargeback is the longest clock, and the store cannot close it

Every window above except the chargeback belongs to the store, and the store can be reasoned with. The chargeback belongs to the bank. A customer can skip the store entirely, call their card issuer, and start a dispute months after the purchase. Google's own 120-day figure for card and PayPal disputes is a good proxy for how long that tail runs, and card network rules can stretch it further in specific cases. A chargeback is final with the bank once it lands, which means the only real defense is the 24-hour evidence window before it settles, or issuing a refund yourself before the customer ever calls the bank.

What the long tail costs you

The length of the tail matters because a reversal is never just the sale price coming back out.

The money is already spent by the time the clock runs out

By the time a refund or chargeback lands, weeks or months on, you have long since delivered the purchase. The compute ran, the third-party API calls were billed, the storage was written, and any creator payout went out the door. That spend is gone and does not return with the reversal. The longer the window, the more of these costs you have stacked up before the money is pulled back.

• The sale price: your net proceeds after the store's commission, reversed when the refund or chargeback goes through.
• The delivery cost: compute, API calls, storage, and payouts you already spent serving the purchase. Gone regardless of the outcome.
• The chargeback fee: on Google Play, for orders placed on or after August 3, 2026, the bank's chargeback fee is now yours too.
• The blind spot: revenue you counted as final in one period, reversed in the next, so your numbers were never as solid as they looked.

The August 3 change makes the Google tail more expensive

Until recently a lost Google Play chargeback cost the developer the sale and little else. For orders placed on or after August 3, 2026, that changes. The developer absorbs the purchase price less Play's service fee, plus the bank's chargeback fee, while Google covers only its own service fee. Because chargeback fees are flat and product prices are not, on a cheap in-app purchase the fee alone can exceed what the customer paid. The 120-day chargeback window was always a risk. After August 3 it is a risk with a fee attached.

RefundHalt watches every one of these clocks so you do not have to. It catches Apple's CONSUMPTION_REQUEST inside the 12-hour window and Google Play's chargeback review inside the 24-hour window, assembles the consumption and delivery evidence, and answers on time without anyone on your team watching for a notification at 3am. It tracks the reversibility tail on your revenue, so a sale that reverses 90 or 120 days later is a number you saw coming, not a surprise in next quarter's payout. You cannot make a customer's refund window shorter. You can make sure none of it reverses without your side of the story.