MOBILE June 9, 2026 · 4 min read

Play Billing Library 9 Is Out — August 31 Deadline for v7 Devs, Plus the Churn-Recovery Features Worth Enabling

Google Play Billing Library 9 shipped on May 19 with in-app price-increase messaging and reduced involuntary churn. More urgently: v7 support ends August 31 — any app update submitted after that date must run v8 or higher. Here's the migration path and which opt-in features to enable now.

By the AppsOps news desk · June 9, 2026 · Original source ↗

Google shipped Play Billing Library 9.0.0 on May 19, bringing a handful of subscription improvements that automatically reduce involuntary churn. The more pressing story is the countdown on v7: any new app submission or update pushed after August 31, 2026 must use Billing Library v8 or higher — or face rejection at the gate. With roughly 12 weeks to go, now is the time to audit your integration.

The August 31 Deadline — v7 Support Ends

Google follows a two-year deprecation cycle for Play Billing Library versions. v7, released in 2024, hits its end-of-support wall on August 31. After that date:

Existing v7 binaries already live on the Play Store continue to function — Google does not break running apps mid-cycle.
New releases and updates built against v7 will be rejected at submission.
There is no direct jump from v7 to v9. You must complete the v8 migration first, then optionally move to v9.

If your team ships updates regularly — bug fixes, seasonal screenshots, ASO metadata refreshes — you need the billing migration landed before the deadline or you'll be blocked from submitting anything at all.

What's New in v9 — and What Landed in v8 Worth Enabling

v9 is a smaller release; the biggest churn-reduction wins actually shipped in v8. Both are worth reviewing if you haven't checked your settings in Play Console lately.

In-app price-increase confirmation (new in v9)

Previously, when a subscription price changed, users were redirected to Play Store settings to confirm. v9's updated showInAppMessages API can surface the confirmation dialog inside your app instead, appearing at most once every seven days. Removing that redirect step should meaningfully improve acceptance rates — similar to the uplift iOS developers see when using StoreKit's native upgrade prompts over a web-based flow.

Extended payment recovery window (v8)

Google expanded failed-payment retry periods from 30 to 60 days. According to figures presented at Google I/O 2026, this change contributed up to an 18% reduction in involuntary churn for apps that opted in. If you're on v8 but haven't verified extended recovery is configured, check Play Console → Subscriptions → Recovery settings.

Flexible subscription flows (v8)

Users can now change or downgrade their plan mid-cancellation rather than churning outright. For apps with multiple tiers this is a quiet win: it hands price-sensitive users an off-ramp that keeps them inside the ecosystem. No UI changes required on your side.

Delayed charging (v8)

For users Google classifies as low-risk, billing can be deferred while the subscription activates immediately. Friction drops at the start of the relationship; Google retries in the background. Opt-in, no additional UI required.

Migration Checklist

Find your current version. Open build.gradle and look for com.android.billingclient:billing. v7.x means migration is urgent.
v7 → v8 first — budget a sprint. v8 introduces updated purchase-flow APIs and revised acknowledgement logic. It's the heavier half of the work.
v8 → v9 is light. The RevenueCat engineering team called the jump "small enough to fit into a single sprint" — mostly opt-in changes. The one required fix: add a null-check on DeveloperProvidedBillingDetails.getLinkUri(), which is now nullable.
Enable in-app price-increase messaging once on v9.
Verify extended recovery is on in Play Console Subscriptions settings.

If your Android app serves users in growth markets — lower banking penetration, more prepaid cards, higher failed-payment rates — the extended recovery window and delayed charging are especially high-ROI changes. We've covered how churn patterns in PPP-priced markets differ from tier-1 markets in subscription churn in low-PPP markets. The same users who benefit from localized pricing are the most susceptible to payment failures, making these billing upgrades doubly relevant.

For teams thinking about the downstream impact of subscription price changes across 40+ currency territories — particularly when you push a price update that will now trigger v9's in-app confirmation flow — the PPP pricing tool can help you model which markets will see the dialog and what the new price anchors look like locally before you hit publish.