Required information to create a Play Console developer account

When creating your Play Console developer account, you must provide certain information which helps us to verify your identity. This article provides an overview of the information that you must provide, which differs between personal accounts and organisation accounts.

Creating a developer account for personal use

When creating a personal account, you must provide the following information:

  • Developer name; can be different from your legal name
  • Legal name 
  • Legal address 
  • Contact email address, for Google to contact you
  • Contact phone number, for Google to contact you 
  • Developer email address, shown as part of your Developer Profile on Google Play

Your developer name will appear on Google Play and can be changed at any time. 

Your legal name and address will be taken from the Google payments profile that you linked to your developer account during account creation. You will need to verify these identity details before publishing on Google Play. Learn more about verifying your developer identity information.

Google will display your legal name, your country (as per your legal address) and developer email address on Google Play. If you decide to monetise on Google Play, then Google will display your full address.

In certain regions, developers are required to provide additional information which may be displayed on Google Play, like their phone number or full address. Visit this Help Centre article to learn more.

Your contact email address, contact phone number and developer email address must be verified using a one-time password and remain operational for the duration of your developer account. Go to the best practices section below to find out more.

Creating a developer account for an organisation

When creating an organisation account, you must provide the following information:

  • Developer name; can be different from your legal name
  • As per your linked Google payments profile:
    • D-U-N-S number (if your developer account is for a government organisation or agency, view the section below)
    • Organisation name 
    • Organisation address
  • Organisation phone number
  • Organisation website
  • Contact name
  • Contact email address, for Google to contact you 
  • Contact phone number, for Google to contact you 
  • Developer email address, shown as part of your Developer Profile on Google Play
  • Developer phone number, shown as part of your Developer Profile on Google Play

Your developer name will appear on Google Play and can be changed at any time. 

Your organisation name and address is taken from the Google payments profile that you linked to your developer account during account creation. You will need to verify these identity details before publishing on Google Play. Learn more about verifying your developer identity information.

To help improve transparency and user safety on Google Play, Google will display your legal name, legal address, developer email address and developer phone number on Google Play. 

Your contact email address, contact phone number, developer email address and developer phone number must be verified using a one-time password and remain operational for the duration of your developer account. Go to the best practices section below to find out more.

What is a D-U-N-S number and how can I get one?

Assigned to organisations by Dun & Bradstreet, a D-U-N-S number is a unique nine-digit identifier that is widely used to verify businesses. Organisations can use Dun & Bradstreet to see if they already have a D-U-N-S number, or request one for free. Many organisations already have a D-U-N-S number as part of doing business. You should check whether your organisation has one before applying for a new one. You can do this by searching the official Dun & Bradstreet website. You can learn more about DUNS numbers by expanding the sections below.

Large organisations may have multiple DUNS numbers for the different entities that make up the organisation, so you must make sure that the one that you use to create your developer account contains the organisation details that you’d like to be associated with your developer account.

If you do not have a DUNS number, then you can apply for one from Dun & Bradstreet. This process can take up to 30 days so you should plan ahead. You will not be able to create a developer account for an organisation without one.

What if I can't get a D-U-N-S number?

If you're in one of the regions that Dun & Bradstreet does not support, then you can apply to our support team for an alternative way to verify your organisation.

Only organisations that are unable to obtain a DUNS number will be given the option to onboard using an alternative method. Requests containing incomplete answers will not be considered. We will not accommodate any exemptions or provide extensions for any organisation accounts that fail to provide a D-U-N-S number; you should prepare for this requirement before creating your developer account.

Tip: If you need to onboard without a D-U-N-S number, contact support before you create your Google Play Developer account.

Government organisations and agencies

If your developer account is for a government organisation or agency, you can complete verifications without providing a D-U-N-S number. However, you will need to apply to our support team for an alternative way to verify your developer account, which will include sharing an official government email domain or official website that we can associate with your developer account.

Tip: If you need to onboard without a D-U-N-S number, contact support before you create your Google Play Developer account.

Linked Google payments profile

Your Play Console developer account is linked to a Google payments profile at the point of account creation, which represents your developer real-world identity. This payment profile, holding your legal name and address, must be kept up to date to keep your developer account in good standing.

If you decide to monetise on Google Play, you will need to create a merchant account. To receive payments, you must configure a payments profile, which can either be the same one that you used to create your developer account or a different one if you prefer. 

Learn more about developer verifications.

Adding and verifying your payment method

Developers that monetise on Google Play using Google Play's billing system must verify their payment method in order to receive payments and keep their developer account compliant with Google Play policies.

Note: Developers that are enrolled in the multi-entity early access programme will see a page named Google Play Billing (instead of Payments profile) on the Settings page. Developers that have configured multiple payments accounts as part of their multi-entity set-up will be required to verify all active payment methods, not just the default payment method.

Adding a payment method

Before you start, note that only the account owner can manage merchant payments accounts.

To add a payment method:

  1. Open Play Console and go to the Settings page.
  2. Under 'Monetisation', select Payments profile.
  3. Go to the 'How you get paid' section.
    • Note: Most developers have a single merchant payment method for their developer account. Developers that have configured multi-entity support must first select the payments account that they wish to manage before the 'How you get paid' section is viewable.
  4. Click Add payment method.
  5. Complete the required information, including the name on your bank account, sort code and account number.
  6. Click Save.

When you add your payment method, you may be informed that you need to verify it. Depending on your location, you may have to complete a deposit challenge or upload official documents to verify your payment method. 

In this instance, the account owner receives an email confirming that a new payment method has been added. If verifications are required, the account owner receives an email about verifying their form of payment.

Verify a payment method

  1. Open Play Console and go to the Settings page.
  2. Under 'Monetisation', select Payments profile.
  3. Go to the 'How you get paid' section. If you are required to complete any locations, this section will have a message saying 'Verifications pending'.
    • Note: Most developers have a single merchant payment method for their developer account. Developers that have configured multi-entity support must first select the payments account that they wish to manage before the 'How you get paid' section is viewable.
  4. Click Verify to start the verification process. Depending on your location, you will have to complete a deposit challenge or upload official bank documents to verify your payment method. 
    • Deposit challenge: We send a small deposit to your bank account, after which you are required to confirm the exact amount by verifying the deposit in Play Console.
    • Upload official bank documents: If we are unable to issue a deposit challenge, you are required to upload official bank documents to verify your bank account.

Verification can take up to five days, so we recommend starting the process early to avoid delays.

Tip: You can visit Google payments centre help to learn more about verifying payment information.

Updating your payments profile to use the name and address on your Dun & Bradstreet profile

If your developer account represents an organisation, you must ensure that the legal name and address in your Google payments profile match those in your Dun & Bradstreet profile. This is crucial for maintaining the health and availability of your developer account and apps on Google Play.

You can view your Google Play developer identity's payments profile information in Play Console:

  1. Go to the Developer account page.
  2. Click Account details.
  3. Scroll to the 'Organisation details' section on the About you tab.

You can fully manage your payments profile in the Google payments centre by clicking View payments profile next to this information in Play Console.

Important: Developers earning money on Google Play may have multiple payments profiles. The specific payments profile relevant to these verifications (and the name and address that must match your Dun & Bradstreet profile) is best confirmed in Play Console using the above steps.

If Google detects any mismatches, you'll receive an email and see a banner in Play Console saying 'Your organisation name or address is no longer verified'. You must fix this by the deadline provided to avoid your developer account being restricted, which would remove all of your apps from Google Play.

Usually, the Play Console account owner can access Google payments centre directly from the Play Console notification and approve any necessary updates:

  1. Click 'View details' on the banner in Play Console.
  2. In the 'How to fix' section, click Review details, which takes you to the relevant page in the Google payments centre.
  3. This takes you to the relevant page in the Google payments centre. Scroll to the field marked 'Action required' in red.
  4. Click Review updates and verify the information. If correct, click Confirm to update your payments profile.
  5. Click Got it to return to the Google payments centre, where the field should now be marked as verified.

Shortly after, refresh Play Console, and the verification banner should no longer be displayed. This confirms that your legal name and address have been successfully verified.

Related issues that require alternative solutions

There are other scenarios in which you have a problem with your Dun & Bradstreet profile or DUNS number:

  • My organisation has been marked as out of business by Dun & Bradstreet: If your Dun & Bradstreet profile is flagged as out of business, contact them directly. You should be able to reinstate it by logging in to your account.
  • My organisation's DUNS number has changed: Sometimes, Dun & Bradstreet assigns a new DUNS number to a DUNS profile. In this case, you'll need to contact Play support to get assistance.

Contact information requirements for developer accounts

All new Play Console developer accounts must have verified contact details. Google Play collects and verifies two sets of information from new developers:

  • Contact phone number and email address that Google uses to contact you about your developer account. These are NOT shown to users on Google Play
  • Developer information, dependent on account type, that Google displays on Google Play as part of your Developer Profile. You can provide a different phone number and email address for app support queries for each of your apps on the Store settings page in Play Console.

The developer information collected and shown on Google Play depends on the type of developer account being created. Personal developer accounts are required to provide and verify a developer email address, whereas organisations must provide and verify a developer email address and phone number. All details are verified using a one-time password during the developer account registration flow. These verification steps ensure that the information that we hold is accurate and up to date. 

In addition to the details and developer information that Google Play collects, we also ask for your organisation's phone number. This should be the phone number that a user might be expected to find when looking up your organisation on the web or a public registry, like Dun & Bradstreet, and therefore might be different to the information that you provided for your public Developer Profile. Your organisation phone number may be used to verify your organisation and isn't shown on Google Play. You can provide a different phone number and email address for app support queries for each of your apps on the Store settings page in Play Console.

Contact information best practices

Learn best practices for managing your contact information (which is not shown to users on Google Play) and your developer information (which is shown to users in Google Play) by expanding the sections below.

Contact information best practices (not shown on Google Play)
  • You must keep your contact details up to date as this is how Google will communicate key information about your developer account. Similarly, ensure that your developer contact details are correct so that users can contact you. 
  • We may occasionally check if your account is active by emailing or calling the account owner using the details that you provided, so it is important that these details are accurate.
  • Consider using a contact email address that is different from the one that you used when creating your developer account, especially if your developer account has multiple users or is created for an organisation or business. You might want to consider setting up a dedicated shared inbox for this purpose so that the right set of people within your team or organisation can access these important messages.
  • The contact email address for an organisation or business account should not be generic or a personal email address. Make sure that you use an email address associated with your organisation.
Developer information best practices (shown on Google Play)
  • If you have an organisation account, you must provide a developer email address and developer phone number to be shown as part of your Developer Profile on Google Play. Make sure that you use an official email address associated with your organisation. Google may remove your apps from Google Play if your developer email address or phone number are not accessible.
  • The developer email address for an organisation should not be a generic or personal email address.

Was this helpful?

How can we improve it?
Search
Clear search
Close search
Google apps
Main menu
3264136599319560493
true
Search Help Centre
true
true
true
true
true
92637
false
false