All Collections
Releases
๐Ÿค– Google PlayStore
Verification of existing Play Console developer accounts
Verification of existing Play Console developer accounts

In order to make the PlayStore a more secure area, all developers must now have themselves confirmed - here are instructions.

Dominik avatar
Written by Dominik
Updated over a week ago

What Apple has been doing in its developer program for years is now also being introduced by Google: developers have to verify themselves. This is about striving for transparency and protection against dangers for potential app users.

If you created your store account after September 2023, this is no longer valid. Verification has already taken place.

Everyone else must now prepare for the verification process - there are no restrictions for the developer account until verification.

Step 1: Choose an appointment

When you log in to the Google Play Console, you will be notified of the need to select a verification deadline. Don't worry, the earliest possible deadline is September 24, 2024 - and then monthly until January 24, 2025.

If no date is selected by February 29, 2024, Google itself will set a deadline for your account verification. So be early enough so that you have it in your own hands.

Attention: If you completely ignore the verification request (i.e. also let the final deadline pass), Google has the right to permanently remove your apps and your store account.

After you have selected an appointment, you will be asked for the account type. By default, you must enter "Organization account" here. You will also be asked for a D-U-N-S number - if you have already created a store account in the Apple AppStore, you should already have this. Otherwise, please ask our Release Manager Dominik Leitner (dol@ovos.at) - he has an overview of all D-U-N-S numbers.

Step 2: Gather the necessary information

Note: Collect this information up to 60 days before your deadline. It is good to have all the information at hand for the verification process (step 3).

Required information for verifying a personal developer account

When account verification is available in Play Console, you'll need to provide:

  • Legal name (shown on Google Play)

  • Legal address (country shown on Google Play)

  • Contact email address (verified using one-time password)

  • Preferred locale for email communications

  • Contact phone number (verified using one-time password)

  • Developer email address (shown on Google Play)

Additional information for personal developer accounts:

  • Developer website (optional)

Required information for verifying an organization developer account

When account verification is available in Play Console, you'll need to provide:

  • Legal name (shown on Google Play)

  • Legal address (shown on Google Play)

  • Contact email address (verified using one-time password)

  • Preferred locale for email communications

  • Contact phone number (verified using one-time password)

  • Developer email address (verified using one-time password and shown on Google Play)

  • Developer phone number (verified using one-time password and shown on Google Play)

Additional information for organizations:

  • Organization type

    • Company/business

    • Non-profit

    • Academic institution

    • Government

  • Organization size

    • 1-10

    • 11-50

    • 51-100

    • 101-1000

    • Over 1k employees

  • Organization phone number

  • Organization website

Step 3: The actual verification process

The date selected in the first step is the deadline - so everything must be done by then. You can start two months beforehand. The steps of the actual verification process are now explained here:

  • Log in to the Google Play Console

  • Click on the blue button to verify your Google Play account.

  • Now follow all the following sections of the popup and upload the files you collected in step 2 to the appropriate location.

  • Finally, Google will send a verification code to the phone number provided - you will then need to enter this code to complete the verification.

Did this answer your question?