Google Play Developer Account: Fee, Types and Verification

Before you publish anything on Google Play you need a Play Console developer account. Signing up takes an afternoon. Getting verified can take weeks for a company, and the account type you pick decides whose name and address people see on your listing. This guide covers the fee, the two account types, the checks each needs, and the D-U-N-S number organisations must have. Google's details below come from its own Play Console Help pages as of 2 September 2026.

The short version

• Registration costs US$25, paid once. There is no yearly renewal.
• Personal accounts suit students, hobbyists and individual developers. Organisation accounts are for companies, and Google expects financial, health, VPN and government apps to use one.
• Every account verifies a legal name and address through a Google payments profile, plus contact details by one-time code. New personal accounts also verify a real Android device with the Play Console app.
• Organisations need a D-U-N-S number, which Google says can take up to 30 days to get, and a website verified through Google Search Console.
• New personal accounts must also run a closed test with 12 testers for 14 days before they can publish to production. That rule has its own guide.

What it costs

As of 2 September 2026, Google's Get started with Play Console page lists a US$25 one-time registration fee, paid by credit or debit card. Prepaid cards are not accepted, and the card types Google takes vary by location. The same page warns that Google may ask for a valid government ID and a credit card, both in your legal name, and that the fee is not refunded if that information turns out to be invalid.

If you also ship on iOS, Apple charges every year instead; our Apple Developer Program guide covers that side. What Google takes from your sales is covered in the Google Play service fee.

Personal or organisation?

Google's Choose a developer account type page says both types get the same Play Console features, and both can earn money through a payments profile. The difference is what you have to prove and what Google shows on your listing:

Sources: Google's pages on required information for a developer account and verifying your developer identity, as of 2 September 2026.

When Google expects an organisation account

The account type page lists four kinds of service that should use an organisation account:

• Financial products and services, such as banking, loans, stock trading, investment funds, and cryptocurrency wallets and exchanges.
• Health apps, such as medical apps and human subjects research apps.
• Apps approved to use the VpnService class.
• Government apps, including apps developed for a government agency.

Which should a small team pick?

If you have a registered company, choose an organisation account. The company's name and address go on the listing, and the closed testing rule for new personal accounts does not apply. The cost is a slower start.

If you are one person building on the side, a personal account is quicker. But once a personal account monetises, Google shows your full address, which for many solo developers is a home address. Decide that before launch, not after.

Verifying a personal account

For a personal account, Google asks for a developer name (shown on Google Play, can differ from your legal name, and can be changed at any time), your legal name and address, a contact email and phone number that Google uses to reach you, and a developer email address that appears on your profile. Your legal name and address come from the Google payments profile you link when you create the account. If that profile is not verified yet, you upload an official government identity document in Play Console.

The contact email, contact phone and developer email are each confirmed with a one-time code, and Google says they must keep working for as long as you have the account.

Device verification

Since early 2024, new personal accounts have to show they can reach a real Android phone before publishing. As of 2 September 2026, Google's device verification page describes the steps:

1. Sign in to Play Console on the web as the account owner and open the Home page.
2. Find the task "Verify that you have access to an Android mobile device" and click View details.
3. Scan the QR code to open or install the Play Console app on your phone.
4. Sign in to the app as the account owner, choose your developer account, tap Verify and follow the prompts.

Any non-rooted physical Android phone running Android 10 or later will do, and Google says the check takes less than a minute. It does not collect the device's phone number, and one device can verify several accounts. Order matters: Google's identity page says phone number verification waits until identity and device verification are done.

Verifying an organisation account

An organisation account asks for more. As of 2 September 2026, Google's required information page lists a developer name; a D-U-N-S number, organisation name and address from your payments profile; an organisation phone number and website; a contact name, email and phone for Google; and a developer email and phone shown on Google Play. Three points are worth knowing:

• Use an address on your own domain. Google says the contact and developer email addresses for an organisation should not be generic or personal addresses.
• The organisation phone number is a check. Google wants the number people would find for you on the web or in a registry such as Dun & Bradstreet. It is not shown on Google Play.
• Phone verification waits for the website. For organisations, phone verification cannot start until identity and website verification are complete.

Website verification

Google introduced website verification for new organisation accounts in February 2024, and recommends it for every account. As of 2 September 2026, its Verify your website page says to register your site in Google Search Console, then send a verification request from the Account details page in Play Console. If the Google account that owns the site in Search Console is the same one you use for Play Console, the request is approved without a further step. If not, the site's owner in Search Console gets an email and has to approve or deny it. Google says social media profile URLs cannot be verified, so you need a real website.

D-U-N-S numbers for Google Play

A D-U-N-S number is a nine-digit identifier that Dun & Bradstreet assigns to businesses. As of 2 September 2026, Google's required information page says:

• You cannot create an organisation account without one.
• Getting a number from Dun & Bradstreet is free. Google warns about third-party services that charge high fees for this free registration.
• Many organisations already have one, so search Dun & Bradstreet's site before applying. Large organisations may have several; use the one holding the details you want on the account.
• A new number can take up to 30 days. Plan for it.
• If Dun & Bradstreet does not cover your region, contact Play support before you create the account to ask for another way to verify.
• Known government organisations and agencies can verify without a D-U-N-S number, through Play support.

Make the names match

Google says the legal name and address in your payments profile must match your Dun & Bradstreet profile. This is not a one-off check. If Google later detects a mismatch, you get an email and a banner in Play Console saying your organisation name or address is no longer verified. Fix it by the deadline given, or the account is restricted and all of its apps are removed from Google Play.

Small differences cause most of the trouble: "Ltd" against "Limited", or an old registered address. Copy the legal name and address from your registration document into both places, character for character. If you already have a D-U-N-S number from enrolling with Apple, it is the same number. Our guide to getting a D-U-N-S number for Apple covers the lookup in more depth.

After the account is set up

For a personal account created after 13 November 2023, the next hurdle is a closed test with at least 12 testers for 14 days. Our guide to the 12 testers, 14 days rule covers it step by step.

Play Console verification also carries over to Android developer verification: in March 2026 Google's Android Developers Blog said developers who have completed it are already verified, and that Google registers eligible Play apps for them. Our guide to Android developer verification covers the rest.

How FeedbackKit fits in

An account gets your app onto Google Play. It does not tell you what the people who install it want next, and a one-star review is a poor place to find out. The wait for verification is a good time to build that part.

FeedbackKit gives your users a place inside the app to post feature requests and vote on them. On Android it is a Kotlin SDK with Jetpack Compose screens (Kotlin docs), and there are SDKs for Flutter and React Native too. A new request starts with its submitter's vote, and voting stops when a request is Completed or Rejected. If you ship on iOS as well, requests from both platforms land on the same board. The pricing page lists the plans. Here is how voting looks in FeedbackKit, with sample data from a fictional hiking app:

Pick the account type that matches who you are, get the names matching before you apply, and give your users somewhere to say what they want. Start free with FeedbackKit when your app is ready for them.