Play Billing Library 9.0: What Changed and What to Migrate
Play Billing Library 9.0.0 landed on May 19, 2026. If you already completed the v8 migration, the v9 surface is deliberately small: one new in-app messaging category, two compatibility adjustments, and a target SDK bump. This guide separates the changes that require code work from those that only matter if you use a specific feature, and it shows how the v9 step fits into the wider v7 sunset.
The short version
Four code-level changes define v9. The main addition is in-app messaging for opt-in price increases. The other three are a reclassification of the blocked-Play-Store error, a nullability change on developer-provided billing links, and a targetSdkVersion bump to 35. Sub-response codes introduced in v8, such as PAYMENT_DECLINED_DUE_TO_INSUFFICIENT_FUNDS and USER_INELIGIBLE, carry forward unchanged.
If you are already on v8, the only forced change is the target SDK bump. The other three are conditional: adopt the price-increase messaging if you have planned increases, touch the error handling if you already branch on BILLING_UNAVAILABLE, and add a null check only if you use developer-provided billing.
Migration decision table
Use this table to decide what your next sprint needs to include.
- Mandatory for every app on v9: bump targetSdkVersion to 35 if you build against an older target and consume the library directly. Expect manifest merger warnings until you match.
- Conditional — planned price increases: add InAppMessageCategoryId.TRANSACTIONAL to showInAppMessages so users can accept the new price inside your app.
- Conditional — existing BILLING_UNAVAILABLE handling: add a branch that checks the debug message for "Play Store is blocked" and shows a specific fallback.
- Conditional — developer-provided billing: handle both null and empty string from getLinkUri before launching a browser intent.
- No action: sub-response codes, the v8 API removals, and the user-choice-billing rename are unchanged in v9.
In-app messaging for opt-in price increases
Before v9, showInAppMessages with InAppMessageCategoryId.TRANSACTIONAL was used for payment recovery prompts during grace period or account hold. v9 extends the same surface to an outstanding opt-in price increase, so the user can confirm the new price without leaving your app.
You call the same method you would for payment recovery. The SUBSCRIPTION_STATUS_UPDATED response covers both outcomes: payment recovery and price increase acceptance. The purchase token in the result identifies which subscription changed, and a refresh from your backend tells you the new state.
The two message types have different frequency caps. The price increase message shows at most once every 7 days, starting the first day the user can accept the new price. The payment issue message during grace period and account hold shows at most once per day. Calling showInAppMessages on every app launch is safe; the library returns NO_ACTION_NEEDED when there is nothing to show.
Why this matters: accepting a new price used to require a detour to the Play Store subscription settings screen, and many users never completed it, so their subscriptions lapsed at the first renewal under the new price. Showing the confirmation inside your app removes that detour and should improve acceptance. If a price increase is already scheduled, this is the v9 change to prioritize.
Blocked Play Store now returns BILLING_UNAVAILABLE
Sometimes the system disables the Play Store app itself: OEM-customized kids modes, managed devices with parental controls, and enterprise devices whose policies turn the store off. Under v8 and earlier, billing calls in that state came back as a BillingResult with response code ERROR and no specific debug message. v9 moves these cases to BILLING_UNAVAILABLE and adds a "Play Store is blocked" debug message.
The migration step is a one-liner in your error handling: when the response code is BILLING_UNAVAILABLE, check whether the debug message contains "Play Store is blocked" and show a specific fallback; otherwise show the generic billing-unavailable fallback. Catching this state needs androidx.core 1.9 or newer, which most current apps already receive as a transitive dependency. For apps that ship to kids tablets or enterprise-managed fleets, the new classification lets you explain the situation in plain terms instead of falling back to a vague billing failure, so users do not hit a dead end at the paywall.
DeveloperProvidedBillingDetails.getLinkUri is now nullable
The return type of DeveloperProvidedBillingDetails.getLinkUri() is now @Nullable instead of non-null. The external-payment link URI is not guaranteed to exist when the user reaches the payment selection step; in some flows it only becomes available further along. Because the old signature promised a non-null value, the library had to hand back an empty string in those situations, and any app that passed that empty string to Uri.parse crashed.
The migration step is to handle both null and empty string before launching a browser intent. Apps that never touch developer-provided billing can skip this change entirely. For apps that do use it, the work is one nullness check plus a fallback branch.
targetSdkVersion bumped to 35
Version 9 compiles against API 35 (Android 15). Apps that consume the billing library directly and still build against an older compile or target SDK can expect manifest merger warnings until their own targetSdkVersion is raised to match. The minimum supported level stays at minSdk 23, the same floor v8.1 set, so nothing changes on the lower bound — only the target moves.
Billing changes aimed at involuntary churn
Involuntary churn is the loss that happens when a renewal payment fails and the subscription lapses before the user can correct it. Three I/O 2026 billing changes are designed to shrink that loss.
Delayed charging comes first. If a renewal payment fails and Google's risk model rates the user as low risk, Play keeps retrying the charge in the background while the user retains access. No payment-failure dialog appears, the entitlement stays intact, and a successful retry settles everything quietly. From the app's perspective the purchase remains in the PURCHASED state during the retry window. If the final retry fails, the standard grace period and account hold flow takes over. The risk model gates this behavior because granting access on a failed payment carries fraud risk, so the feature applies only when the model is confident the user is genuinely going to pay.
Second, the account recovery window doubles. Account hold is the state a subscription enters when grace period runs out without a successful payment; it used to last 30 days, and I/O 2026 extends it to 60 days. Google's published figures from the extension test are an 18% reduction in involuntary churn and a 9% reduction in total churn for top developers, so smaller apps should expect more modest effects. The longer recovery window costs nothing on the developer side: the subscription state is identical, the same RTDN notifications fire, and recovery surfaces through the existing SUBSCRIPTION_RESTARTED event the same way it did at 30 days.
Third, subscription management gains flexibility. A new in-app subscription management API lets you surface plan changes and downgrade offers right when the user is cancelling, so they no longer have to be sent out to the Play Store subscription settings screen. Downgrade credits are prorated through replacement modes on the existing subscription update flow, which means someone moving from annual to monthly gets the correct credit without manual handling.
The three changes compound. If your subscription business sees 5% involuntary churn per month and you adopt the extended recovery window, even a fraction of the published 18% reduction takes that to roughly 4.1%. Over a year, that translates into a larger active subscriber base for the same gross adds.
What v9 means for the v7 sunset
Google's Play Billing Library deprecation page shows the August 31, 2026 deadline for new apps and updates built against v7. v7 binaries already published continue to function, but no new release built against v7 can be uploaded after that date. v9 does not change this calculation. If you are still on v7, the migration is cumulative: the v7-to-v8 work is the bulk of the effort, and the additional v9 step is the four changes covered above plus adopting the in-app messaging extension for price increases.
For teams already on v8, the v9 jump is small enough to fit into a single sprint. The new in-app messaging category is opt-in, the error code reclassification only requires touching code that already handles BILLING_UNAVAILABLE, and the nullability change only affects developer-provided billing integrations. The targetSdkVersion bump is the only forced change, and it is one line.
Wider Play updates from I/O 2026
Beyond the billing library, Google announced several Play changes that affect discovery and operations.
Discovery is moving into Gemini. Over 450,000 movies and TV shows surface through the Gemini app, and the Engage SDK, which exposes in-app content to Play surfaces like Collections, has grown to over 30 million monthly active users and is driving a 45% year-over-year lift in app opens for participating titles. Store listing integration ships next month, with new tablet surfaces including home screen Collections, and every Engage SDK surface now scales across 80-plus Play markets.
Inside the Play Store, Play Shorts is a full-screen, portrait, short-form video feed rolling out to US users and select developers. Ask Play is a conversational search overlay backed by Gemini; the on-store Q&A feature already answers 95% of user queries. For developers, the implication is that descriptions, screenshots, and review text all feed Gemini's answer construction, so listing copy has to read well for both a human user and an LLM.
For games, Play Games Sidekick is an in-game overlay that surfaces AI-generated tips, rewards, and achievements without new SDK work. Over 100 games have launched with Sidekick, and Google is opening eligibility to all participating titles globally in summer 2026.
The Play Console adds AI-assisted localization (CSV or Google Sheet upload with Gemini translations), keyword-to-listing-copy generation, and agentic bulk price changes, SKU import, and metadata configuration automation.
Analytics gains reach measurement, conversion granularity, and AI-assisted interpretation, including interactive Q&A on selected metrics and tenure-aware churn reason breakdowns.
Protected with Play consolidates integrity configuration, distribution defense, and monetization fraud controls into one dashboard. Google reports 160 million spam ratings and reviews blocked and $3.2 billion in fraudulent and abusive transactions blocked automatically. Play Integrity API warm-up latency has also been reduced for latency-sensitive journeys.
| Change | Who needs it | Effort |
|---|---|---|
| targetSdkVersion 35 | Every app on v9 | One line |
| In-app price increase messaging | Apps with planned price increases | Add TRANSACTIONAL category |
| BILLING_UNAVAILABLE for blocked store | Apps handling billing errors | One branch |
| getLinkUri nullable | Developer-provided billing only | Null check + fallback |
Effort estimates are qualitative; actual work depends on your existing error handling and billing integration.
Frequently asked questions
Is Play Billing Library 9.0.0 a breaking change from v8?
No. The API surface is intentionally small. v8 was the breaking release; v9 adds one new in-app messaging capability, two compatibility adjustments, and a target SDK bump. Sub-response codes carry forward unchanged.
Do I need to change my code if I don't use developer-provided billing?
Only the targetSdkVersion bump is forced. The getLinkUri nullability change has no effect if you don't use developer-provided billing. The error code reclassification only requires touching code that already handles BILLING_UNAVAILABLE.
How often does the price increase message show?
At most once every 7 days, starting the first day the user can accept the new price. The payment issue message during grace period and account hold shows at most once per day. Calling showInAppMessages on every launch is safe; it returns NO_ACTION_NEEDED when there is nothing to show.
What happens if my app is still on v7?
The August 31, 2026 deadline applies to new apps and updates built against v7. There is no shortcut from v7 straight to v9: you do the v8 work first, then add the four v9 changes.