verapli
Sign inJoin free
Menu

Guides · devtools · Verification-gated

Google Play Console organisation developer account

Register a Google Play developer account as an organisation (US$25 one-off), with a D-U-N-S number, verified organisation documents, verified contact channels and a verified website, so the company can publish Android apps on Google Play.

Researched · not yet run liveLast researched 25 October 2026 · Google · provider site

Researched, not yet run live. Built from the provider’s official pages (linked below). A person hasn’t walked this flow end to end yet, so check each step against the source.
Do this with verapliJSON for agents

Who owns what

A Google Account (ideally a company-controlled one, not a staff member's personal Gmail) becomes the owner of a Play Console developer account of type "Organisation". The organisation's legal name and address come from a linked Google Payments profile, which must match the D-U-N-S record and the uploaded documents exactly. Other people and service accounts are invited later through Users and permissions.

  • Google Account (account owner) personal owned by the company (use a company-controlled login)Must be 18+. Only the owner can complete some verification tasks [to verify].
  • Google Payments profile (organisation) billing owned by the company · under Google Account (account owner)Supplies the legal name and address that must match all documents.
  • Play Console developer account (Organisation) developer owned by the company · under Google Account (account owner)
  • Google Search Console property for the company website other owned by the companySame Google account as the Play Console owner gives instant website approval.
  • Google Cloud project with a service account projectoptional owned by the companyOnly needed to automate publishing via the Google Play Developer API.

The type (personal vs organisation) is chosen at sign-up; choose organisation for a company. [to verify whether it can be changed later]

Google shows the legal name, legal address, developer email and developer phone publicly on Google Play for organisation accounts.

Have ready

  • apple/duns-number: The same Dun & Bradstreet D-U-N-S number Apple uses; Google requires one for organisation accounts.
  • A company website on a domain you control, registered in Google Search Console
  • A non-generic, non-personal company contact email and a company phone number
  • The organisation's D-U-N-S number, with D&B record matching the legal name and address exactly · Google will not create an organisation account without one; getting one can take about 30 days. [2]Needed for: Create the organisation developer account and pay US$25
  • Credit or debit card (not prepaid) for the US$25 one-off fee, ideally in the organisation's or legal name [1]Needed for: Create the organisation developer account and pay US$25
  • Official government identity document for the person verifying [3]Needed for: Verify the organisation and the person
  • Official organisation document (e.g. certificate of incorporation) matching the payments profile name and address [3]Needed for: Verify the organisation and the person
  • Organisation website (not a social media profile) that you can verify in Search Console [4]Needed for: Verify the organisation website
  • Contact email that is neither generic nor personal, plus a developer email shown on Google Play [2]Needed for: Verify contact and developer email and phone
  • Contact phone and developer phone that can receive one-time passwords and stay working for the life of the account [2]Needed for: Verify contact and developer email and phone
  • Official bank document, only if Google cannot issue a deposit challenge to verify the payment method [2]Needed for: Verify the payment method

Steps

Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.

  1. Get or confirm the D-U-N-S number

    Look up whether the organisation already has a D-U-N-S number and that its legal name and address are right. If not, request one free from Dun & Bradstreet. Do not pay third-party services for it.

    • Guided by hand
    • Human step: The provider reviews it
    The provider says
    About 30 days to obtain a D-U-N-S number (Android developer verification page says up to 28 days). [2]
    If something goes wrong (2)
    • Several D-U-N-S numbers exist for the organisation: Use the one whose legal entity name and address match the payments profile and company documents. [2]
    • The organisation cannot get a D-U-N-S number: Request Google's alternative onboarding method, answering every question in full; incomplete requests are not considered. [2]

    Where: https://www.dnb.com/duns-number/get-a-duns.html

  2. Create the organisation developer account and pay US$25

    Signed in with the company Google Account, start Play Console sign-up, choose "Organisation", enter the D-U-N-S number and organisation details, accept the Developer Distribution Agreement and pay the fee. You accept the terms and pay yourself.

    • Guided by hand
    • Human step: You add payment details
    • After: Get or confirm the D-U-N-S number
    If something goes wrong (1)
    • Card declined or not accepted: Use a Mastercard, Visa, American Express or (outside the US) Visa Electron credit or debit card; prepaid cards are not accepted. [1]

    Where: https://play.google.com/console/signup

  3. Accept the Google Play Developer Distribution Agreement

    Read and accept the agreement during sign-up. You must accept it yourself.

    • Guided by hand
    • Human step: You accept the terms
    • After: Get or confirm the D-U-N-S number

    Where: https://play.google.com/about/developer-distribution-agreement.html

  4. Verify the payment method

    Complete Google's payment method verification (normally a deposit challenge; otherwise upload a bank document).

    • Guided by hand
    • Human step: You add payment details
    • After: Create the organisation developer account and pay US$25
    The provider says
    Payment method verification can take up to 5 days. [2]

  5. Verify contact and developer email and phone

    Enter the one-time passwords Google sends to the contact email, contact phone, developer email and developer phone.

    • Guided by hand
    • Human step: You enter a 2-step code
    • After: Create the organisation developer account and pay US$25
    If something goes wrong (1)
    • Rejected or flagged contact email: Use a role or person address on the company domain that is not a generic inbox or personal webmail [to verify exact wording of Google's rule]. [2]

    Where: https://play.google.com/console/developers

  6. Verify the organisation and the person

    In Play Console, complete the verification task: confirm the D-U-N-S details and upload an official government ID and an official organisation document. You upload documents yourself.

    • Guided by hand
    • Human step: You prove your identity
    • After: Create the organisation developer account and pay US$25, Verify the payment method
    People report
    People report Google replies with a result within several days of submitting documents. [12]
    If something goes wrong (2)
    • Verification fails because documents do not match: Make the payments profile legal name and address match the documents exactly (including suffix such as Ltd vs Limited); the profile can be updated during the verification task. [3]
    • Google cannot verify the information: Respond before the deadline; unverified developer presence and apps may be removed and cannot be republished until verification completes. [3]

    Where: https://play.google.com/console/developers

  7. Verify the organisation website

    Register the website in Search Console with the same Google account if possible, then send the website verification request from Play Console Account details.

    • Guided by hand
    • Human step: You press submit
    • After: Create the organisation developer account and pay US$25
    If something goes wrong (2)
    • Website verification request is stuck or denied: Check the URL, make sure the Search Console owner approves the request (or use the same Google account for both), and resend from Account details. [4]
    • Website is a social media profile: Social media profile URLs cannot be verified; use a website on a domain you own. [4]

    Where: https://search.google.com/search-console

  8. Check whether a closed test is required before productionoptional

    Personal accounts created after 13 Nov 2023 must run a closed test with 12+ testers for 14 consecutive days before production access. Google's page only names personal accounts; check Play Console for any requirement on your organisation account [to verify].

    • Guided by hand
    • After: Verify the organisation and the person
    The provider says
    For personal accounts, at least 14 consecutive days of closed testing with 12+ opted-in testers. [5]

  9. Register apps for Android developer verificationoptional

    From September 2026 (Indonesia, Singapore, Thailand first; global from 2027) apps on certified Android devices must be registered by a verified developer. Check that your apps show as registered [to verify how Play Console accounts are handled].

    • Guided by hand
    • After: Verify the organisation and the person

  10. Optional – give a service account access for automated publishingoptional

    Create a service account in a Google Cloud project, enable the Google Play Android Developer API, and invite the service account email in Play Console Users and permissions with only the permissions needed.

    • Guided by hand
    • Human step: You press submit
    • After: Verify the organisation and the person

    Where: https://play.google.com/console/users-and-permissions

Terms and gotchas

Plain-English summary, not legal advice. Each card links its source.

Can get you bannedThe rules say

A termination takes every related account with it

If Google terminates a developer account, related developer accounts are terminated too, and any new account you open is terminated without refund. Only one appeal per termination. Never open a second account to get around a suspension. [7]

Can get you bannedThe rules say

Strikes add up

App suspensions count as strikes; repeated or serious violations (malware, fraud, harmful apps) terminate the account and related accounts. [8]

Can cost moneyThe rules say

The fee is not refunded if your details are invalid

If the ID or card information is found invalid, the US$25 registration fee is not refunded. [1]

Can cost moneyThe rules say

Inactive accounts are closed for good

Accounts that never submit an app within a year, or that have few installs, unverified contact details and no Console use for 180 days, are closed after warning emails. Closed accounts cannot be reactivated and the fee is not refunded. [9]

Worth knowingThe rules say

Your company details become public

Google shows the organisation's legal name, legal address, developer email and developer phone on Google Play. [2]

Worth knowingThe rules say

Free D-U-N-S

Dun & Bradstreet issues D-U-N-S numbers free; third-party services may charge high fees for the same thing. [2]

What you end up with

Env varSecretFormatWhat it is
GOOGLE_PLAY_SERVICE_ACCOUNT_JSONsecret./secrets/play-service-account.jsonPath to the service account key file used by publishing tools (only if you chose the API step; prefer keyless auth where your CI supports it)

Renewals

  • Keep the four verified contact channels working and use Play Console to avoid inactivity closure: every 180 days [9]

Pricing

  • Costs: US$25 one-time registration fee (card, not prepaid).
  • D-U-N-S numbers are free from Dun & Bradstreet.

Source [1]

For agents

The same entry as JSON: /api/v1/entries/google/play-console-org · requirements /api/v1/requirements/google/play-console-org · terms /api/v1/terms/google/play-console-org.

Remote MCP (read-only, no auth)
claude mcp add --transport http verapli https://verapli.com/mcp

> "What do I need for Google Play Console organisation developer account, and how long will it take?"
  → tools/call requirements { "provider_id": "google/play-console-org" }

Sources

  1. Play Console Help – Get started with Play Console (sign up) US$25 one-time fee; accepted card types, no prepaid cards; must be 18+; accept the Developer Distribution Agreement; choose personal or organisation; government ID and card in legal name may be needed and fee not refunded if information is invalid; testing requirement applies to personal accounts created after 13 Nov 2023; new personal accounts verify an Android device · accessed 25 October 2026 · official
  2. Play Console Help – Required information to create a Play Console developer account Organisations need a D-U-N-S number (no account without one); D-U-N-S can take about 30 days; payment method verification up to 5 days; organisation name/address come from the Google Payments profile; organisation phone, website, contact name; contact and developer email/phone verified by one-time password; contact email must not be generic or personal; legal name, address, developer email and phone shown publicly; alternative onboarding only for organisations that cannot get a D-U-N-S · accessed 25 October 2026 · official
  3. Play Console Help – Verify your developer identity information Organisation accounts provide a D-U-N-S number, an official government identity document and an official organisation document; documents must exactly match the payment profile; must verify before submitting apps; unverifiable accounts may have presence and apps removed · accessed 25 October 2026 · official
  4. Play Console Help – Verify your website Website ownership verified through Search Console; request sent from Account details; automatic approval when the same Google account owns the Search Console property; otherwise the owner must approve; social media profile URLs cannot be verified · accessed 25 October 2026 · official
  5. Play Console Help – App testing requirements for new personal developer accounts Personal accounts created after 13 Nov 2023 must run a closed test with at least 12 testers opted in for 14 consecutive days before production access; page does not mention organisation accounts · accessed 25 October 2026 · official
  6. Android Developer Console Help – Understanding Android developer verification Verified developers must register apps for certified Android devices; goes live 30 Sep 2026 in Indonesia, Singapore and Thailand, global from 2027; organisations need a D-U-N-S number (free, up to 28 days); full distribution account US$25; free limited distribution account for up to 20 devices · accessed 25 October 2026 · official
  7. Play Console Help – Understanding Google Play developer account terminations On termination, related developer accounts are also terminated and new accounts are terminated without refund; one appeal per termination · accessed 25 October 2026 · official
  8. Play Console Help – Enforcement process Suspensions are strikes; repeated or serious violations terminate individual and related accounts · accessed 25 October 2026 · official
  9. Play Console Help – Inactive developer accounts Accounts over a year old that never submitted an app, or with few installs, unverified contact details and no Console use for 180 days, are closed after 60/30/7-day notices; fee not refunded; closed accounts cannot be reactivated · accessed 25 October 2026 · official
  10. Google Play Developer API – Getting started API access via a Cloud project and service account invited in Play Console Users and permissions; linking the developer account to a Cloud project is no longer required · accessed 25 October 2026 · official
  11. Android Developers Blog – Boosting trust and transparency in Google Play (July 2023) D-U-N-S requirement for new organisation accounts; obtaining a D-U-N-S can take up to 30 days · accessed 25 October 2026 · official
  12. Uscreen Help – Google developer account – verify identity and organisation by uploading documents People report Google contacts them within several days with the verification result; name and address mismatches are a common cause of rejection · accessed 25 October 2026 · community

Provider rules change. This page is generated from verapli registry version 2026.1025.387; spotted something out of date? Tell us. Google is not affiliated with verapli.