Google Play earned wage access policy: fixes and checks
By The Draftbit team · Updated
Sources checked
This guide is for Google Play apps offering earned-wage access directly or through leads and third-party providers.
Calling an advance “earned wages” doesn’t make it qualify as earned-wage access. Google’s definition concerns already-earned wages, repayment through payroll or linked autopay, and a specific fee and debt model.
Compare the real terms with the definition
Check that access is limited to wages already earned in the current pay period. Review interest, transaction/subscription fees, failed-payment charges, repayment, and credit reporting. We’d calculate a representative customer’s full cost, including fees outside the advance screen.
Google describes EWA as interest-free with modest, transparent fees and no added interest, penalties, or fees after a failed autopay. Its example fee ranges are guidance in that definition, not a substitute for local obligations.
Correct declarations and access
Use the Finance category and disclose repayment conditions, all fees, a representative cost, and data handling. Apply the shared loan data-access and country requirements where relevant.
Test the offer and failed-payment behavior in a safe setup. Give Google the provider documentation and terms that establish the product’s classification. If it is actually a personal loan, assess it under that policy instead of changing the label.
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: Earned wage access Checked 22 September 2026