How to Create a Google Play Developer Account

Creating a Google Play developer account is mostly paperwork, plus a US$25 fee. This guide shows first-time Android developers how to choose a Play Console account type, register it, complete verification, and plan for the testing rule that can delay a new personal account’s public release.

The account is where you manage your apps in Google Play Console. It is not a published app. You need it before you can upload or release an app.

What you need before creating a Google Play developer account

Start with the person or business that will own the account long term. Google requires the person registering for Play Console to be at least 18. Use a Google Account the real owner can keep. Do not use a contractor’s personal inbox or an address that will disappear after the project.

Have these ready:

Google lists MasterCard, Visa, American Express, Discover in the United States, and Visa Electron outside the United States as accepted registration cards. Prepaid cards are not accepted. Card availability can vary by location. Google says it will not refund the registration fee if it cannot verify the identity details it requests. Read the current Play Console sign-up requirements before you pay.

What organization accounts need in addition

An organization developer account normally needs a D-U-N-S number. This is a nine-digit business ID from Dun & Bradstreet. Google has other verification paths in limited cases, including some government organizations and regions that Dun & Bradstreet does not support. Check whether your organization already has one before you request another. Google says a new number can take up to 30 days.

You also need the organization name, address, phone number, website, and contact person’s details. They must match the linked Google payments profile. Small differences in legal names and addresses can stop verification.

The Google Account that starts the account should be one your business can still control after the launch party is over.

Choose Personal or Organization before you sign up

Personal and Organization accounts have the same Play Console features. Both can earn money through a payments profile. The difference is who the account represents and what Google needs to verify.

When a Personal account fits

Choose Personal when the account is truly for you. This includes students, hobbyists, and independent developers publishing in their own name. You can still earn money and invite others to help manage the account.

For a personal account, Google collects your legal name and address through the Google payments profile. Your developer name can be different and is changeable. Google displays your legal name, country, and developer email address on Google Play. If you monetize, it displays your full address too.

When an Organization account fits

Choose Organization when you are publishing for a business, nonprofit, professional practice, or government body. Google says financial services, health apps, apps approved to use VpnService, and government apps must use an Organization account.

Organization accounts normally need a D-U-N-S number and business details that agree with the linked payments profile. On Google Play, Google displays the organization’s legal name, legal address, developer email address, and developer phone number.

Keep Google contact details separate from public developer details

Google collects two sets of contact details. Your account contact email and phone number let Google contact you about the account. Users cannot see them. Your developer email, and your developer phone number for organizations, appear on Google Play. You must verify all of them and keep them active.

The fields are close together, so this split is easy to miss. Give each field an owner and use an inbox someone monitors. A shared business mailbox is often safer than the personal address of the person registering today.

Create your Play Console account in five steps

1. Go to Play Console sign-up and sign in with the long-term account owner. Create the Google Account first if needed.
2. Read and accept the Google Play Developer Distribution Agreement. This is the agreement that covers distributing apps on Google Play.
3. Select Personal or Organization. Link or create the Google payments profile that holds the legal identity for the account.
4. Enter the developer name, legal details, Google contact details, and public developer contact details requested for that account type. For organizations, enter the D-U-N-S number if prompted and the business information.
5. Pay the one-time US$25 registration fee with an accepted card.

Do not rush through a field because you plan to change it after launch. The legal name and address in the payments profile are part of identity verification. Organization details must match the Dun & Bradstreet record when one is used.

Complete verification without creating a mismatch

After registration, complete the verification prompts in Play Console. The steps vary by account type. Google may ask you to verify your identity, email, phone number, payments-profile information, and, for new personal accounts, access to an Android device through the Play Console mobile app.

Before you submit a document or confirm a field, compare four places: your ID, Google payments profile, D-U-N-S record if it applies, and Play Console entry. The legal name and address should match. For an organization, use the D-U-N-S record for the entity that will own the account, not a parent company or a related company.

Google’s required account information guide explains which details are public and which are only for Google. It also says organization accounts can be restricted if their verified name or address no longer matches the D-U-N-S profile, so update both records when the business changes.

A developer name is branding. A legal name and address are verification. Treating them as interchangeable is how a five-minute form turns into a support ticket.

What new Personal accounts must do before a public release

Account registration does not automatically open the Production track. For Personal developer accounts created after November 13, 2023, Google requires app-level testing before the app is eligible for public distribution.

Run a closed test with 12 testers for 14 continuous days

Set up the app in Play Console, then create a closed test. At least 12 testers must opt in and stay opted in for 14 continuous days. A tester who opts out no longer counts for that period, even if they later join again. Each tester needs a full, uninterrupted 14 days.

Internal testing is optional and useful for a small trusted group. It does not replace the closed-test threshold. Open testing becomes available after you gain production access.

Apply for production access after the test

Once the test meets the requirement, open the Play Console Dashboard and select Apply for production. Google asks about your closed test, your app or game, and production readiness. Be ready to describe tester activity, feedback, changes you made, and why the app is ready.

Meeting the 12-tester and 14-day threshold makes you eligible to apply. It does not guarantee approval. Google reviews the application and says the review usually takes seven days or less, though it can take longer. Keep the closed test running if Google asks for more testing.

The official testing requirements for new personal accounts also reminds developers that production access is separate from policy review. You still need correct store listing information, app content declarations, a privacy policy where required, and working review access for any sign-in flow.

Avoid the setup mistakes that delay a first release

The costliest registration mistake is choosing the fastest form instead of the right owner. If a company is publishing, register it as an Organization and prepare its D-U-N-S record first when required. Do not use a Personal account with company details mixed into it.

Next, keep verification simple. Use legal information that matches across the ID, payments profile, and business record. Monitor the Google contact channels, and do not confuse them with the public developer email that users see.

Finally, plan for two separate jobs: registering the account and preparing the app. A completed Play Console account lets you start publishing work. It does not skip closed testing, production-access review, or the app’s policy review. If Play Console stops you later, start with this guide to common Google Play Developer Console errors.

A Play Console account lets you begin publishing work. It does not skip the app review and testing work that follows.

FAQ

Is the Google Play developer account fee recurring?

No. Google lists a US$25 one-time registration fee for a Play Console developer account. The accepted card types and local availability can change, so check the current registration page before paying.

Do I need a D-U-N-S number?

Organization accounts normally need one. Personal accounts do not. Google has alternative verification paths for some government organizations and regions that Dun & Bradstreet does not support. Otherwise, if your organization does not have a D-U-N-S number, Google says to request one from Dun & Bradstreet and plan for the wait before registration.

Can I change from Personal to Organization later?

Choose carefully before registration. Google’s sign-up guidance describes separate account types and verification details, but does not present a self-service conversion in the registration flow. If ownership or business structure changes, use Play Console Help to ask about the appropriate transfer or account path rather than assuming a profile edit will change the account type.

Do all new Personal accounts need 12 testers?

The rule applies to Personal developer accounts created after November 13, 2023. Before applying for production access, the app needs at least 12 testers opted in continuously for 14 days.

How long does identity verification take?

Google does not give one universal verification time in its account-creation guidance because requests and checks vary. Complete each prompt promptly, make the legal details match, and do not schedule a launch around an assumed approval date. After you apply for production access, Google says that review usually takes seven days or less, but can take longer.

Conclusion

Use the account type that matches the real owner. Prepare matching legal and contact details, and allow time for a D-U-N-S number if your organization needs one. Treat account registration and app release as separate tasks. Plan the closed test before you set a launch date.

Further reading: How to publish an app on the Google Play Store and how to fix common Google Play Developer Console errors.