Google Play Developer Account Verification Guide

Personal or organization account: the choice that sets your timeline

Google offers two account types. Each one is verified differently and reaches production at a different speed. The comparison below comes from Google's Play Console Help pages on developer verification requirements, D-U-N-S numbers and testing requirements for new personal accounts. For each point, here is how the two accounts compare:

• Who it's for. Personal account: an individual publishing under their own name. Organization account: a registered company.
• ID required. Personal account: a government ID. Organization account: a government ID plus an official organization document.
• D-U-N-S number. Personal account: not needed. Organization account: required (government bodies are exempt).
• Website verification. Personal account: not needed. Organization account: required, through Google Search Console.
• Android device check. Personal account: required, through the Play Console app. Organization account: not listed.
• Closed test before launch. Personal account: 12 testers opted in for 14 days in a row (accounts created after 13 November 2023). Organization account: not required.
• Production access review. Personal account: usually 7 days or less, per Google. Organization account: not required.
• Slowest step. Personal account: the closed test plus the review. Organization account: getting the D-U-N-S number.

A simple way to decide

Apple's developer program uses the same nine-digit D-U-N-S number. If you plan to ship on iOS too, one application covers both stores. Pick your path based on where you are today:

• You have a company and investors or customers will see the listing: go organization. The store shows your company name instead of your personal name.
• You don't have a company yet and want to test the market: a personal account works. Plan for the closed test from day one.
• You have a company but no D-U-N-S number yet: check the Dun & Bradstreet lookup today. If you have no number, apply now. It's free. Google warns about third-party services that charge for it.

How to verify a Google Play developer account: personal account

Follow these steps in order:

• 1. Create the account in Play Console with a Google account you control. You must be at least 18.
• 2. Pay the $25 one-time registration fee.
• 3. Link a Google Payments profile. The legal name and address on it must match your ID.
• 4. Upload a government ID.
• 5. Verify your developer email and phone number.
• 6. Install the Play Console app on an Android phone and confirm device access.
• 7. Upload your app to a closed test and get at least 12 testers to opt in. Each one must stay opted in for 14 days in a row.
• 8. Apply for production access from the Play Console dashboard. Google says the review usually takes seven days or less.

How to verify a Google Play developer account: organization account

Follow these steps in order:

• 1. Get your D-U-N-S number first. You can't create the organization account without it.
• 2. Create the account and pay the $25 fee.
• 3. Link a Google Payments profile with the company's exact legal name and address, as listed with Dun & Bradstreet.
• 4. Upload a government ID and an official organization document.
• 5. Verify the public developer email and phone number. These appear on your store listing.
• 6. Verify your website. Register it in Google Search Console, add the URL in Play Console, and send the verification request. If the same Google account owns both, approval is automatic. If not, the Search Console owner gets a request to approve.

How long does Google Play developer verification take?

In practice, a personal account can't reach production in less than about three weeks from the first tester opting in. An organization account with a D-U-N-S number in hand skips the testing rule completely. This matters when you plan a build. Our MVP Development package is Fixed at $3,460, delivered in about 20 days, with App Store and Google Play submission support. Start your account work on day one of the build, not on launch day, so the app is not left waiting on the account. Here is a realistic timeline built from Google's own figures:

• D-U-N-S number: up to 30 days, according to Google. This is the longest step, and it happens outside Google.
• Identity and contact checks: Google doesn't publish a fixed time. Most of the wait here comes from mismatched details being sent back for correction, not from the review itself.
• Closed test (personal accounts only): 14 days minimum, and only if all 12 testers stay opted in the whole time.
• Production access review (personal accounts only): usually seven days or less, sometimes longer.

Why verification gets stuck: 6 common blockers

These six blockers are the ones that stall founders right before launch. Not sure your setup is right? Book a call. It's a free 30-minute call.

• 1. Name or address mismatch. The Payments profile says "Acme Ltd", Dun & Bradstreet says "Acme Limited", or the address formats differ. Google flags the mismatch by email and banner and gives you a deadline to fix it. Copy the D&B record word for word.
• 2. The website is verified with a different Google account. Then the request goes to someone else's inbox, often a former web agency. Check who owns the site in Search Console before you send the request.
• 3. Testers drop out before day 14. Google is clear: testers who opt in, test for fewer than 14 days and then opt out don't count. Recruit more than 12 so one dropout doesn't restart your clock.
• 4. No Android phone. Personal accounts must confirm device access with the Play Console app. Founders on iPhone often find this out in launch week.
• 5. The account was opened by a freelancer. If a developer created it with their own Gmail and ID, the account belongs to them. Moving it later is painful. Open it yourself, in your name or your company's, then invite your developer as a user in Play Console.
• 6. Paying someone for a D-U-N-S number. It's free from Dun & Bradstreet. Paid services don't make Google accept you faster.

What you do yourself and what your developer can do

Verification is tied to your identity, so some steps can't be handed over. This keeps the account and the app in your hands. The code lives on your GitHub, and the store accounts should be yours too. If your app gets past verification but is then rejected, our guide on fixing and resubmitting a rejected Android MVP walks through the next step. You'll find more Android launch guides in our Android and Google Play topic. Here is how the work splits between you and the BuildMVPFast team:

• You do it (only you can): create the account and pay the fee, upload your ID and company documents, get the D-U-N-S number, verify email, phone and device, own the website in Search Console.
• What our team covers: design included, Google Play submission support, progress shown every week, 2 weeks of fixes after launch, code 100% yours on your GitHub.

A new rule for apps outside Google Play

Google is extending developer verification beyond Play. From 30 September 2026, apps installed on certified Android devices in Brazil, Indonesia, Singapore and Thailand must come from verified developers. Google says the requirement expands globally in 2027 and beyond, per its Android developer verification page. If you publish on Google Play and your account is verified, check your Play Console home page to confirm your apps are registered.

How long does Google Play developer account verification take?

Google doesn't publish one fixed time for the identity check. The long waits are elsewhere: up to 30 days for a D-U-N-S number and, for new personal accounts, a 14-day closed test plus a production review that usually takes seven days or less.

Do I need a D-U-N-S number for a Google Play developer account?

Only for an organization account. Personal accounts don't need one, and government organizations are exempt. The number is free from Dun & Bradstreet.

Why is my Google Play developer account verification failing?

The most common causes are a legal name or address that doesn't match your ID or D&B record, a blurry or expired ID, and website verification sent from a Google account that doesn't own the site in Search Console. If your details can't be verified, Google keeps the $25 fee.

Do organization accounts need 12 testers for 14 days?

No. That rule applies to personal accounts created after 13 November 2023. Organization accounts can publish to production without the closed test requirement. Want your Android app live without losing weeks to account setup? Book a call. It's a free 30-minute call.