Google Play billing Fraud policy: fixes and checks
By The Draftbit team · Updated
Sources checked
This guide is for Apps or SDKs that can initiate premium SMS, calls, or carrier charges.
Billing fraud includes deceptive charges through premium messages, premium calls, and carrier billing. A hidden WebView or SDK can cause this finding even when your visible checkout looks normal.
What to check
Inspect telephony permissions, billing redirects, WebViews, subscription prompts, and message interception. Check whether any code hides carrier confirmations or makes disclosures unreadable.
Test on a mobile network as well as Wi-Fi. Trace what happens after every button near a carrier payment flow, including transparent overlays and background navigation.
How to address the rejection
Remove deceptive billing code and any dependency responsible for it. Require a clear, intentional purchase action and keep price, recurrence, and confirmation information visible. Don’t suppress carrier messages that tell users about a charge.
Verify the corrected artifact cannot initiate the flagged transaction in the background. Give Google the affected library version and a precise explanation of the removed behavior. A refund policy doesn’t repair an unauthorized charging mechanism.
Messages this guide can help with
Billing Fraud; Billing Fraud policy violation; Billing Fraud rejection; Billing Fraud denied
Official sources
We checked these instructions against the sources below. The console layout may change, and your review decision may call for different steps.
- Google Play: Billing Fraud Checked 22 September 2026