Developer account verification problems and how to resolve them

Most verification problems on a new Google Play developer account come from one of three checks: identity verification (your ID or organization documents), device verification (proving you have a real Android phone), or contact verification (email and phone codes). Each has its own rules, and knowing which one is stuck is half the fix.

This article covers what each check requires according to Google's help pages and what usually goes wrong. It doesn't cover the closed-testing rule itself, which only starts once your account is ready.

First, know which account type you have

Requirements differ between Personal and Organization accounts. Organizations need a D-U-N-S number, an organization website and a phone number, and they provide extra documents. If you're not sure which type fits you, or which one the 12-tester rule applies to, read personal vs organization developer accounts first.

Two basics apply to everyone: there's "a US$25 one-time registration fee", and you must be "at least 18 years of age".

Identity verification

Google asks developers to verify who they are:

• Personal accounts without a verified payments profile provide an official government ID.
• Organization accounts provide a D-U-N-S number, a government ID and an organization document.

Accepted documents vary by country. Google keeps a list of accepted documents by country, so check it before uploading anything.

Common problems

• Name mismatch. The legal name on the account doesn't match the ID exactly. Check spelling, order of names and any middle names.
• Wrong document type. A document that's accepted in one country may not be in another. Use the country list.
• Unreadable upload. Blurry photos, glare, cropped edges or expired documents. Take a fresh, flat, well-lit photo of the whole document.
• Address details. The address you entered doesn't match your documents or payments profile.

Don't ignore verification requests. Google says accounts that aren't verified can have their apps removed. The full process is described on Google's verify your identity page.

D-U-N-S problems (organization accounts)

If you're registering as an organization, the D-U-N-S number is a frequent bottleneck:

• Google notes that applying for a D-U-N-S number "is a completely free process". If someone asks you to pay for it, you're not dealing with the official route.
• It can take up to 30 days to get one, so start early.
• The organization name and address in your D-U-N-S record should match what you enter in Play Console. Fix the record first if they differ.

Device verification

Since early 2024, new personal accounts must "verify that they have access to a real Android mobile device using the Play Console mobile app" before they can make apps available. The task appears on the Home page of Play Console.

Google's rules for the device:

• it must be a "non-rooted physical Android mobile device that runs at least the Android 10"
• you complete the check with the Play Console mobile app
• the same device can verify multiple accounts

Common problems

1. Using an emulator. It has to be a physical phone. Emulators don't qualify.
2. Rooted or modified phone. A rooted device won't pass. Use a stock, unrooted phone.
3. Android version too old. The device must run Android 10 or later.
4. Wrong Google account in the app. Sign in to the Play Console mobile app with an account that has access to your developer account.
5. Not finding the task. Look on the Play Console Home page, not in the app settings.

If you don't own a suitable phone, borrowing one from a friend or family member is fine, since the same device can verify multiple accounts. Details are on Google's device verification page.

Contact verification

Your contact details are verified with a one-time password. Problems here are usually simple:

• the code went to spam or a different inbox
• the phone number was entered without the right country code
• the code expired before you used it, so request a new one

Don't confuse this with Android developer verification

Separately from Play Console, Google announced in August 2025 that apps on certified Android devices must come from verified developers, including apps installed outside Google Play. Google's rollout post says that from September 30, 2026, apps must be registered by verified developers to be installed and updated on certified devices in Brazil, Indonesia, Singapore and Thailand, with global expansion in 2027.

For Play developers, Google says: "If you've completed Play Console's developer verification requirements, your identity is already verified and we'll automatically register eligible Play apps for you." In other words, if your Play Console verification is complete, Google says it will automatically register your eligible Play apps. Apps you distribute outside Play may still need their own registration.

This program is separate from the closed-testing requirement. Being verified doesn't replace the 12 testers for 14 days, and running a closed test doesn't verify your identity.

What comes after verification

Once your account is verified, the usual path is:

1. Set up your app and complete the App content declarations.
2. Create a closed testing track and upload your first build.
3. Run a closed test with at least 12 opted-in testers for 14 continuous days (for personal accounts created after November 13, 2023).
4. Apply for production access.

Our closed testing explainer covers step 3, and the setup guide shows the tester invite steps if you use GoPlayTester. When you're verified and need testers, you can order here.