Google Play announces expanded billing choice, a Registered App Stores program, and a new fee model (March 2026)

Original post (source): Android Developers Blog - “A new era for choice and openness” (March 4, 2026)

• https://android-developers.googleblog.com/2026/03/a-new-era-for-choice-and-openness.html

The headline

Google is signaling a broader shift in how Android app distribution and payments work:

• More billing choice (including using your own billing in-app alongside Play billing, and guiding users to your website),
• a Registered App Stores program (to make installing third-party app stores feel less scary/frictiony), and
• lower fees with a model that splits “billing” and “service” components.

This is mostly “platform ops”, but it has growth impact because it changes:

• where users can pay,
• how entitlement flows need to work, and
• how you structure your pricing, refunds, and compliance story across channels.

1) Expanded billing choice

Google’s language here is deliberately broad, but the direction is clear:

• Developers can choose to use their own billing system in-app alongside Google Play billing.
• Developers can also guide users outside the app to their own websites for purchases.

Practical implication: your growth stack needs a clearer, documented answer to:

• “Where can a user buy?”, and
• “What is the source of truth for entitlement?”

2) Registered App Stores (distribution / sideloading)

Google says it will introduce a Registered App Stores program that gives qualified app stores a more streamlined installation flow, as long as they meet quality and safety benchmarks.

Notes Google calls out:

• It’s optional.
• It starts outside the US first, with intent to bring it to the US subject to court approval.

Practical implication: if you distribute via alternative stores, the top-of-funnel friction may drop, which means your attribution and lifecycle messaging need to treat “store source” as a real segmentation dimension.

3) New fee model (service + billing)

Google describes a fee approach that:

• decouples a billing fee from a service fee, and
• sets a market-specific billing rate for those choosing Play billing.

They explicitly mention (in the post snippet) that in the EEA, UK, and US, the billing rate will be 5%.

Even if you don’t change anything, this is a finance and pricing conversation you should be aware of because the “default Play take-rate” is no longer a single number.

Why this matters for app marketing teams

1. Entitlements get harder. Multi-billing and multi-store distribution turns “what did they buy?” into a support and data problem unless you have one canonical entitlement layer.

2. Attribution gets messier. More purchase routes means more cases where “install source” and “purchase source” diverge.

3. Lifecycle messaging needs guardrails. If you can buy on the web, your in-app prompts need to be consistent (and compliant) across regions.

Tiny win

Write a one-page “entitlement map” today:

• purchase routes (Play billing, alternative billing, web)
• where the receipt lives
• how access is granted
• what Support should check first

If that doc doesn’t exist, you will relearn it during the first refund/chargeback incident.