Google Play Previews Multi-Seat Subscriptions, Usage-Based Billing and Mixed Carts
On September 29, 2026, Google Play announced a group of subscription features it is testing and rolling out: multi-quantity (multi-seat) subscription purchases, usage-based billing with automatic top-ups, mixed carts that put a subscription and one-time products in a single checkout, and bundles that combine subscriptions from different developers. Google says many of these are available or rolling out through an Early Access Program with select partners, so most apps cannot simply switch them on today. The one feature Google states is available to all developers now is the In-App Messaging API for payment declines and price changes.
The announcement matters most to apps that sell to teams, charge for AI usage, or lose subscribers to failed card payments. If you are planning or reworking subscriptions in an Android app, our Android app development team can help you decide which of these fit your billing model.
What did Google Play announce on September 29, 2026?
Google Play published a roadmap-style post describing nine subscription capabilities, grouped into new ways to sell and new ways to keep subscribers. The post, "Driving growth on Google Play: The next era of subscriptions", was written by a Google Play product manager and appeared on the official Android Developers Blog.
The selling features are Multi-Quantity Subscription Purchase, Usage-Based Billing, Mixed Carts and Cross-Developer Bundling. The retention features are the In-App Messaging API, Dynamic Grace Period, Retention Offers, Plan Change and Subscription Winback Offers. The post does not give launch dates, prices or fee changes for any of them.
Which of these features can an app use today?
As of October 6, 2026, only the In-App Messaging API is described by Google as "available now to all developers". For the rest, the post says that many features "are currently available or rolling out through our Early Access Program", which it defines as active testing with select partners before a broader rollout in Play Console.
Google does not list the status of each feature one by one, so treat everything other than in-app messaging as something to confirm in your own Play Console before you plan around it. Developers who work with a Google Play partner manager are told to contact that person to express interest as programs open. The post does not describe an application route for developers without a partner manager.
What is usage-based billing on Google Play and who is it for?
Usage-based billing is prepaid metered billing: the user holds a balance, and Google Play tops it up automatically when it falls below a threshold. Google positions it for apps with variable computing costs, and names AI generation tools as the example.
This addresses a real mismatch. A flat monthly price works when every subscriber costs about the same to serve. It works badly when one user generates ten images a month and another generates ten thousand, because the heavy user can cost more than they pay. Until now, apps on Google Play have usually handled this with credit packs sold as one-time products, which the user has to remember to rebuy.
The announcement does not explain how thresholds are set, whether users can cap automatic top-ups, or how unused balances and refunds are handled. Those details decide whether the model suits your app, so wait for the documentation before committing to it.
How do multi-seat subscriptions and mixed carts change what an app can sell?
Multi-quantity subscriptions let one buyer purchase several subscriptions in a single transaction and assign them as seats to team members or students. Google names productivity, education and generative AI apps as the intended users. For a business app, this means a manager could buy ten seats inside the app instead of asking ten employees to subscribe and claim expenses.
Mixed carts let an app sell an auto-renewing subscription together with one-time products in one API call and one checkout sheet. Google says these were historically separate transactions, so a user who wanted a monthly plan plus a starter pack of credits had to check out twice. Google also mentions offering a discount when the user buys the subscription and the extra items together.
Cross-developer bundles
Cross-Developer Bundling lets a developer sell a single bundle of two or more subscriptions, either across its own apps or together with another company. Google's example is a language learning app bundling its monthly plan with a partner's travel guide subscription at a combined discounted price. The post does not say how revenue is divided between the partners.
How does Google Play plan to reduce cancellations and failed payments?
Google Play is adding tools at three points: when a payment fails, when a user starts to cancel, and after a subscription has lapsed.
When a payment fails
The In-App Messaging API shows a Google Play message inside your app asking the user to fix a declined payment, or telling them about a price change. According to the Google Play Billing subscriptions documentation, the payment message is shown once per day during the grace period and account hold. The same documentation explains the two stages: during the grace period the user keeps access to what they paid for, and during account hold they do not.
Dynamic Grace Period replaces a fixed grace period with one that Google Play sets per subscriber, using machine learning and heuristic models to estimate how likely that person is to fix the payment. Google says it adjusts the following account hold period automatically so your total configured recovery window stays the same, and that no changes to app code are needed.
When a user cancels or has already left
Retention Offers let you show a developer-funded incentive, such as a discount, inside the Play Store cancellation flow. Plan Change suggests a cheaper tier to users who are not eligible for an offer. Subscription Winback Offers show offers to former subscribers on the Play Store itself, which reaches people who have uninstalled the app and can no longer receive its notifications.
Is Apple doing the same thing on the App Store?
Yes, in part: Apple has announced multi-seat purchases and subscription bundles with firmer dates than Google has given. In a September 16, 2026 developer notice, Apple said Volume Purchasing launches on October 22, 2026, Group Purchases will launch "this winter", and Bundles and Suites will be available "later this year" on request.
The practical point for a business with both an Android and an iPhone app is that team plans and bundles are arriving on both stores at about the same time but on different schedules and with different rules. Your backend needs to track seats and entitlements in a way that does not assume either store's model.
What should a business do now?
Adopt what is available, and prepare for the rest without building on features you cannot yet access.
- Ask your developer whether your Android app already calls the In-App Messaging API. It is available now and is aimed at the failed payments most apps lose subscribers to.
- Check the grace period and account hold lengths set for each base plan in Play Console, and confirm your app removes and restores access correctly in each state.
- If you sell to teams or charge for AI usage, write down how you would price seats or metered usage, so you can move quickly when access opens.
- If you have a Google Play partner manager, tell them which early access programs interest you.
- Review your server-side entitlement logic. Seats, top-up balances and bundles all need records that a simple "is this user subscribed" flag cannot hold.
Quick answers
What did Google Play announce for subscriptions in September 2026?
On September 29, 2026, Google Play described nine subscription features, including multi-seat purchases, usage-based billing, mixed carts, cross-developer bundles, dynamic grace periods, and retention and winback offers. Most are in testing or early access rather than generally available.
Can I use Google Play usage-based billing today?
Probably not yet. As of October 6, 2026, Google has not said usage-based billing is generally available, and describes many of the new features as rolling out through an Early Access Program with select partners.
What is the Google Play In-App Messaging API?
It is a Play Billing feature that shows a Google Play message inside your app when a subscriber's payment has been declined or a price change needs their attention. Google says it is available now to all developers.
What is a mixed cart on Google Play?
A mixed cart is a single checkout that contains an auto-renewing subscription and one or more one-time products. Google Play announced it on September 29, 2026 so users no longer need two separate purchases.
How do I join the Google Play subscriptions Early Access Program?
Google's announcement says developers who work with a Google Play partner manager can contact them to express interest as programs open. It does not describe another way to apply.
Did Google Play change its subscription fees in this announcement?
No. The September 29, 2026 post does not mention service fees, pricing or commission changes for any of the new features.
Conclusion
Google Play is moving subscriptions beyond one person paying one flat monthly price, toward seats, metered usage and bundles. Most of that is still in early access with no published dates, so the sensible work today is the available part: in-app payment messages, correct grace period handling, and entitlement logic that can cope with more than a yes-or-no subscription.
Entrant Technologies builds websites, web applications, mobile apps and custom software. If you want a second opinion on how your app handles subscriptions, contact us and we will take a look.