Yara TestersProduction Guaranteed
Play Console3 min readUpdated November 5, 2026

How to create a Google Play developer account

Personal vs organization accounts, the registration fee, identity verification, and the setup details that cause problems later.

Creating a Google Play developer account is straightforward. Creating one that does not create a verification problem three weeks later takes a little more care.

Here is the practical setup path.

Choose the account type first

Google Play offers personal and organization developer accounts.

Personal is for an individual developer. It usually requires identity verification and is the type most affected by the 12-tester closed-testing rule for accounts created after 13 November 2023.

Organization is for a company, studio, or institution. It typically requires organization details and may require a D-U-N-S number. Organization accounts are generally not covered by the 12-tester requirement, but they have their own verification checks.

Choose based on who owns the app and how you will operate. Do not choose organization just to avoid testing if you are an individual developer; mismatched details can cause bigger issues.

What you need

  • a Google account you will use for Play Console;
  • a payment method for the one-time registration fee;
  • your legal name and address;
  • a phone number;
  • government ID for personal verification;
  • a non-rooted physical Android device running Android 10 or later, for personal-account device verification;
  • organization details and documentation if applicable.

Use accurate information. The name on your ID, your payment profile, and your developer profile should line up.

The registration flow

  1. Go to the Google Play Console and sign in.
  2. Accept the developer agreement.
  3. Pay the one-time registration fee.
  4. Complete your developer profile.
  5. Complete identity verification.
  6. Complete device verification from the Play Console mobile app if you have a personal account.
  7. Set up your payment profile if you plan to sell paid apps or in-app products.

Google controls the exact screens and fees. Check the current Play Console for the latest amount and requirements.

The details that cause problems

Name mismatches

If your ID says one name and your payment profile says another, verification can fail. Use your legal name consistently.

Address mismatches

Your address should match the documents you provide. A virtual address or a friend's address can create a mismatch that is hard to explain.

Duplicate accounts

Do not create a second developer account to get around a rejection, suspension, or verification problem. Google can link accounts, and duplicate accounts can make the situation worse.

Shared accounts

Do not share your Google account password with a freelancer or agency. Use Play Console permissions to give access instead. If you already share credentials, change the password and set up proper access.

Skipped device verification

New personal accounts may need to confirm access to a real Android device before publishing. It is easy to miss because it lives in the Play Console mobile app, not the web sign-up flow. Read device verification for a new Play account.

Unverified payment profile

If you plan to charge for your app, complete the payment profile before you need it. A missing payment profile can block paid app setup later.

After the account is created

Before uploading your first app:

  • enable two-step verification on the Google account;
  • review the developer distribution agreement;
  • set up user permissions if you work with a team;
  • decide on your app's package name and signing strategy;
  • check for device verification and package name registration tasks on the Play Console home page;
  • read the current testing requirements for your account type.

If verification is rejected

Do not keep resubmitting the same documents. Read Play Console verification rejected and fix the specific mismatch first.

The short version

  • Choose personal vs organization based on reality, not a shortcut.
  • Use consistent legal details.
  • Pay the registration fee and complete verification.
  • Do not create duplicate accounts.
  • Use permissions instead of sharing passwords.
  • Complete your payment profile early if you need it.

Next: Play Console verification rejected or publish your first app.

Our team’s note

If this answered the question but your situation still feels messy, send us the screenshot or the rejection email. Some things are easier to solve in a two-minute conversation than another article.

Order testing