The signup itself is quick. You sign in with a Google Account, accept the Developer Distribution Agreement, pay a one-time US$25 fee by card, pick an account type and verify who you are (Play Console Help).
A personal account needs a government photo ID. An organization account needs a D-U-N-S number from Dun & Bradstreet.
What catches people off guard comes after registration. If your personal account was created after November 13, 2023, you can’t publish to production until a closed test has run with at least 12 testers opted in continuously for 14 days (Play Console Help).
What does registration cost, and what do you need before you start?
The fee is a one-time US$25, paid by card during sign-up. You also need to be at least 18 and hold a Google Account, according to Play Console Help.
What you get for it is a publisher account in Play Console, where you publish and manage Android apps and games. Personal and organization accounts share the same features. Both can earn money through a payments profile and invite other users.
Get a few things together before you open the form. The Google Account you sign in with becomes the account owner login. Your legal name and address come from the payments profile you link, so they need to be right. You’ll want a government photo ID and a card, both in your legal name, plus a contact email and phone number that can receive one-time codes. Organization accounts also need a D-U-N-S number, and personal ones don’t.
Mastercard, Visa and American Express are accepted. Discover works in US locations only, Visa Electron outside the US only, and prepaid cards are rejected.
Refunds are murky because Google’s own pages disagree. The sign-up guide says the fee stays non-refundable if the ID or card details are judged invalid.
The identity verification FAQ says you can ask support for a full refund after a failed check, and each request is reviewed. Treat a refund as something you can ask for, not something you’re owed.
Personal or organization: which Google Play developer account type fits?
Go personal if you build as an individual, say a student or hobbyist. Semi-professional developers fit here too. Go organization when a registered business stands behind the app, or when Google’s policy requires one.
Features are identical. What changes is the information and the checks Google asks for.
| Requirement | Personal | Organization |
|---|---|---|
| Identity basis | Government photo ID and proof of address | D-U-N-S number, representative ID, organization document |
| D-U-N-S number | Not needed | Required (known government bodies excepted) |
| Website verification | Optional | Required for new accounts |
| Device verification | Required for new accounts | Not required |
| Closed test before production | Required for new accounts | Rule applies to personal accounts only |
Some apps take the choice away, because Google sends these categories to an organization account:
- Financial products and services, including banking, loans, trading and crypto wallets or exchanges
- Health apps, meaning medical apps and human subjects research apps
- Apps approved to use the VpnService class
- Government apps, including anything built on behalf of an agency
If your app isn’t in one of those, the decision mostly comes down to time. A new D-U-N-S number can take up to 30 days to arrive, while the personal closed test runs 14 days (Play Console Help).
So a solo developer with no D-U-N-S number will usually get to production sooner on a personal account. Organization wins on speed only if the number already exists.
You can switch types later, though only one way. Google supports converting a personal account to an organization account, which means setting up an organizational payments profile and adding the extra account details.
How to create a Google Play developer account step by step
- Go to play.google.com/console/signup and sign in with the Google Account that should own the developer account.
- Read and accept the Google Play Developer Distribution Agreement.
- Pay the registration fee with an accepted credit or debit card.
- Choose personal or organization. The choice sets which details and checks follow.
- Enter the developer name and contact details, then link or create a Google payments profile when Play Console asks.
- Upload your identity documents. Personal accounts submit a government photo ID and proof of address, organizations submit a D-U-N-S number and organization documents.
- Finish the remaining Home page tasks: website verification (organizations), device verification (personal accounts), and the one-time codes for your phone and email.
Google’s help article lists the fee before the account type. Some walkthroughs put the payment on the last screen, so just follow whatever order Play Console shows you.
You can start preparing your app while verification is pending. Publishing stays locked until it clears.
Which details appear on your public developer profile?
The developer name is the one public detail you choose yourself. It can differ from your legal name, and Google lets you change it at any time.
On a personal account, the public side is your legal name, country and developer email address. Once you monetize on Google Play, your full address shows too.
Organization accounts show the legal name and address, along with the developer email address and developer phone number.
In the EEA and UK, what shows also depends on trader status. Every active developer account must declare trader or non-trader status in Play Console by February 1, 2027, per Play Console Help.
Traders display name, address, phone number and email on the store listing (organizations also show their D-U-N-S number). Non-traders show only an email address and country.
The contact email and phone Google uses to reach you stay private. Each is verified with a six-digit code, and the phone code arrives by text or voice call.
The phone code only works after identity verification is done, plus website verification for organizations or device verification for personal accounts.
How does identity verification work, and where does the payments profile fit?
Google checks your legal name and address through the Google payments profile you link at sign-up. Personal accounts then upload a government photo ID. Organizations submit a D-U-N-S number, a representative ID and an organization document.
Until verification clears, you can prepare an app but can’t publish it.
Personal account verification
Identity verification takes approximately 3 business days, according to Play Console Help.
After the account is created, you upload a government-issued photo ID from the country you signed up in, plus a proof of address document. The name and address you type must match the ID exactly.
Google’s list of reasons a check fails is pretty mundane:
- An unaccepted or expired document
- An ID issued by a country other than the payments profile country
- A name that doesn’t match the ID exactly
- Photocopies, screenshots, black and white images, or photos with cropped corners or glare
- A payments profile type that contradicts the account type
Attempts are limited, so photograph the whole document flat with all four corners visible and no flash. Google also warns that uploading anything other than an ID image may lead to suspension.
Organization verification and the D-U-N-S number
A D-U-N-S number is a nine-digit business identifier issued by Dun & Bradstreet, and it’s free to request. Google warns that third-party services charge fees for it. Large organizations that hold several numbers should pick the one carrying the right details.
The legal name and address in your payments profile must match your Dun & Bradstreet record exactly. A mismatch triggers an email and a Play Console banner, and if it’s left unresolved, the account gets restricted and apps get removed.
Beyond the number, you’ll need an official organization document, the representative’s ID and an organization phone number (not shown to users). New organization accounts also need a verified website.
If you’re in a region Dun & Bradstreet doesn’t support, contact Google Play support for an alternative route. Google grants no exemptions or extensions, and known government bodies go through support as well.
Request the number before you open the sign-up form. Google doesn’t let you create an organization account without a valid one.
Payments profile and selling apps
One profile, two jobs.
At sign-up it supplies your legal name and address for verification, and its type follows the account type. Country, account type and D-U-N-S number can’t be edited on an existing profile, so a wrong one means creating, verifying and linking a new profile (Play Console Help).
On the selling side, monetizing requires a merchant account, and payouts require a configured payments profile. Only the account owner manages merchant payment accounts.
Adding a payment method can trigger a deposit challenge or an upload of bank documents. Google says that verification can take up to 5 days, so start it well before the first paid release is due.
What must a new personal account complete before the first app goes live?
A personal account created after November 13, 2023 can’t publish to production until it clears device verification, a closed test and a production access review. Until then, Play Console keeps the Production and Pre-registration pages disabled (Play Console Help).
- Verify device access. Scan the QR code from the Home page task, sign into the Play Console mobile app as the account owner on a physical, non-rooted phone running Android 10 or newer, and tap Verify.
- Finish app setup, then start a closed test. Internal testing is optional.
- Keep at least 12 testers opted in, continuously, for the preceding 14 days.
- Click Apply for production on the Dashboard and complete the application form.
The count isn’t cumulative. A tester who opts out early doesn’t count, and one who opts out and back in only counts if the days are consecutive.
The application form asks for specifics. How easy was it to recruit testers? Did they use every feature, and did their usage match real production behavior? You summarize the feedback you collected, give your target audience and value proposition with an estimated first-year install range, and say what you changed because of the test and how you judged the app ready.
Google emails the account owner when the review finishes. With fewer than 12 opted-in testers, or thin engagement, you may be told to keep testing.
For recruiting, Google suggests personal and professional networks, plus communities where your target users already gather. Tell testers up front that they must stay opted in.
Review is not a troubleshooting step. Policy violations found at this stage lead to rejections and longer appeals, so check the app against the Google Play Developer Content Policies before you apply.
Older guides still quote 20 testers. Google cut the requirement from 20 to 12 testers on December 11, 2024, and its current page says 12.
Does Android developer verification change anything for a new Play developer?
Not at sign-up. It adds a package name registration check that Play Console handles for most apps automatically.
The idea is that apps on certified Android devices should come from verified developers with registered package names. Google announced it in August 2025, and it’s separate from the identity checks you complete when you create the account (Play Console Help).
Verification launched in March 2026. Apps already on Play were registered automatically, and new apps created in Play Console register to your developer account on creation (Android developer verification guide for Play Console).
Enforcement began on September 30, 2026 for participating stores in Brazil, Indonesia, Singapore and Thailand, per Google’s July 2026 update. Unregistered apps can still be sideloaded through adb or an advanced flow.
Global expansion follows in 2027 and beyond, according to the Android Developers Blog.
As of that July 15, 2026 update, 99% of apps on Play were already registered automatically. Apps left unregistered by the deadline risked global removal from Google Play.
A Play-only developer doesn’t need a separate Android Developer Console account. That console is for developers who distribute apps only outside Google Play.
Some guides describe a September 2026 identity mandate aimed at new personal accounts. Google’s own pages describe package name registration instead, so follow Google’s version.
For a new account, the practical step is small. After you create your first app, open the Play Console Home page and confirm it shows as registered.
How long does it take to get from sign-up to a published app?
Plan for roughly three to four weeks on a personal account, and almost all of that is waiting. An organization account skips the closed test, but a missing D-U-N-S number can cost more time than the test does.
The published figures are these. The closed test needs 12 testers opted in continuously (Play Console Help). The production access review usually takes seven days or less, occasionally longer (Play Console Help). A free D-U-N-S request can take up to 30 business days, and the paid expedited version arrives within eight business days (Dun & Bradstreet).
| Route | What you wait for | Rough elapsed time |
|---|---|---|
| Personal | Identity check, closed test, production access review | About three to four weeks |
| Organization with a D-U-N-S number | Identity and website verification | No closed test, no published total |
| Organization without one | D-U-N-S request, then the same checks | Add up to 30 business days |
The personal estimate is arithmetic from Google’s published figures, not a Google promise.
Google’s help pages phrase the D-U-N-S wait in days. Dun & Bradstreet counts business days, which at the upper end is about six calendar weeks.
The paid expedite brings the wait close to the length of the closed test. It’s worth buying only when a launch date depends on it.
Third-party guides report a wide spread for the identity check. Google’s own estimate is the one to plan around.
What goes wrong during registration, and how do you fix it?
Identity mistakes cost the most: the wrong account type, the wrong person verified, an organization name that doesn’t match its record. Each has a documented fix, and two of them mean opening a new account.
Start with the wrong account type. Google supports changing a personal account to an organization account only, and the process goes like this.
- Get the personal account fully verified, with no warnings on the Home page.
- Add the organization website, verify it, and click Send verification request.
- Choose Change account type, then create or select an organizational payments profile that carries the D-U-N-S number.
- Enter organization type, size and phone number, plus developer and contact details, and verify identity if asked.
- Link the payments profile and confirm. Wait at least 72 hours before submitting new apps.
Organization to personal isn’t supported. You open a new personal account, verify it, and transfer the apps to it.
D-U-N-S errors split a few ways. With an address mismatch, correct the address with Dun & Bradstreet first and then retry, since updates take up to 5 business days to reach Google. A business information mismatch calls for a new payments profile instead of reusing an old one. And if the lookup fails outright, re-enter the number exactly as Dun & Bradstreet shows it.
If the wrong owner got verified, there’s no fix in place. Account ownership can’t be transferred, so Google says a new account must be created and verified with the correct information. Applicants under 18 can’t verify at all.
Details can also lapse after sign-up. Google can remove your developer presence and apps if identity or contact details stop verifying. Re-verifying reinstates them, and an appeal in Play Console can buy more time.
Merchant developers face the same removal when a bank account stays unverified. Organization name or address changes go through Dun & Bradstreet first, and Google then asks the account owner to re-verify.
On documents, proof of address can be a government-issued document or ID, a utility or phone bill, a bank statement, or a lease or mortgage agreement. It must be unexpired, and a black and white copy of a color original is rejected.
Google Play developer account FAQ
Can I change the developer name after I register?
You can, and Google lets you do it at any time. The public name doesn’t have to match your organization’s legal name.
A legal name change follows a separate route. Personal accounts update the payments profile, while organizations update their Dun & Bradstreet record first.
Can one D-U-N-S number cover more than one developer account?
Google confirms that one D-U-N-S number can register several developer accounts.
If those accounts share the same identity details, an organization can also reuse a single payments profile across them, which simplifies verification.
Which Google Account should I sign up with?
Pick one you’ll keep long term. The account that creates the developer account becomes the owner, and Google says ownership can’t be transferred.
Organizations should also give Google a contact email tied to the company, not a personal address.
What should I do if the verification code never arrives?
For phone codes, switch from text to the voice call option. Delivery can lag on crowded networks or with a weak signal.
Still nothing after several tries? Use a fixed-line phone or retry another day. For email codes, check spam first, then try a different address.
Can a government organization register without a D-U-N-S number?
Known government organizations and agencies can. If Play Console still asks for the number, contact Google Play support through the Help section, and only when you can’t supply one.
Google still encourages agencies to request a free D-U-N-S number.
What Keeps a Google Play Developer Account in Good Standing?
Reachable contact details do. Google requires verified emails and phone numbers to stay operational for the life of the account, and it occasionally emails or calls the account owner to confirm activity (Play Console Help).
The failures that go unnoticed are the dull ones, so deal with those first. Move the contact email to a monitored, shared inbox and make sure both verified phone numbers can still receive codes. For the public developer email, use an organization address, never a personal or generic one.
The trade-off is administrative. A shared inbox puts every notice in front of several people, but each changed address or number must be re-verified with a one-time code.
Verified as of November 2026. A revision to Google’s account requirements would change this advice.
- Protecting Users and Brand Standards Across Image-Driven Platforms - November 10, 2026
- Go Cheat Sheet - November 9, 2026
- Build or White-Label Software? How Software Teams Decide What to Resell in 2026 - November 9, 2026
