BestPaid guides · Android · Google Play Billing

Play Billing Library 7 deadline passed: what to change when you move to version 8 or 9

Google Play's deadline for apps on Play Billing Library 7 ran out on November 1, 2026, the end of the extension period. If your app sells anything through Google Play and still ships version 6 or 7, the next release needs version 8 or later. Version 9 is the current release (9.0.0 came out on May 19, 2026, and 9.1.0 on June 18, 2026) and is accepted the longest, so it is the one to move to. Here is what PBL 8 and PBL 9 remove and what replaces it.

Which version do you ship? Our free APK and AAB checker reads the Play Billing Library version from your build in the browser, along with target API and 16 KB support.
Sources: Google's migration guide to PBL 9, its migration guide to PBL 8, the release notes, the deprecation FAQ and the integration guide. Checked on November 21, 2026. This page is our own summary; follow Google's documentation for every detail.

The deadlines

The deadlines apply to new apps and updates. Google says existing apps keep working.

1. Update the dependency

dependencies {
    implementation "com.android.billingclient:billing:9.1.0"
}

Use the latest release. Since 8.1.0 the library needs minSdkVersion 23 (version 7 needed 21), so if your app's minSdkVersion is lower, raise it to 23 first. Google's integration guide and its PBL 9 migration guide (for apps on version 7 or 8) use 9.1.0; the older PBL 8 migration guide shows 8.0.0. If you use the Kotlin extensions, move billing-ktx to the same version. Flutter, React Native, Unity and .NET MAUI apps get the library through their in-app purchase plug-in: update the plug-in to a release built on PBL 8 or later and read its changelog, because the plug-in's own API may change too. If Play Console still shows a deprecation warning after the update, Google says to check that your AndroidManifest.xml contains com.google.android.play.billingclient.version and that manifest merging doesn't remove it.

2. Replace the APIs that PBL 8 removed

Coming from version 6 or 7, you need these changes whether you stop at version 8 or go on to 9.

Removed in PBL 8Use instead
querySkuDetailsAsyncqueryProductDetailsAsync and ProductDetails (the SkuDetails class itself is removed in PBL 9, so move to ProductDetails now)
queryPurchaseHistoryAsyncGoogle's "Query purchase history" guidance (the history method is gone from the library). If you used it to check free-trial eligibility, Google points to ProductDetails.getSubscriptionOfferDetails()
enablePendingPurchases() without parametersenablePendingPurchases(PendingPurchasesParams.newBuilder().enableOneTimeProducts().build()), which Google says is the same behaviour
queryPurchasesAsync(String skuType, listener)queryPurchasesAsync(QueryPurchasesParams, listener)
Coming from version 6: already removed in PBL 7Use instead
enableAlternativeBilling, AlternativeBillingListener, AlternativeChoiceDetailsenableUserChoiceBilling, UserChoiceBillingListener, UserChoiceDetails
setOldSkuPurchaseToken, setReplaceProrationMode, setReplaceSkusProrationModesetOldPurchaseToken and setSubscriptionReplacementMode. Google's 8.1.0 release notes say to use SubscriptionProductReplacementParams.setReplacementMode instead of setSubscriptionReplacementMode

3. Replace the APIs that PBL 9 removes

Skip this step if you stop at version 8. Google's PBL 9 migration guide lists these as removed when you come from version 8; coming from version 7, you also need everything in the first part of the table above.

Removed in PBL 9Use instead
SkuDetailsProductDetails
SkuDetailsParamsQueryProductDetailsParams with queryProductDetailsAsync
SkuDetailsResponseListenerProductDetailsResponseListener with queryProductDetailsAsync
BillingClient.SkuTypeBillingClient.ProductType; Google says its INAPP and SUBS constants remain functionally similar to the old ones
getSkuDetailsList and setSkuDetailsListBillingFlowParams.Builder.setProductDetailsParamsList
QueryPurchaseHistoryParamsqueryPurchasesAsync for active and pending purchases, your own backend for consumed purchases, and the server-side Voided Purchases API for canceled or voided ones

PBL 9 also changes two behaviours. When the system blocks the Play Store app (for example, in an OEM-customized kids mode), the response code is now BILLING_UNAVAILABLE instead of ERROR; Google notes this needs AndroidX core 1.9 or later. And if you use external payments, DeveloperProvidedBillingDetails.getLinkUri() can now return null, so handle both null and empty values.

4. Update the product details callback

Coming from version 6 or 7: the signature of ProductDetailsResponseListener.onProductDetailsResponse changed in PBL 8, so every queryProductDetailsAsync call site needs an update. Google's "Show products available to buy" section has the new shape. Plan for products that come back unfetched instead of assuming the list matches your request.

5. Turn on automatic reconnection

Google recommends enabling automatic service reconnection with enableAutoServiceReconnection() on BillingClient.Builder (added in 8.0.0): the library then tries to reconnect by itself when an API call is made while the billing service is disconnected. Google says this can reduce SERVICE_DISCONNECTED responses, because the library reconnects before it makes the call. With it on, don't call startConnection() yourself in onBillingServiceDisconnected(); Google still tells you to keep the BillingClient connected when you call its methods.

6. Test the purchase flows end to end

The same release usually has to meet the other current Google Play rules too: target API 36 and, from February 1, 2027, 16 KB page support. See our target API 36 and 16 KB checklist.

Can't release because of billing, target API or 16 KB? We update native, Unity, Flutter, React Native and Xamarin apps to the current Google Play and App Store rules at a fixed price. You keep your signing keys. It starts with a $290 check and a fixed quote within 2 business days.
See the app update offer