Google Play User Choice Billing in 2026: A Step-by-Step Guide to Alternative Billing in the EEA, UK, and US

Google Play takes a cut of every in-app purchase, and for most apps that is the end of the story: Play's billing system is the only way to charge for digital goods. User choice billing is the exception. Under this pilot, an eligible app can show users a second, non-Google payment option next to Google Play's billing system — and for purchases that run through it, the developer pays Google a reduced service fee.

Two things changed in 2026 that make this worth re-reading. The pilot now spans eight markets instead of the EEA alone, and the fee schedule for the EEA, the UK and the US was rewritten with an effective date of June 30, 2026 — from that day the fee depends on whether the buyer is a new or an existing install. Everything below comes from Google's own program page, cited at the end.

What user choice billing is — and what it is not

User choice billing lets a Play-distributed app offer an alternative billing system inside the app, alongside Google Play's billing system. Users still see Play billing as an option; the service fee still applies. Three neighbouring programs are often confused with it:

• Alternative billing without user choice — the EEA program built for the Digital Markets Act, where you are not required to offer Play billing next to your own system.
• External offers / linking out — a separate program for directing users to make purchases outside the app, with its own fees and rules.
• South Korea and India — each has its own alternative billing program, and neither is part of this pilot.

You can mix: keep Play billing in some markets and offer user choice billing in others. Enrollment is per app and per market, and for any given app you may select only one program at a time per country.

Who is eligible in 2026

Two hard gates. Your developer account must be registered as a business — an individual account cannot enroll — and your app must fit one of these buckets:

• Any app or game, any form factor, for users in the EEA.
• Any app or game on mobile or tablet for users in the United States or Japan.
• A non-gaming mobile or tablet app for users in the remaining announced markets.

The announced pilot markets are the EEA countries, Australia, Brazil, Indonesia, Japan, South Africa, the United Kingdom and the United States. Games are currently limited to the EEA, the US and Japan.

The fee table that changed on June 30, 2026

For transactions with users in the EEA, the UK or the US on or after June 30, 2026, Google replaced the old blanket discount with a table that turns on purchase type and install age:

• Auto-renewing subscriptions: 10% in every column, including the standard service fee.
• Other digital features, new installs: 10% on the first $1M of annual earnings, 20% at the standard rate, 15% if the app is in the Play Games Level Up or Apps Experience programs.
• Other digital features, existing installs: 10% on the first $1M, 25% at the standard rate, 20% with Level Up or Apps Experience.

A new install is a user whose first install or first update from Google Play happened on or after June 30, 2026; an existing install is anyone who was already in before that date. Outside those three markets, the older rule still stands: when a purchase goes through your alternative billing system, the standard service fee is reduced by 4%.

Step by step: enroll and integrate

1. Check eligibility against the market and app-type rules above, and confirm the developer account is a business account.
2. Enroll in Play Console under Settings → Alternative billing, accept the terms of service and complete any payment profile setup the onboarding asks for.
3. Integrate the alternative billing APIs from day one. They render the user choice flow and report transactions back to Play; since March 13, 2024 apps offering alternative billing as part of this pilot have had to use them.
4. Configure each app in the Play Console alternative billing settings: opt in or out per app, upload payment method logos and subscription management URLs.
5. Report every authorized transaction from pilot-market users within 24 hours through the APIs. This is what keeps transactions visible in Play's top charts and what your service fee is calculated from.

The requirements that get developers removed

The obligations are part of the pilot, not paperwork around it:

• Offer the alternative system inside the app only. Web-based payment is allowed as an embedded webview inside the app, not as an out-of-app checkout.
• PCI-DSS compliance if you or your processor handle credit and debit card data.
• Your own customer support for anything bought through the alternative system, including a documented process for disputing unauthorized transactions.
• Advance notice to Google before you change enrollment — enabling or disabling user choice billing for a market or an app.

Google also states that its billing system must remain available as an option, because it carries protections the alternative system may not — parental controls, family payment methods, subscription management, gift cards and Play Points. The Payments policy remains the binding document for what counts as a digital purchase in the first place.

Should you actually switch?

Run the arithmetic before you build. On subscriptions in the EEA, the UK or the US the answer is usually yes: a flat 10% applies to auto-renewing revenue regardless of install age, and it is the only line in the table that does not move. On one-time digital purchases it narrows fast — an existing install at 25% is close enough to Google's standard fee that the saved margin can disappear into the cost of the stack you now own: PCI scope, card refunds, chargebacks, tax collection in each market, and a 24-hour reporting obligation that must not fail silently. For a portfolio dominated by existing installs and one-time purchases, staying on Play billing alone is a defensible answer.

Sources

• Google Play Console Help — Enrolling in the user choice billing pilot: support.google.com/googleplay/android-developer/answer/12570971
• Google Play Console Help — Understanding Google Play's Payments policy: support.google.com/googleplay/android-developer/answer/10281818