# Google Play Payments policy: use Play Billing

> Google Play rejected the app under the Payments policy for selling digital goods with Stripe? What must use Play Billing, and how to fix it.

**Payments — Payments: digital goods must use Google Play Billing.** The app sells digital content or subscriptions with Stripe or another processor instead of Google Play’s billing system. Physical goods and real-world services are exempt; alternative billing is only allowed in some countries, through Google’s programs.

- Google Play · Payments. Payments: digital goods must use Google Play Billing.
- Interactive page: https://capwr.app/free-tools/app-store-rejection-explainer/google-play-payments-policy
- Rejection explainer: https://capwr.app/free-tools/app-store-rejection-explainer
- Last updated: 2026-10-14

## What this rejection means

The app sells digital content or subscriptions with Stripe or another processor instead of Google Play’s billing system. Physical goods and real-world services are exempt; alternative billing is only allowed in some countries, through Google’s programs.

## Why reviewers send it

Digital goods and subscriptions sold inside an Android app on Google Play generally have to use Google Play’s billing system. A wrapped Stripe checkout is the usual trigger; physical goods and real-world services are exempt.

## The message Google Play sends

```
Issue found: Violation of Payments policy

Your app offers digital goods or subscriptions without using Google Play’s billing system.
```

The exact wording changes from one review to the next; the policy name is what to look for.

## How to fix it

1. Sell digital goods and subscriptions in the Android app through Google Play Billing. RevenueCat covers both stores.
2. Remove the Stripe checkout and links to buy digital content on your site from the Android app, unless you are enrolled in an alternative billing program for that country.
3. Create the products in Play Console → Monetize, upload a build with the billing library, and resubmit.

## Fix it with Lovable, Bolt or Cursor

If the app was built with an AI builder, paste this into it, then check the result on a phone:

```
On Android (Capacitor.getPlatform() === "android"), hide the Stripe checkout and every “buy on the website” link, and sell premium through Google Play Billing with RevenueCat’s Capacitor SDK.
```

## What to tell Google Play

Replace the [brackets] with what you actually changed:

```
Digital purchases in the Android app now go through Google Play Billing. We removed [the Stripe checkout / external purchase links] from the app.
```

## Got a different message?

Paste the whole rejection into the [rejection explainer](https://capwr.app/free-tools/app-store-rejection-explainer). It recognises this one and 26 others, in your browser — nothing is uploaded.

## Other Google Play rejections

- [Google Play Broken Functionality rejection](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-broken-functionality)
- [Google Play webview and minimum functionality](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-webview-minimum-functionality)
- [Google Play invalid privacy policy](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-invalid-privacy-policy)
- [Google Play Data safety section inaccurate](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-data-safety-inaccurate)
- [Google Play missing login credentials](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-missing-login-credentials)
- [Google Play account deletion requirement](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-account-deletion)
- [Google Play photo and video permissions policy](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-photo-video-permissions)
- [Google Play Metadata policy violation](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-metadata-policy)
- [Google Play production access refused](https://capwr.app/free-tools/app-store-rejection-explainer/google-play-production-access-denied)

## Fixed it? Ship the new build to Google Play

CapWrapp builds and signs the Android app from your GitHub repo, bumps the version code, and uploads it to Google Play — then promotes it to production when you are ready.

[Get started free](https://capwr.app/login).

## About CapWrapp

CapWrapp turns a web app on GitHub — built with Lovable, Bolt, Base44, Cursor or by hand — into iPhone and Android apps. It adds Capacitor if the repo needs it, signs the builds, and ships them to TestFlight and Google Play from GitHub Actions, with no Mac or Xcode on your side. [Get started free](https://capwr.app/login) · [Lovable to App Store guide](https://capwr.app/guides/lovable-to-app-store)