Google Play Developer Account Verification for Organizations

Diese Seite auf Deutsch

Short answer

Every Google Play developer account has to pass identity verification before it can publish. Organization accounts need a D-U-N-S number whose legal name and address match what you enter in Play Console, plus verified contact details. New personal accounts verify an individual and must run a closed test with opted-in testers before they can apply for production access.

Personal or organization account: decide first

Play Console asks at sign-up whether the account belongs to a person or an organization. The choice determines which checks you go through and how your apps appear in the store, so it is worth getting right before anything else.

AspectPersonal accountOrganization account
Intended forIndividual developers, hobby projectsCompanies, agencies' clients, public bodies, associations
Identity proofThe individual's legal name and IDD-U-N-S number plus the verified identity of the contact person
Closed test before productionRequired for newly created accountsNot required
Legal owner of the appsThe individualThe organization

If the app is a business product, choose an organization account even if it takes longer. Users, procurement teams and app reviewers expect the publisher to be the company, and changing the account type later is possible only with extra effort – often it means creating a new organization account and transferring the apps.

What Google checks for organizations

  1. D-U-N-S number: a nine-digit identifier issued by Dun & Bradstreet. Google uses it to confirm the organization exists.
  2. Legal name and address: must match the D-U-N-S record exactly, including the legal form (Inc., LLC, GmbH and so on).
  3. Contact details: a contact name, email address and phone number, each verified separately.
  4. Organization website and phone: requested during sign-up and used for public contact information.
  5. Additional documents: Google may ask for official registration papers if the automated checks do not match.

Parts of this information, such as the developer name and contact email, appear on your store listing. Plan for that before you enter a personal mobile number or a private address.

Getting the D-U-N-S number right

Most verification delays come from the D-U-N-S record, not from Google. Look up your organization in the Dun & Bradstreet directory before you start. Many companies already have a number without knowing it. If the record shows an old address, a trading name instead of the legal name or a missing legal form, ask Dun & Bradstreet to correct it first and wait until the change has propagated. Requesting or correcting a number is free but can take from a few days to several weeks.

If you also publish on iOS, the same D-U-N-S number is used for Apple's organization enrollment, so one clean record serves both stores.

Personal accounts and the closed testing rule

Newly created personal accounts must run a closed test before they can request production access. Google currently requires a minimum number of testers who stay opted in for a set number of consecutive days, and then reviews your answers about the test. You may also be asked to confirm access to a physical Android device. Our guide to the Google Play closed testing requirement explains how to run that test so it counts.

Typical pitfalls

  • Registering the account with an employee's private Google account. When that person leaves, access leaves with them.
  • Letting an agency or freelancer register the account in their own name. Ownership of the app listing then sits outside your organization.
  • Choosing a personal account to avoid the D-U-N-S step, then discovering the closed test and the transfer effort later.
  • Entering a shortened company name that does not match the D-U-N-S record.
  • Leaving an account unused for a long time. Google may close inactive developer accounts.

Use a dedicated Google account that the organization controls, protect it with 2-Step Verification and invite team members and service providers through Play Console's user permissions instead of sharing the login.

How jocapps helps

Account creation and identity verification stay with you, because Google verifies the legal owner. Once the account exists, appsubmitter.io takes over the release work: AI-assisted checks, signing, CI/CD setup, submission and hands-on help with rejections – all inside your own developer account, so ownership never moves. If you are planning a broader launch, see our app store launch service.

Unsure which account type fits your setup? Book a free 30-minute intro call via the meeting planner.

Frequently asked questions

How long does Google Play organization verification take?

Google's own checks often finish within days, but obtaining or correcting a D-U-N-S number can take several weeks. Start with the D-U-N-S lookup before you open Play Console.

Do organization accounts need the closed test with testers?

No. The closed testing requirement before production access applies to newly created personal accounts. Organization accounts can still use closed testing voluntarily, which is good practice.

Can an agency publish our app in its developer account?

It can, but the app then belongs to the agency's account. It is usually better to own the account yourself and give the agency user permissions in Play Console.

Is the same D-U-N-S number used for Apple?

Yes. Apple also uses D-U-N-S numbers to verify organizations, so one correct record covers both stores.

Guides on this topic

Talk to us about your project

Honest advice on your idea, prototype or app.

  • 30 minutes
  • Free
  • No obligation

Book a free call [email protected]