Google Play Developer Verification 2026 — What Every New Developer Needs to Know

Google is rolling out mandatory developer verification for all Play Console accounts, phasing it in through 2026 and 2027. If you publish Android apps — or plan to — this affects you directly. The verification requirement works alongside the 12-tester, 14-day Closed Testing mandate, and together they form a two-layer gate that every new developer must pass.

What Changed and When

Before 2026, creating a Play Console account was straightforward: pay a $25 one-time registration fee, provide an email address and a name, and you had an account. Google had no way to verify whether you were who you claimed to be. This made it easy for malicious actors to create developer accounts under fake identities, publish scam apps, and disappear when banned — only to create a new account under a different fake name.

The new verification system is modeled on what Apple has required for years on the App Store. Starting September 2026, all new personal developer accounts must complete identity verification. Organization accounts already require D-U-N-S numbers and business documentation, but the verification bar for both account types is rising.

The key dates:

• September 2026: Mandatory identity verification for all new personal Play Console accounts. No new account can reach production without completing verification.
• Early 2027 (expected): Existing developer accounts from before September 2026 must complete verification. Google will provide account-specific deadlines — expect 6-12 months of notice.
• Unknown date (2027+): Google may extend verification to accounts in all countries. The initial rollout focuses on accounts in higher-risk regions, but Google plans global coverage.

What Personal Account Verification Requires

For personal accounts, verification requires three things: identity proof, address proof, and phone verification. These must all be consistent — the name on your ID must match the name on your Play Console profile exactly, and the address on your documents must match the address you registered with.

Government-issued photo ID: Passport, driver's license, or national identity card. The document must be current (not expired), clearly legible (no glare, no blur), and show your full legal name. If your ID includes a middle name, your Play Console profile must include it too. Google cross-references the name field character by character.

Proof of address: A utility bill (electricity, water, gas, internet), bank statement, or government-issued document showing your name and physical address. The document must be dated within the last 90 days. Google rejects PO Box addresses — you need a physical street address. If you live in a country where utility bills are not in your name, a rental agreement or government tax document can sometimes substitute, but acceptance varies.

Phone verification: A phone number that can receive SMS or voice calls for a one-time verification code. This number does not need to match your address country, but it must be a real, active number that you control.

Organization Account Verification: D-U-N-S and Beyond

Organization accounts require a D-U-N-S number from Dun & Bradstreet. This is a 9-digit business identifier that is free to obtain through Google's partnership with D&B — do not pay any third-party service for "expedited" processing. The standard timeline is 1-5 business days. Google prioritizes Play Console D-U-N-S requests, so they typically come through faster than the 30-day window for general business D-U-N-S requests.

Beyond the D-U-N-S number, organization accounts need: business registration or incorporation documents from a government authority (trade license, certificate of incorporation, or equivalent), proof of the organization's physical address (not a registered agent address), and verification of the authorized representative — the person who signs legal agreements on behalf of the company. This person must provide their own personal ID and must be listed on the business registration.

The most common failure point for organization verification: the business legal name on the registration documents does not match the name entered in Play Console. Use the exact legal name from your incorporation certificate — not a trade name, not a DBA, not a shortened version.

How Verification and Closed Testing Work Together

Verification and Closed Testing are sequential requirements. The full workflow for a new developer after September 2026:

1. Create your Play Console account and pay the $25 registration fee.
2. Complete identity verification — this may take 2-5 business days. Your account is in a limited state during this period. You can upload builds and set up your store listing, but you cannot publish to any track.
3. Once verified, upload your app to the Closed Testing track.
4. Recruit 12 testers and complete 14 consecutive days of active testing.
5. Complete the production access questionnaire and submit for review.

The total time from account creation to production is approximately 3 weeks: up to 5 business days for verification, plus 14 days for Closed Testing, plus 1-3 days for production access review. Plan accordingly.

Should You Create Your Account Before September 2026?

If you know you will publish an Android app at any point in the next year, create your Play Console account now. Accounts created before the September 2026 cutoff will have a grace period — likely through mid-to-late 2027 — to complete verification. This means you can start your Closed Testing period without waiting for the verification step, and your app can reach production faster.

Creating your account now costs $25 (the one-time registration fee) and locks in the pre-verification timeline. Even if you are not ready to publish immediately, having an active developer account means you avoid the September bottleneck. When thousands of developers rush to create accounts and complete verification simultaneously, processing times will spike. An account created in July 2026 that has already completed or is exempt from immediate verification will not be stuck in that queue.

If you wait until after September 2026 to create your account, budget an extra week for verification processing and ensure all your documents are scanned, current, and consistent before starting. A rejected verification resets the clock — fix the issue and resubmit, adding another 2-5 business days.