Skip to content

How-to guide

Opening a Google Play developer account: personal and organisation

The steps of a Play Console registration, why an organisation account is the only right option for most companies, and the closed-testing requirement that applies to personal accounts.

Written for: Companies that need to publish their Android app from their own corporate accountLast updated: 7 min read

In short

How do you open a Google Play developer account?

A Google Play developer account is opened through Play Console for a one-time registration fee of 25 US dollars. The account is opened as either personal or organisation; an organisation account requires a D-U-N-S number. Identity verification happens during registration, and a government ID and credit card in your legal name may be requested. Neuros publishes apps from the client's own account.

Steps

0 / 7 steps

  1. Choose the account type

    A personal account is for students and individual developers. If you are publishing on behalf of a company, open an organisation account; treat this choice as irreversible, because changing type in practice means setting up a new account.

  2. Have a D-U-N-S number ready for an organisation

    A D-U-N-S number is mandatory when registering an organisation account. If you do not have one, get it first; it is requested free through Dun & Bradstreet but can take days to issue.

    Watch out: The name on the number must match the trade register name exactly.

  3. Bind the Google account to a corporate address

    Use a company mailbox that outlives any one employee. Play Console access follows the Google account, so a console tied to someone's personal Gmail leaves the app unmanageable the week they hand in their notice.

  4. Register and pay the fee

    The registration fee is a one-time 25 US dollars, paid by credit card; prepaid cards are not accepted. The card is expected to be in the legal name of the person registering.

  5. Complete identity verification

    Identity verification is requested during registration; a valid government ID and credit card in your legal name may be asked for. For organisation accounts, company details are additionally verified against the D-U-N-S record.

  6. Set up users and permissions

    Invite the development team with their own accounts and grant only the permissions they need. Uploading an app and distributing test builds do not require account ownership.

    Watch out: Ownership and the payments profile stay with the company in all cases.

  7. Plan the closed test if you are on a personal account

    Personal accounts created after 13 November 2023 must run a closed test with at least 12 testers opted in continuously for 14 days before applying for production access. That period belongs in the release schedule from the start.

    Watch out: A tester has to accept the invite and install the app; if they opt out and rejoin, the 14-day clock restarts.

Should I open a personal or organisation Google Play account?

Both account types have the same functionality and the same monetisation options; the difference is whose name the app is published under and how verification works. A personal account is for students, hobbyists and individual publishers. If publishing on behalf of a company, the right answer is an organisation account, and that requires a D-U-N-S number.

For some app types there is no choice. Apps offering financial products and services — including banking, loans, stock trading, investment funds, cryptocurrency software wallets and exchanges — must register as an organisation. The same applies to medical apps and human subjects research apps, to apps using the VPN service class, and to apps developed by or on behalf of a government agency.

Difference between personal and organisation accounts
ItemPersonalOrganisation
Registration fee25 USD, one-time25 USD, one-time
D-U-N-S numberNot requiredMandatory
Finance, health, VPN and government appsCannot publishCan publish
Closed-testing requirement for accounts created after 13 Nov 202312 testers, 14 continuous daysThe requirement is defined for personal accounts
Publishing under a corporate identityNoYes

What is the Google Play 12 testers requirement?

Personal developer accounts created after 13 November 2023 must keep their app in closed testing with at least 12 testers opted in continuously for 14 days before they can apply for production access. The critical detail is continuity: a tester who tests for fewer than 14 days and opts out does not count, and for a tester who opts out and rejoins, the clock restarts.

How the 14 days are counted — three testers
day1234567891011121314
Joined day 1, stayed

A continuous 14 days — counts.

Joined day 1, left day 6

Shorter than 14 days — does not count at all.

Left day 6, rejoined day 8

The first six days (faded) count for nothing; the clock starts from zero on day 8 and has to reach 14.

The practical consequence: at least 12 testers have to satisfy this at the same time, and the clock runs backwards from the day you apply. So two weeks before the release date, testers need to have genuinely installed and be using the app. That period is a stage to put in the calendar, not a wait.

Whose name should the Play Console account be in?

The company that owns the app. On the Play side that has a distinct consequence: in-app purchase and subscription revenue flows into the account's payments profile, so if the account belongs to the firm the money reaches them first and getting it to you becomes a separate accounting relationship. Give the developer upload and test rights; ownership and the payments profile are never handed over.

What is Android developer verification and who does it affect?

Google is making verification of developer identity a requirement for apps installed on certified Android devices. It is a layer separate from reviewing the app's content: confirming who published it. Early access began in November 2025, and the Android Developer Console opened to all developers in March 2026.

The timetable runs like this: from 30 September 2026 the requirement takes effect in Brazil, Indonesia, Singapore and Thailand, with global expansion announced for 2027. Türkiye is not in the first wave, but will be in the second.

What it means in practice: if you publish through Play Console you have already completed identity verification as part of registration, so nothing changes for you. The real impact is on distribution outside Play — handing out an APK directly, installing onto corporate devices by hand, or using a third-party store will require a verified developer identity. If you are an organisation distributing to a dealer network or a field team from outside Play, put this timetable into your plan now.

Why is my app not showing on newer phones?

Play holds a floor for the Android version an app targets, and moves that floor up a release every year. An app below it is not deleted from the store but stops being listed on new devices; it quietly becomes unreachable, and you usually notice when downloads fall. An annual release schedule is therefore part of staying published rather than part of a maintenance agreement.

How many days does Play account approval take?

On a personal account identity verification usually takes a few business days. On an organisation account the time depends on whether your D-U-N-S record is ready: with the number in hand verification takes days, without it the number application adds weeks. Put this step first when building your release schedule; waiting on an account with the code ready is the most common delay.

Where do I find 12 testers?

The requirement is that testers genuinely install and use the app. Your own team and close contacts can count, but Google also looks at the quality of engagement: a tester who installs and never opens produces a weak signal. What works is assembling fifteen people from the product's real audience and giving them a concrete test scenario — the requirement gets met and the first feedback arrives.

Can I convert a personal account to an organisation one?

Changing account type means setting up a new account in practice, and the app's reviews, download history and ranking do not transfer. The decision is therefore expensive to reverse: if you will publish on behalf of a company, open an organisation account from the start. Most teams that start personal and grow pay that cost in year two.

What is needed for in-app purchases?

A payments profile set up and verified. That is a step separate from the developer account and asks for bank and tax details. If you sell digital content or subscriptions the store's payment system is mandatory; for physical goods and services you can use your own. That distinction directly affects your commission arithmetic.

What do I do if my app is taken down?

The removal notice names the policy breached and an appeal route is open. Read it first and establish whether the breach genuinely exists; if it does, fix and resubmit, if not, appeal. Submitting the same build repeatedly gets the account flagged, and that is a far heavier consequence than one app being removed.

Sources

  1. 01Choose a developer account typeGoogle Play Console Help · 2026
  2. 02Register for a Google Play Console developer accountGoogle Play Console Help · 2026
  3. 03Testing requirements for new personal developer accountsGoogle Play Console Help · 2026
  4. 04Understanding Android developer verificationAndroid Developer Console Help · 2026
  5. 05Google Play target API level requirementsGoogle · 2025

Frequently asked

Questions we get asked

No, it is one-off. The Google Play registration fee lists at 25 US dollars; paying from Türkiye charges the lira equivalent to your card and no renewal is ever requested. Apple's membership, by contrast, is annual, and an unrenewed one takes the app off the store. If you ship to both, keep one as a one-off line and the other as a subscription line — putting them on the same line produces a surprise in year two.

Yes, it is mandatory when providing organisation account information, and Google verifies identity with it. The good news: Apple asks for the same number, so if you are shipping to both stores you only need to obtain it once. What the number is and how to get one is covered in detail in our App Store account guide.

The requirement is defined for personal developer accounts created after 13 November 2023; accounts created on or before that date are outside its scope. If you are publishing on behalf of a company you need an organisation account anyway. Rather than looking for a shortcut, add the 14 days to the release schedule as a stage; the testing data is useful for a first release regardless.

Yes, the two stores have separate accounts and separate verification processes. Both should be opened in the company's own name. What they share is the D-U-N-S number: both stores ask for it in an organisation enrolment, so a number obtained once serves both applications.

No. Google Play does not accept prepaid cards for the registration payment. Identity verification may also ask for a valid government ID and a credit card in your legal name, and the two names are expected to match. For an organisation registration, company details are additionally checked against the D-U-N-S record.

Let's walk these steps together

We can stand alongside you while you apply any of this to your own project.