Guides
Google Play Billing for Website Apps: When Your Checkout Needs It (2026)
If your site sells memberships, courses or premium content, Google's Payments policy decides how that checkout can work inside an Android app. Here are the rules, the exceptions and the dated US changes, checked November 2026.
If your website sells digital goods or subscriptions (memberships, courses, premium content, software access) and that checkout appears inside an Android app on Google Play, Google's Payments policy generally requires Google Play billing for those purchases. Physical goods and services go the other way: Play billing must not be used for them. The policy also names in-app webviews as one way an app can lead users to another payment method, so a website app does not get a pass just because the checkout is a web page. Rules checked November 21, 2026.
Does Google Play billing apply to a website app?
Yes, when the app requires or accepts payment for digital content or features. Section 2 of Google's Payments policy says Play-distributed apps requiring or accepting payment for access to in-app features, services, digital content or goods must use Google Play's billing system, unless Section 3, 8 or 9 applies. Its examples include subscription services (fitness, education, music, video and other content subscriptions), app functionality such as an ad-free version, and cloud software such as storage or productivity tools.
Section 4 closes the obvious workaround. Apps may not lead users to a payment method other than Play billing through in-app webviews, buttons, links, messaging, advertisements or other calls to action, including account creation and sign-up flows. Google's policy text does not carve out a website loaded in a WebView, so my reading is that a pricing page or checkout shown inside your app counts as in-app. That is an inference from the wording, not something Google says about website apps by name.
Billing is separate from Google's webview spam review, which is covered in the guide to Google Play rejecting WebView apps. An app can pass one and fail the other.
Which products on your website need Play billing?
Google sorts products by what the buyer receives, not by how the checkout looks. This table summarises the main cases from the policy and its FAQ.
| What your website sells | Play billing under Google's rules |
|---|---|
| Physical goods (clothing, groceries, electronics, housewares) | Must not be used. Use your own checkout. |
| Physical services (transport, cleaning, airfare, gym memberships, food delivery, live event tickets) | Must not be used when payment is primarily for these. |
| Content subscriptions (fitness, education, music, video, dating) | Required, unless a policy exception or regional program applies. |
| Premium unlock or ad-free version of the app | Required. |
| Cloud software and services (storage, business productivity, financial management) | Required. |
| Digital content that can only be used outside the app and cannot be accessed in it | Not required, per the FAQ. |
| 1:1 online paid services (lessons, health coaching, advisory) that cannot be replayed afterwards | Not required, per the FAQ, if the service is between two individuals and is not recorded or replayable in any Play-distributed app. |
| Gift cards sold in the app | Not required, per the FAQ. |
| Mixed carts of physical and digital items | Required for items that include more digital than physical content, and for items marketed as digital. |
Selling physical products is covered in more depth in the guide to turning a Shopify store into an Android app. The rest of this post is about the digital side.
Can a consumption-only app skip Play billing?
Yes, if the app itself sells nothing. Google's FAQ says any app can be consumption-only, even when it is part of a paid service: a user can log in when the app opens and reach content they paid for somewhere else. The catch is in the definition. Consumption-only means no product or service, digital or physical, can be purchased from within the app.
Inside such an app, Google still says developers may not directly link to a page that could lead to another payment method, or use wording that encourages buying the digital item outside the app. General information about purchasing options without direct links is allowed, and Google's examples include telling users they can upgrade on the developer's website. Developers can also point users to administrative pages such as account management, a privacy policy or a help center, as long as the page does not eventually lead to a prohibited payment method.
If the paid area sits behind a login, reviewers need working sign-in details. Google's FAQ notes that apps have been rejected for missing login credentials after a payments-policy update; the fix is in the guide to Google Play app access instructions.
What changed for US users in 2025 and 2026?
Google's US policy update page says that, to comply with a US court injunction as of October 29, 2025, it will not require Play Billing in Play-distributed apps serving US users on mobile and tablet, will not prohibit other in-app payment methods, and will not prohibit developers from linking to transactions or talking about other payment options. The page says these changes apply during the effective dates of the injunction.
| Date | What Google says |
|---|---|
| October 29, 2025 | Injunction-related changes apply for apps on mobile and tablet serving US users. |
| December 9, 2025 | Alternative billing and external content links programs launched for US users. |
| March 4, 2026 | New settlement with Epic; the parties asked the court to enter a revised Modified Injunction, with more details to come. |
| July 22, 2026 | Notice that developers enrolled in the US programs must report transactions and pay service fees starting October 1, 2026. |
| October 21, 2026 | External content links enrollees have until February 1, 2027 to report successful downloads and pay the related fees. |
Google words this in two ways. The update page says Google will not require Play Billing for US users, while the Payments FAQ says developers may offer additional billing options or lead US users outside the app if they are enrolled in the appropriate program. The update page also says the policies and programs remain in effect. My inference: enroll before you rely on a US external link or alternative checkout, and reread the update page before each release, because the program pages say Google can modify or end the programs if the court order changes.
| Fee tier | Auto-renewing subscriptions | Other digital items, new installs | Other digital items, existing installs |
|---|---|---|---|
| First US$1M annual earnings | 10% | 10% | 10% |
| Standard service fees | 10% | 20% | 25% |
| Play Games Level Up or Apps Experience programs | 10% | 15% | 20% |
Google counts an install as new when the user's first install or first update from Google Play happened on or after June 30, 2026. The external content links program has its own fee table, so read that page too if you plan to link out.
Outside the US, Google offers an alternative billing program and an external offers program in the European Economic Area. In India and South Korea, developers can offer an alternative billing system alongside Play's, with the service fee reduced by 4 percentage points (Google's example: 15% becomes 11%).
What should a website app that sells things do before submitting?
- 1
List what the site sells
Write down every product, plan and upgrade, including free tiers that unlock paid features.
- 2
Classify each item
Use the table above: physical, digital, or exempt, such as a non-replayable 1:1 session.
- 3
Decide what the app version does
Use Play billing for digital items, run as consumption-only with no purchase flows inside the app, or, for US users, enroll in an alternative program first.
- 4
Check what the WebView can reach
On a phone, follow every link from your account and pricing pages. Anything leading to a payment method other than Play billing falls under Section 4.
- 5
Match prices and disclosures
Google requires clear terms and pricing, in-app pricing must match the price shown in Play's billing interface, and a listing that mentions paid features must say payment is required.
- 6
Prepare reviewer access
If the paid area needs a login, give reviewers working sign-in details under App access before you submit.
Frequently asked questions
- Does my website app need Google Play billing for subscriptions?
- If the app requires or accepts payment for digital content, subscriptions or features, Google's Payments policy says it must use Google Play billing unless an exception or regional program applies. The examples Google lists include fitness, education, music, video and other content subscriptions. Physical goods and services are the opposite: Play billing must not be used for them.
- Can I send app users to my website to pay?
- In general no. The policy says apps may not lead users to another payment method through in-app webviews, buttons, links, messaging or other calls to action, outside the listed exceptions. For US users, Google offers an external content links program with its own enrollment steps, fees and rules, so check that page before linking out.
- What is a consumption-only app on Google Play?
- It is an app where users can access content they paid for elsewhere but cannot buy any product or service, digital or physical, from inside the app. Google's FAQ says any app can be consumption-only, even if it is part of a paid service, but in-app links to pages that lead to other payment methods are still restricted.
- Do I need Play billing for physical products in my app?
- No. Google's Payments policy says Play billing must not be used when payment is primarily for physical goods such as clothing, electronics or housewares, or for physical services such as transport, cleaning or food delivery. Use your own checkout for those.
- Did Google stop requiring Play billing in the US?
- Google's US update page says that, to comply with a US court injunction, as of October 29, 2025 it will not require Play Billing for US users on mobile and tablet while the order is in effect. It also points developers to enrollment programs with reporting and service fees from October 1, 2026. Terms can change, so recheck the page before each release.