All articles
Deep dive7 min read

Play Billing Library 8 is now required for every Google Play update, and it moves refund tracking onto your server

Google's extension for Play Billing Library 7 ran out on November 1, 2026, so new apps and updates need version 8 or later. Version 8 removed queryPurchaseHistory(), which means refunded and consumed purchases have to be tracked server-side. Here's what changed and what a slow migration costs.

An Android developer's desk in morning light with a laptop, a phone and a wall calendar with a date circled, the week Play Billing Library 8 became the minimum for Google Play updates

Key takeaways

  • Google's deprecation table set August 31, 2026 as the last day for new apps and updates on Play Billing Library 7, with extensions ending November 1, 2026, so any Google Play update now needs Play Billing Library 8 or later.
  • Apps already live on Play Billing Library 7 keep working, because Google says the deprecation only blocks new apps and updates, not existing installs.
  • Play Billing Library 8 removed queryPurchaseHistory(), and Google's replacement plan is server-side: track consumed purchases on your own backend and fetch refunded or cancelled ones from the Voided Purchases API.
  • The Google Play Voided Purchases API only shows voided purchases from the past 30 days and allows 6,000 queries per day and 30 queries in any 30-second period per app.
  • Google Play still refunds a purchase automatically and revokes the entitlement if the app doesn't acknowledge it within three days, and a broken Play Billing Library 8 migration can trigger that for every sale.
  • Google Play's chargeback review is the one Android refund flow that asks the developer for evidence, through orders.reviewrefund within 24 hours of the PendingRefundReviewNotification.
  • For Google Play orders placed after August 3, 2026, the developer pays the purchase price, less Play's service fee, plus the bank's chargeback fees on every lost chargeback.

Every Android app that sells through Google Play now has to ship Play Billing Library 8 or later with its next update. Version 7's deadline for new apps and updates was August 31, 2026, and the last extensions ran out on November 1, 2026. The dates sit in a table on Google's deprecation FAQ, and the reminders arrive as warnings on the Play Console Policy status page.

For most teams it's a dependency bump and a few renamed methods. For refunds, it's more than that. Play Billing Library 8 deleted the one client call that let an app look back at past purchases. From here on, if you want to know what a user bought, consumed or got refunded, your server has to remember it.

What the Play Billing Library 8 deadline actually blocks

Google gives each library version a two-year life. The deprecation only stops new apps and updates. Google's FAQ says existing apps still work and unmaintained APKs don't need updates. So nothing breaks today for an app you've stopped touching. It breaks the day you try to ship a fix, a new price or a new paywall.

Library versionNew apps and updates deadlineExtension deadline
6August 31, 2025November 1, 2025
7August 31, 2026November 1, 2026
8August 31, 2027November 1, 2027
9August 31, 2028November 1, 2028

Version 8.0.0 shipped on June 30, 2025. Version 9.0.0 followed on May 19, 2026. If you're migrating now, going straight to 9 buys you a year more than stopping at 8.

Why Play Billing Library 8 matters for refunds

The headline removal is queryPurchaseHistory(). It was deprecated in version 7 and removed in version 8.0.0. Google's migration notes split its old job into three pieces, and only one of them stays on the device.

What you used queryPurchaseHistory() forWhat Google says to use nowWhere it runs
Active and pending purchasesqueryPurchasesAsync()On the device
Consumed one-time purchasesYour own recordsYour server
Refunded, cancelled or charged-back purchasesVoided Purchases APIYour server
A user's full purchase historyYour own recordsYour server

Can I still restore consumable purchases on Android?

Not from the client. queryPurchasesAsync() returns what's active, so a consumed credit pack or a used-up gem bundle never comes back through it. If a user reinstalls and asks where their coins went, the answer has to come from the ledger you kept when the purchase happened. Apps that leaned on purchase history as a free backup have lost it.

How do I find out about refunds now?

Two server-side channels. Real-time developer notifications send a VoidedPurchaseNotification with the purchase token, the order ID, the product type and a refund type that's either a full refund or a quantity-based partial refund. The Voided Purchases API lets you pull the same events by time range, as a backstop for anything you missed.

The pull API has hard edges. It only shows voided purchases from the past 30 days. Each app gets 6,000 queries a day and 30 queries in any 30-second period. And a developer refund made without the revoke option isn't returned at all. A server that's down for five weeks loses refunds it can never pull back.

An engineer with a tablet in a quiet server aisle, where refunded and consumed Google Play purchases now have to be recorded after Play Billing Library 8 removed client-side purchase history

Which refunds the developer still gets a say in

Moving refund tracking to the server doesn't give you more control over refunds. Almost every Google Play refund is decided without you: self-service refunds, support refunds, cancellations and automatic refunds on unacknowledged purchases. You learn about them after the fact, through the voided purchase notification.

The exception is the chargeback review. When a buyer files a chargeback that needs your input, Google sends a PendingRefundReviewNotification. Google says you should answer with a refund suggestion and usage evidence within 24 hours by calling orders.reviewrefund. That evidence comes from the same server records the new library forces you to keep. A team that keeps a ledger for restores already has what it needs to answer.

What a slow migration costs in money

The direct risk is the three-day rule. Google Play refunds a purchase automatically and revokes the entitlement if your app doesn't acknowledge it within three days. For pending purchases, the clock starts when the purchase moves from PENDING to PURCHASED. A migration that breaks the connection logic, the new queryProductDetailsAsync() listener or the pending purchase setup can stop acknowledgements without stopping sales. Every order in that gap is refunded in full, and the user already got what they paid for.

That's where it hurts. A refunded image credit pack still burned the GPU time behind each generation. A refunded AI plan still ran the paid API calls. A refunded storage tier still filled the disks you pay for. A refunded tip still went out in a creator payout. The refund returns the revenue to the buyer and leaves those bills with you.

Chargebacks got more expensive too. Google's help center says that for orders placed after August 3, 2026, the developer covers the purchase price, less Play's service fee, plus the chargeback fees from the bank. Google keeps paying only its own service fee. An app that can't answer a chargeback review in 24 hours with real usage data pays that whole bill each time.

A migration checklist that protects revenue

  • Bump the dependency to Play Billing Library 8 or 9 and remove queryPurchaseHistory(), querySkuDetailsAsync() and the no-argument enablePendingPurchases().
  • Update your queryProductDetailsAsync() listener. Since version 8 it also returns products that couldn't be fetched, with a status code.
  • Turn on enableAutoServiceReconnection() so a dropped billing connection doesn't stall purchase processing.
  • Call queryPurchasesAsync() in onResume() so purchases that complete while the app is closed still get acknowledged inside three days.
  • Log every purchase token, order ID and consumption on your server, tied to your own account ID.
  • Subscribe to real-time developer notifications and handle both VoidedPurchaseNotification and PendingRefundReviewNotification.
  • Run a daily Voided Purchases API sync as a safety net, well inside the 30-day window and the 6,000-query daily quota.

RefundHalt listens for Google Play's voided purchase and chargeback review notifications, answers each review through orders.reviewrefund inside the 24-hour window with your real usage data, and keeps the refund history your app can no longer ask the device for.

Frequently asked questions

Do I have to use Play Billing Library 8 now?
Yes, for any new app or update that sells through Google Play billing. Google's deprecation table set August 31, 2026 as the deadline for version 7, and extensions ended November 1, 2026. You can use version 8 or the newer version 9.
Will my existing app stop working if it still uses Play Billing Library 7?
No. Google says existing apps still work and unmaintained APKs don't need updates. The deprecation only blocks you from publishing a new app or an update that uses an unsupported version.
What replaced queryPurchaseHistoryAsync in Play Billing Library 8?
Nothing on the device does the same job. Google says to use queryPurchasesAsync() for active and pending purchases, keep track of consumed purchases on your own server, and use the Voided Purchases API for cancelled or refunded purchases.
How far back does the Google Play Voided Purchases API go?
30 days. Google says the API can only show voided purchases that happened during the past 30 days, and it limits each app to 6,000 queries per day and 30 queries in any 30-second period.
Does Google Play refund a purchase if my app doesn't acknowledge it?
Yes. If a purchase isn't acknowledged within three days, the user automatically gets a refund and Google Play revokes the purchase. For pending purchases, the three days start when the state changes from PENDING to PURCHASED.

Sources and further reading

RefundHalt

The refund autopilot for the App Store and Google Play

Keep reading

The next refund request is already on its way.

Set up RefundHalt in the time it takes to read another support email about a refund you didn't get to contest.