Google Play Billing for Digital Goods in WebView Apps: A Complete 2026 Guide

Google pulled a WebView app from the Play Store for selling subscriptions through Stripe directly inside the app. No warning — just a policy violation notice. The developer had to scramble to fix the billing flow or lose their listing entirely.

If your Android app wraps a website that sells digital goods, this guide explains exactly what Google requires, which products are affected, and the simplest way to stay compliant without rebuilding your entire payment flow.

What Google Play's Billing Policy Requires for Digital Goods

Google Play requires apps to use Google Play Billing when they sell digital goods or digital content inside the app. This applies to subscriptions, in-app purchases, and any digital item unlocked directly within the app experience.

The policy is clear: if a user can purchase something digital without leaving the app — and that purchase delivers value within the app — it must go through Google Play's billing system. Charging via Stripe, PayPal, or any external processor for in-app digital purchases violates the policy and can result in app removal.

The Google Play billing requirement has been enforced strictly since 2022. With the growing number of WebView apps on the Play Store, Google's automated policy scanners now regularly flag apps where payment forms appear inside a WebView without a Google Play Billing integration.

Which Digital Goods Actually Trigger the Requirement

Not everything you sell is subject to this rule. Google defines "digital goods" narrowly, and it's worth understanding the line.

Subject to Google Play Billing:

• Subscriptions that unlock in-app features or content (course platforms, membership sites, SaaS tools)
• Virtual currency or in-game items
• Downloadable digital content (PDFs, presets, digital templates sold inside the app)
• Premium app features unlocked via purchase

Exempt — Google Play Billing is NOT required:

• Physical goods (clothing, furniture, food orders, products shipped to customers)
• Physical services (restaurant bookings, cleaning appointments, haircut scheduling)
• Digital goods purchased on your website and delivered separately
• Peer-to-peer payments, ride-sharing, financial services

This distinction matters enormously for most WebView apps. A Shopify store wrapped as an app selling physical products has no billing policy issue. A WooCommerce store selling digital downloads through its built-in checkout does.

If you run a course platform, SaaS dashboard, or subscription-based community, the rule applies to you.

How WebView Apps Handle Google Play Billing Compliance

WebView apps that need to comply have two options.

Option 1 — Implement Google Play Billing SDK. This involves integrating Google's billing library into the native wrapper around your WebView. It's the full-compliance approach but requires native Android development work. Unless you have a developer, this is complex to maintain.

Option 2 — Redirect purchases to an external browser. This is the most common approach and is explicitly permitted by Google's policy. When a user taps a purchase button inside your app, instead of completing the transaction inside the WebView, you open an external browser (Chrome, for example) where the user completes the purchase. The app then delivers the content once the purchase is confirmed.

This is the same pattern Udemy, Coursera, and most subscription apps use on iOS and Android. The purchase does not happen inside the app — it happens on your website in a browser.

Services like Webvify handle this configuration during the app build process, ensuring WebView apps are pre-configured to route payment flows to an external browser so they pass Google's policy review without requiring you to write any native code.

The Simplest Fix: External Browser Redirect

If your website's checkout process is the problem, the fix is to make those pages open in the device's default browser instead of inside the WebView.

This means identifying which URLs trigger the purchase flow (typically /checkout, /subscribe, /purchase, or similar paths) and configuring the WebView to intercept those links and open them externally. This is a native-layer configuration — it cannot be done from your website's code alone.

This approach has three advantages:

1. You stay fully compliant with Google Play's billing policy without building a billing integration.
2. Your website's existing payment processor (Stripe, PayPal, etc.) continues to work exactly as it does on the web.
3. Apple's App Store has an equivalent rule (Guideline 3.1.1) — the external browser redirect solves both platforms at once.

Once you've configured external redirects, test the app by going through the full purchase flow on a test device. Confirm the checkout page opens in Chrome (or the default browser), not inside the app. If the payment form appears inside the WebView, Google's scanner will flag it.

The same compliance principle applies to iOS — you can read the full App Store submission requirements in our app store rejection prevention guide. And if you haven't yet converted your website to an Android app, see our step-by-step guide to converting your website to an Android app.

What Happens If You Ignore the Policy

Google enforces billing violations in two ways.

Pre-launch: During the review process, Google's automated tools check whether payment forms or purchase buttons are present inside the app without a Google Play Billing integration. If they find one, the app is rejected before it ever goes live.

Post-launch: Google also audits live apps. An app that passed review can be taken down later if a billing policy violation is discovered. When this happens, Google sends a policy violation notice and gives a window to fix the issue. If the issue isn't resolved, the app is removed from the Play Store.

A removed app loses all its reviews, its install base, and its search ranking. Getting reinstated requires fixing the issue and appealing — a process that takes days to weeks.

The compliance fix (external browser redirect) takes far less time than recovering from a policy removal.

FAQ

Does Google Play billing apply to WebView apps that only sell physical products?

No. Physical goods — including physical products sold through Shopify, WooCommerce, or any e-commerce platform — are exempt from the Google Play billing requirement. The rule applies only to digital goods and digital content purchased and delivered within the app experience. A restaurant app taking food orders, a clothing store selling physical items, or a service business taking appointment bookings are all fully exempt.

Can I use Stripe inside my Android WebView app?

Stripe can be used for physical goods and services without any issue. For digital goods purchased inside the app, Stripe alone is not permitted — the purchase must either go through Google Play Billing or be redirected to an external browser. If you redirect the purchase to an external browser (your website's checkout page), Stripe continues to work normally — the restriction is about where the purchase happens, not which payment processor you use.

How do I know if my app will be flagged for a billing policy violation?

Check whether your website has any pages where a user can complete a purchase of digital content (subscriptions, digital downloads, premium features) without leaving the app. If those checkout pages load inside your WebView, you are at risk. Audit your purchase flows before submitting to Google Play. If you're using a done-for-you app service, ask them specifically whether payment pages are configured to open in an external browser.

---

Keeping your Google Play listing compliant is a one-time configuration, not an ongoing maintenance burden. If you want your WebView app built with billing compliance pre-configured — so payment flows route correctly from day one — get started with Webvify.