Google Play tests seat and usage billing for subscriptions; access remains limited

Google Play is testing ways to sell subscriptions by seat, by prepaid usage and alongside one-time products, but developers should not treat the whole set as generally available. Google described the changes on September 29, 2026, while saying that many of the capabilities are available only to selected partners or are still rolling out. For an app team, the immediate decision is to match a billing model to a real entitlement problem, then check access before designing a checkout around it.

Four purchase models address different constraints

Multi-Quantity Subscription Purchase is intended for a customer who needs several seats in one transaction and can assign them to team members or students. It is a different question from whether an individual user wants a monthly or annual plan. Google presents it as a way for productivity, education and AI apps to sell group access; it has not supplied a general launch date in the announcement.

Usage-Based Billing targets services with variable costs, including AI generation. Google describes prepaid metered use with an automatic top-up when the balance falls below a threshold. That is a proposed way to fund consumption, not evidence that an app can charge without a clear purchase experience. Teams would need to define what one unit buys, how a user sees remaining credit and how access changes when funds run out. Those are implementation questions, not features Google says it has solved for every app.

Mixed Carts would put an auto-renewing subscription and a one-time product into a single API call and checkout sheet. Previously, Google says, those purchases required separate transactions. Cross-Developer Bundling is a different arrangement: two or more subscriptions could be sold as one catalog bundle, including subscriptions from partner developers. That brings commercial and entitlement coordination between companies as well as a checkout change.

Existing subscriptions still have a usable path

The current Play Billing subscription documentation describes base plans, offers, prepaid plans and subscription add-ons. A prepaid top-up extends a subscription entitlement; it should not be confused with the newly described metered balance and automatic replenishment. Google also says its In-App Messaging API is available to all developers for payment declines and price-change notices. Those are concrete options to evaluate while the new models are being tested.

The September Google Play announcement says many of the new capabilities are in an Early Access Program or rolling out through Play Console. It directs developers with a Play partner manager to express interest as programs open. It does not give a single availability date, eligibility rule or production API specification for every new model.

Plan around access and entitlements, not a promised conversion lift

For a team selling AI usage, the first test is whether prepaid credit expresses its costs and user expectations better than a fixed recurring entitlement. For a collaboration app, the first design question is who owns seats and what happens when a seat is reassigned. A mixed cart may simplify a purchase, but it also requires the app to account for recurring and one-time rights separately. These are editorial implementation implications of the models Google describes, not measured results from live deployments.

Google frames the changes as tools for growth and retention, but the announcement provides no independent conversion or churn results for these features. Developers can map their entitlement and support flows now, then confirm which specific feature is enabled for their account before promising it to customers.

Sources

• Google Play's September 29 subscription announcement

• Google's Play Billing subscription documentation