Google Play Alternative Billing Rolls Out: Savings Aren't Simple

Google has begun rolling out Google Play alternative billing across the U.S., UK, and EU this month, letting Android developers route payments outside its system and avoid a portion of its fees. Australia, South Korea, and Japan follow before the end of 2026. The rest of the world comes later, after September 30, 2027, Bloomberg Law reported in March.

Who benefits depends on a set of conditions that make this a clear opportunity for some developers and an ambiguous one for many others.

The timing carries context worth understanding. Google began this rollout while the court overseeing its antitrust settlement with Epic Games has not yet issued final approval, The Verge reported this week. The UK launch, which went live in March 2025, came explicitly in response to concerns from the Competition and Markets Authority, Google's blog noted at the time. Google's VP of commerce said the fee changes weren't required by the U.S. court or foreign regulators, Bloomberg Law reported in March. The geography of where changes are landing first suggests a more complicated story.

Which developers stand to gain from Google Play billing choice

The fee change is real. Its value is concentrated.

The developer profile that benefits most is specific: high-revenue, subscription-driven, with an existing payments relationship and the engineering capacity to integrate a parallel billing path. Google's flat 30% commission is being replaced by a tiered structure with three variables: annual developer revenue, which billing system processes the transaction, and when the user first installed the app, The Verge reported this week.

For apps earning over $1 million annually, the numbers get meaningful fast. The store fee on subscriptions drops to 10%. Developers who use Google's own billing system on top of that pay an additional 5% billing fee. Route those same renewals through an external processor and only the 10% store fee applies that additional 5% disappears, Bloomberg Law reported in March. On a subscription business with tens of millions in annual recurring revenue, that differential compounds quickly. The catch is that the developer now absorbs processor fees, fraud management, disputes, and backend reporting overhead that Google previously handled.

Subscription apps and streaming services at that revenue scale are the most plausible near-term adopters. They already manage recurring billing relationships, often have processor contracts in place, and can measure the fee reduction against a large, ongoing transaction base.

Smaller developers face a harder calculation. For those already on Google's reduced rate under its small business program, the incremental gain from switching may not clear the bar. The program also isn't uniformly accessible: eligibility varies by region, availability is determined at runtime rather than configured statically, and a developer who completes the integration may find it inactive for users in certain markets, RevenueCat explained yesterday. Whether external billing pencils out depends on transaction volume, existing infrastructure, and which markets their users are in.

How Google Play billing choice actually works

The framing of "outside payments allowed" understates how much of the purchase flow Google still controls. Two distinct programs exist, and only one is broadly available in the current rollout.

"Alternative billing with user choice" presents buyers with a side-by-side screen showing both Google Play Billing and the developer's own system. "Alternative billing only" lets certain developers in eligible regions skip Google's billing entirely, but it's subject to separate regional terms and enrollment requirements, Android Developers documentation explains. The current rollout runs primarily on the user choice model.

The choice screen is not a neutral handoff. Developers can build their own version or let Google render it, but either way, Google's payment artwork and any loyalty messaging Play Points promotions, for instance must appear alongside the developer's option, retrieved at runtime via Google's API, RevenueCat explained yesterday. Before any alternative transaction completes, the app must trigger a legally required disclosure dialog that Google specifies. Google's developer policy still designates its billing system as the default; the alternative programs are defined carve-outs, not a blanket repeal of that requirement, Google Play Developer Program Policy.

Every transaction completed outside Google's system must still be reported back to Google through its external transaction APIs, whether payment happened in-app or through an external link, Android Developers documentation notes. Manual transaction reporting is being sunset the API path is now the required path. Developers gain real flexibility on payment processing. Google keeps the disclosure language, the screen design rules, the reporting obligation, and the eligibility gate.

One scope point worth noting: these changes cover digital goods and in-app content. Physical goods, physical services, and utility payments were never subject to Google Play billing requirements and remain exempt, Google Play Developer Program Policy.

The build cost that doesn't show up in the fee numbers

Accessing alternative billing is an engineering project, not a settings toggle. The scope of that project will determine whether the fee savings are worth pursuing.

Billing Choice requires Play Billing Library version 9.1 or higher. Separately, every new app and every update to an existing app must build against Billing Library 8 or later by August 31, 2026, with an extension available on request through November 1, RevenueCat explained yesterday. Developers who haven't already migrated face that prerequisite before enrollment is even possible.

Subscriptions add a layer of complexity that matters to the business decision, not just the build. The first transaction in a recurring subscription requires an external transaction token, which must be reported to Google. Renewals reference the original token rather than generating new ones. A plan upgrade or downgrade is treated as a new purchase with its own token, which then anchors all subsequent renewals for that user, RevenueCat explained yesterday. Implementing this incorrectly produces misreported transactions a compliance exposure, not just a technical bug.

The full cost of switching runs beyond the fee differential: one-time engineering work to integrate and test the alternative billing path; ongoing overhead from operating a second processor relationship; fraud and dispute management that previously sat with Google; compliance reporting that now falls on the developer's backend. For a large subscription publisher with strong renewal volume, that tradeoff has a reasonable chance of resolving in favor of switching. For a smaller developer or one with a one-time purchase model, the arithmetic is considerably murkier.

What to watch in the second half of 2026

Analysts had estimated that changes to Google's app store structure could cost the company roughly $1 billion in gross profit, Bloomberg Law reported in March. Whether developers claim those savings or leave them on the table is now an open question.

The signal worth watching is whether large subscription publishers and streaming apps begin integrating alternative billing at scale over the next six months. If they do, it confirms the savings justify the build cost at that tier. The legal picture adds another variable: the Epic settlement's durability remains uncertain while final court approval is pending, The Verge reported this week. Regional availability also continues to expand on a delayed schedule, with the majority of markets not covered until after September 2027.

For users, the immediate experience is a choice screen at checkout, assuming developers complete the integration. Whether any fee reduction passes through as lower prices or better subscription terms is a separate decision one developers haven't had to make yet, and one nobody is requiring them to make.