Play Billing Library v8 is mandatory on 31 August 2026

Are you affected? Two minutes

Search your Gradle files for the billing dependency:

grep -rn "com.android.billingclient:billing" --include="*.gradle*" .

Anything below 8.0.0 has to move. If you use Unity, Flutter, RevenueCat, Adapty or a similar wrapper, the version that matters is the one they bundle — check their release notes for Billing 8 support rather than assuming a plugin update covers it.

What v8 actually removed

This is not a version bump. v8 deleted the API surface that most integrations were written against, so the migration is a rewrite of your purchase path rather than a dependency edit:

• The SkuDetails family is gone. Queries now use queryProductDetailsAsync and return a QueryProductDetailsResult.
• Pending purchases must be declared explicitly through PendingPurchasesParams.
• Subscription upgrades and downgrades move to SubscriptionProductReplacementParams.
• One-time products gain multiple purchase options and offers, which changes how you model anything that isn’t a plain unlock.

Source: Google’s Billing Library deprecation FAQ and its v8 migration guide. Read them yourself — the FAQ also lists a 2027 row for the following version, which is easy to mistake for this deadline.

If you need more time

Google allows a requested extension to 1 November 2026. That is an extension, not a second deadline: you ask for it, and until it is granted the August date is the one that binds.

The part nobody budgets for

Swapping the client library is the visible half. The half that generates support tickets is server-side: entitlement that survives a refund, a chargeback, a grace period and an account hold; real-time developer notifications that arrive out of order and more than once; and a purchase acknowledged inside three days or automatically refunded by Google. A client-only migration passes review and still loses revenue quietly.