Google Play payments policy: fixes and checks

A Payments rejection usually requires checking what you’re selling and how the user reaches checkout. Google generally requires Play billing for paid downloads and in-app digital purchases, with specific exceptions and regional programs.

What to check

Classify each product separately. Digital access, virtual currency, cloud features, and subscriptions generally fall under Play billing. Physical goods, physical services, and certain other transactions must not use it.

Trace the entire purchase path, including account creation, WebViews, emails linked from the app, and listing calls to action. An external checkout button can still be a payment-policy issue even if it opens a browser.

How to address the rejection

Use the required billing method for the product and region. Alternative billing and external offers depend on current eligibility, enrollment, and program terms. Don’t apply an exception from one country to every user.

Make displayed prices match the billing interface and identify paid features in the listing. Keep purchased virtual currency within its app or game. If purchases award randomized virtual items, disclose the odds near the purchase before users pay.

Test purchase, cancellation, entitlement delivery, and restore or account recovery. In your response, identify the product type, affected region, checkout change, and any enrolled program you rely on. Use the official policy’s linked program terms for current regional details.