Did Google Play change developer account verification details?

Did Google Play change what verification details are required when creating a developer account

Yes. Google Play now asks for a defined set of verification details when you create a developer account, and the required details differ for personal and organization accounts. The change is not just cosmetic, because the account type determines what Google verifies, what it shows on Google Play, and what must stay current after creation. Google’s Help Center says new accounts must provide verified contact details, and that the information collected depends on account type.

For a personal account, Google Play says you must provide a developer name, legal name, legal address, contact email address, contact phone number, and a developer email address. The legal name and address come from the linked Google Payments profile, and Google says those identity details must be verified before publishing. Google also says the contact email address and contact phone number are verified with a one-time password.

For an organization account, Google Play asks for more. Google says you need a developer name, organization name, organization address, organization phone number, organization website, contact name, contact email address, contact phone number, developer email address, and developer phone number. Google also ties the organization’s legal identity to the Google Payments profile, and says the developer email and phone number are shown on Google Play for transparency and user safety.

The part people often get wrong is thinking the app-store listing fields are the same thing as the account verification fields. Google separates them. The contact email and contact phone number are for Google to reach the account owner. The developer email address, and for organizations the developer phone number too, are part of the developer profile that users may see on Google Play. Google says these details must be verified and kept operational for the life of the account.

Another common mistake is assuming the old sign-up experience still applies. Google says it announced a verification policy update in July 2023, and it now requires developers to complete a verification process. It also says newer personal accounts may face additional device verification before apps can be made available on Google Play. That is a separate requirement from identity verification, so a finished account creation flow does not always mean the account is ready to publish.

The inconvenient part is that the details are not just collected once and forgotten. Google says the contact information must remain active, accurate, and verified, and updates to phone numbers can require phone verification again. If your developer identity or contact information changes later, Google says you must update Play Console so your account does not become restricted and your apps are not removed.

If you are creating a personal account, the practical checklist is simple: make sure the legal name and address on your Google Payments profile are correct, then use contact email and phone details that will stay reachable. If you are creating an organization account, confirm the organization’s official name, address, website, and contact channels before you start, because Google may ask for extra proof tied to the organization’s real-world identity.

If you are unsure which path you are on, stop at the account-type step and decide first. Google says the selection between personal and organization affects which verifications you must complete, and that choice cannot be changed later for that account. That is the point where many teams lose time, because they try to fix a mismatch after the payment profile and verification steps are already in motion.

If you are building a Play-ready workflow around this, the right approach is to collect the verified account details before you create the account, then keep the contact channels monitored after setup. That is the same pattern DevConnect uses for app testing coordination, where the goal is a reliable exchange between builders rather than a shortcut around platform rules: https://devconnectplatform.com.

In short, Google Play did change the required verification details, and the current rules are stricter about identity, contact information, and account type. Personal accounts and organization accounts now have different required fields, and both must keep verified contact details current after creation.