Google Play developer account requirements: personal vs organization

Google Play has two account types: personal and organization. Both can publish and earn money. Organizations must provide a free D-U-N-S number; personal accounts verify an individual's identity and, when new, access to a real Android phone. And only personal accounts created after November 13, 2023 have to pass the closed test with 12 testers for 14 days.

Here's what each type requires, and how to pick.

Which account type fits you

Google's guidance (Play Console Help):

• Personal account: "if you're a student, hobbyist, or amateur developer." You can still earn money, invite others to your account and manage your apps.
• Organization account: "if you're engaged in commercial, industrial, professional, or governmental activities."

Some apps require an organization account, whatever your size:

• Financial products and services (banking, loans, stock trading, investment funds, crypto wallets and exchanges).
• Health apps, such as medical apps and human subjects research apps.
• Apps approved to use the VpnService class.
• Government apps.

If your app falls in one of these, plan for an organization account and its D-U-N-S delay from day one.

What a personal account asks for

When you create a personal account, Google asks for (Play Console Help):

• A developer name (shown on Google Play, can differ from your legal name, can be changed later).
• Your legal name and legal address, taken from the Google payments profile you link.
• A contact email and contact phone for Google to reach you.
• A developer email, shown on your Google Play profile.

Each email and phone number is verified with a one-time code and must keep working for the life of the account. You'll also verify your identity details before you can publish.

What the public sees: your legal name, your country and your developer email. If you monetize, Google also shows your full address. Some regions require extra details, such as a phone number.

What an organization account asks for

Organizations provide (Play Console Help):

• A D-U-N-S number, plus organization name and address matching your payments profile.
• Organization phone number and website.
• A contact name, contact email and contact phone.
• A developer email and developer phone, both shown on Google Play.

Google insists on two points about D-U-N-S:

1. It's free. "Applying for a D-U-N-S number through Dun & Bradstreet is a completely free process. Be aware of third-party services that may attempt to charge high administrative fees."
2. It takes time. "This process can take up to 30 days so you should plan ahead." You can't create an organization account without one. Check first whether your company already has a number.

If Dun & Bradstreet doesn't operate in your region, you can ask Google support for another verification method before creating the account. Government agencies can also ask support.

Once the account exists, keep the name and address in your payments profile identical to your Dun & Bradstreet profile. Google says a mismatch triggers the banner "Your organization name or address is no longer verified", and an unfixed mismatch can lead to restrictions that remove all your apps.

Device verification for new personal accounts

New personal accounts must prove they have a real Android device before publishing (Play Console Help):

1. Sign in to Play Console on the web as the account owner.
2. On the Home page, open the task "Verify that you have access to an Android mobile device".
3. Scan the QR code to install or open the Play Console mobile app.
4. Sign in as the account owner, select your developer account, tap Verify.

The device must be a non-rooted physical Android phone running Android 10 or later. Google says it takes less than a minute, the phone number of that device isn't used, and the same device can verify several accounts.

Fees and payments

Google's developer verification FAQ refers to "Play's $25 registration fee" (Android Developers).

If you plan to sell apps or in-app items, you'll also add and verify a payment method in the payments profile. Google says that verification "can take up to 5 days" (Play Console Help). Start it early.

Which accounts must run a closed test

The rule is scoped by account type and creation date (Play Console Help):

• Personal account created after November 13, 2023: yes. You need a closed test with at least 12 testers opted in continuously for 14 days, then a production access application. Until then, Production and Pre-registration stay disabled.
• Personal account created on or before that date: the rule's wording doesn't cover it.
• Organization account: Google's page doesn't mention it.

Production access is requested per app, from that app's Dashboard. Google doesn't describe any exemption after your first app, so plan a closed test for each new app on a new personal account. The rule in full: The 12 testers, 14 days rule explained.

Should you pick an organization account just to avoid testing? Only if you really are an organization. You'll need a D-U-N-S number, your address and phone number become public, and Google's definitions are clear about who each type is for.

Android developer verification

Separately, Google now requires apps on certified Android devices to be registered by verified developers, starting with four countries on September 30, 2026. For most Play developers, Google says the identity verified in Play Console already meets this, and apps you create in Play Console are registered automatically (Android Developers). Details in Android developer verification 2026.

Checklist before you create the account

1. Decide the type. Check whether your app category requires an organization account.
2. Organization: get or find your D-U-N-S number first (up to 30 days).
3. Use contact details you'll keep for years. Google may check that the account is active.
4. Have a non-rooted Android 10+ phone ready for device verification (personal accounts).
5. Personal account: budget time for the closed test before launch. The steps are in How to set up a closed test.

For the whole path from account to production, read the Google Play closed testing guide.