Most developers underestimate what it actually takes to publish on Google Play until their account gets rejected or suspended.
The Google Play developer account requirements changed significantly in 2023, adding mandatory identity verification, D-U-N-S numbers for organizations, and stricter app-level compliance checks that directly affect account standing.
Google banned over 158,000 developer accounts in 2024 alone. Getting these requirements wrong is not a minor inconvenience.
This article covers every requirement across registration, identity verification, payment setup, policy compliance, and ongoing enforcement so you know exactly what to prepare before and after your account goes live.
What Are Google Play Developer Account Requirements?
A Google Play developer account is the registered identity through which individuals or organizations publish apps on the Google Play Store.
Requirements fall into 3 categories: identity verification, payment, and policy compliance.
All 3 must be met. Missing even one blocks app publication entirely.
The account is governed by 2 core documents: the Android-specific Developer Distribution Agreement and the Google Play Developer Program Policies. Both must be accepted before a developer can publish a single app.
As of August 31, 2023, Google restructured the entire registration process. Before that date, a valid email and a $25 payment were enough to go live. That’s no longer the case.
Google blocked 2.36 million policy-violating apps and banned 158,000 developer accounts in 2024 alone (Google Play Transparency Report, 2025). The verification overhaul is a direct response to that scale of abuse.
Requirements differ between personal and organization accounts. Personal accounts need a government-issued ID. Organization accounts additionally require a D-U-N-S number from Dun & Bradstreet.
| Requirement Category | Personal Account | Organization Account |
|---|---|---|
| Registration fee | $25 USD (one-time) | $25 USD (one-time) |
| Identity verification | Government-issued ID | D-U-N-S number and business documentation |
| Contact info | Verified email address and phone number | Public-facing email address and phone number |
| Payments profile | Personal payments profile | Business payments profile (legal business name must match the D-U-N-S record) |
Who Can Register for a Google Play Developer Account?
Google sets 3 baseline eligibility conditions: age, geography, and account type. All 3 apply regardless of whether you’re registering as an individual or a company.
The minimum age is 18 years old. Minors cannot hold a developer account directly.
Google Family Link accounts are explicitly excluded from registration eligibility. A standard Google account is required.
Individual vs. Organization Account Eligibility
Personal accounts are for solo developers publishing under their own legal name.
Organization accounts cover companies, non-profits, government bodies, and academic institutions. As of July 2024, Google also requires developers offering financial services, health apps, VPN services, or government-related apps to register as an organization, not an individual (Google Play Policy Update, July 2024).
One Google account maps to one developer account. Creating duplicate accounts after a termination violates Google’s policies and results in the new account being closed without a registration fee refund.
Countries Where Google Play Developer Accounts Are Restricted
Developer registration is available in most countries, but merchant accounts for paid apps have geographic restrictions.
Google maintains a supported countries list for merchants. Developers in unsupported regions can publish free apps but cannot sell paid apps or offer in-app purchases.
- Distribution of free apps: available in 190+ countries
- Merchant accounts for paid content: restricted to Google’s approved merchant country list
- Payment methods accepted: credit and debit cards (no prepaid cards, no virtual cards for the registration fee)
Card-issuing country matters. Google cross-checks the card’s country of issue against the account’s registration region and current IP location. Mismatches trigger payment failure during the $25 fee step.
What Is the Google Play Developer Registration Fee?

The registration fee is $25 USD, paid once, non-refundable.
This covers unlimited app publications under the same account. There is no annual renewal fee for the account itself. No per-app charge. No recurring subscription.
For context: Apple charges $99 per year for its developer program. Over 5 years, Google Play costs $25 total vs. Apple’s $495 (SplitMetrics, 2025).
How the Fee Is Paid
Payment method: credit or debit card only. Google does not accept prepaid cards, most virtual cards, Alipay, or WeChat Pay for this charge.
The fee is paid during the sign-up flow in the Google Play Console. Payment happens before identity verification completes, but the account is not active until verification passes.
If the payment fails, the most common cause is a prepaid card or a region-mismatched card. The fix is using a card issued in the same country as the registration region.
What the Fee Does Not Cover
The $25 grants account access. It does not cover the service fee on paid app revenue.
- 15% service fee on the first $1 million in annual earnings (enrollment in the reduced-fee tier required)
- 30% on earnings above $1 million for the remainder of that calendar year
- 15% from day one on auto-renewing subscriptions, regardless of total annual revenue
These fees only apply when monetizing through Google Play Billing. Free apps with no in-app purchases incur no ongoing fees beyond the one-time $25 (SplitMetrics, 2025).
What Identity Verification Does Google Require?

Google introduced expanded identity verification on August 31, 2023. Before that date, no ID was required to go live. Now, all accounts must verify identity before publishing any app.
The type of verification differs by account type. Both require a verified email address and phone number. What changes is the documentation.
Individual Identity Verification Steps
Personal accounts require a government-issued identity document. Accepted formats include a national ID card, driver’s license, passport, or residence permit.
PDF scans are not accepted. Google requires a photo (image file) of the document.
After document upload, identity verification goes through Google Payments. The developer receives an email with the subject “You need to verify your identity” containing a “Verify now” button to complete the final step. Approval typically takes a few hours to 2 business days.
Organization Verification and D-U-N-S Number Requirements
Organization accounts require a D-U-N-S number issued by Dun & Bradstreet. This is a unique 9-digit identifier assigned to business entities globally.
Requesting a D-U-N-S number is free but takes up to 30 days. Google strongly recommends starting this process before beginning account registration.
The legal name and address in the Google Payments profile must exactly match the information on file with Dun & Bradstreet. A mismatch causes verification failure and delays account activation.
Organizations also need to submit one official business document. Accepted documents include:
- Certificate of incorporation or business registration
- Business license
- VAT or tax registration certificate
- EIN verification letter (CP 575) for US entities
- SEC filings (Form 10-K, 10-Q, or 8-K) for publicly traded companies
Submitting unsupported or modified documents is the primary reason for verification failures, according to Google’s Play Console Help documentation. Providing fake documents leads to immediate account removal.
What Information Is Required During Account Setup?
The setup collects 2 types of information: private data used only by Google internally, and public data shown on the Play Store to users.
| Field | Visibility | Personal Account | Organization Account |
|---|---|---|---|
| Developer name | Public | Can differ from the legal name | Company or organization name |
| Legal name & address | Public (organization) / Private (personal) | Taken from the Payments profile | Must match the D-U-N-S registration |
| Developer email | Public | Required and verified | Required and verified |
| Developer phone | Public (organization only) | Not displayed publicly | Required and publicly displayed |
| Website URL | Optional / Public | Optional (recommended) | Required for new organization accounts |
The developer name appears on all app store listings and can be changed later. Everything else tied to the Payments profile is harder to update because changes require re-verification.
Contact email and phone must remain operational and verified for the entire lifetime of the account. An email address that bounces or a disconnected phone number puts the account at risk of suspension.
New organization accounts created after February 2024 are also required to verify website ownership as part of the identity check (Google Play Console Help, 2024).
What Are the Google Play Developer Program Policy Requirements?
Accepting the Developer Distribution Agreement (DDA) is a registration prerequisite. Developers who have previously violated this agreement cannot create a new account.
The DDA is not a one-time checkbox. It governs every action taken under the account, from app updates to monetization choices.
Developer Distribution Agreement: What Developers Agree To
The DDA covers 5 enforcement areas: restricted content, privacy and data handling, deceptive behavior, monetization practices, and spam and minimum functionality standards.
Accepting the DDA means agreeing that Google can remove any app at any time for policy violations, and that account termination voids the registration fee without refund.
In 2023, Google blocked 2.28 million policy-violating apps from publication and banned 333,000 developer accounts (Google, via Statista, 2023). In 2024, those numbers were 2.36 million apps blocked and 158,000 accounts banned (Google Play Transparency Report, 2025).
Restricted Content Categories That Disqualify Apps
Certain content types result in immediate app removal and potential account termination. These are non-negotiable and not subject to appeal in most cases.
- Malware and spyware: apps designed to harm devices or harvest data without user consent
- Sexual content involving minors: zero-tolerance, permanent ban
- Hate speech: content promoting violence or discrimination against protected groups
- Deceptive behavior: impersonating other apps, brands, or developers
- Unauthorized data access: requesting sensitive permissions without a justified use case
Google uses a combination of automated AI models and human reviewers to detect violations. As of 2024, over 92% of human reviews for harmful apps are now AI-assisted, allowing faster detection before apps reach users (Google Play Transparency Report, 2025).
How the Strike System Works
Policy violations accumulate as strikes against the account’s standing. Multiple strikes result in termination of the developer account and all related accounts.
Serious violations (malware, fraud, content that harms users) skip the strike process and go straight to termination.
As of October 2025, Google introduced a 180-day appeal window for account terminations, replacing the previous 7-day window. Appeals are submitted through the Google Play Console Help Center. Any new account created after termination is also terminated without a refund (Google Play Policy Announcement, October 2025).
What Are the Requirements for Publishing Paid Apps or In-App Purchases?

A standard developer account lets you publish free apps. Selling paid apps or offering in-app purchases requires a separate step: setting up a Google Play Payments merchant account.
The merchant account is distinct from the developer account. Developers can hold a verified developer account without a merchant account as long as they only publish free apps.
Google Play Payments Merchant Account Setup
Requirements for the merchant account:
- Valid bank account in a Google-supported merchant country
- Legal name and address matching the developer account’s Payments profile
- Tax identification information (varies by country)
- For organizations: legal name must also match the D-U-N-S number on file
The merchant account is created through Google Payments Center. It links to the same Payments profile used during developer account setup, so any name or address discrepancy between the two causes payout issues.
Developers earn money through app pricing models including paid downloads, one-time in-app purchases, and auto-renewing subscriptions. Each follows the same tiered service fee structure.
Tax Form Requirements by Region
Tax forms are required before Google processes payouts.
- US developers: W-9 form (individual taxpayer identification)
- International developers: W-8BEN (individuals) or W-8BEN-E (entities) to certify foreign status and avoid US withholding tax
- 1099-K threshold: Google files a Form 1099-K for US developers earning more than $20,000 in gross sales with more than 200 transactions per year (Google Play Console Help, 2024)
Google acts as the merchant of record in most countries and handles VAT, GST, and sales tax collection on behalf of developers. This means, for most regions, developers do not charge tax directly to users on Google Play transactions (Afternoon Blog, 2026).
Developers earning through alternative billing in the US (a change resulting from the Epic v. Google ruling, effective October 29, 2025) may have different tax obligations depending on how transactions are routed.
What Are the App-Level Requirements That Affect Account Standing?
App-level compliance is not separate from account compliance. A violation at the app level becomes a strike against the account.
Enough strikes, and the account is terminated, not just the app. Every submission decision carries account-level risk.
Data Safety Section Requirements
Every app published on Google Play must complete the Data Safety form in Play Console, regardless of whether it collects user data.
Apps that collect zero data still need to complete the form and link to a privacy policy confirming that fact.
The Data Safety section went live for users in April 2022. Since July 2022, approved Data Safety forms have been required for all new app submissions and updates (Adjust Help Center, 2022).
The form covers 4 areas:
- Whether the app collects or shares user data
- What specific data types are collected or shared
- The purposes for each data type
- Security practices, including whether data is encrypted in transit
In late 2024, Google began cross-checking Data Safety form declarations against actual runtime behavior using machine learning. Apps where declared data practices don’t match what the app actually does get flagged for review (Idea2App, 2025).
Target API Level Requirements
Google raises the minimum API level requirement each year. Missing the deadline limits app visibility, not just new submissions.
As of August 31, 2025, new apps and updates must target Android 15 (API level 35) to be submitted. Existing apps must target Android 14 (API level 34) or higher to remain discoverable on devices running Android 15 or 16 (Google Play Console Help, 2025).
Apps falling below the threshold don’t get removed. They become invisible to users on newer Android versions, which cuts reach significantly on a platform with 2.5 billion monthly active users (Appinventiv, 2025).
| Form Factor | New Apps (from Aug 31, 2025) | Existing Apps (from Aug 31, 2025) |
|---|---|---|
| Mobile / Android Auto | API level 35 (Android 15) | API level 34 (Android 14) |
| Wear OS | API level 34 (Android 14) | API level 33 (Android 13) |
| Android TV | API level 34 (Android 14) | API level 33 (Android 13) |
Google offers a deadline extension to November 1, 2025 for developers who need extra time. Extension requests are submitted through Play Console.
Beyond API level, all new app submissions must use the Android App Bundle (AAB) format. Google deprecated APK-only submissions for new apps in August 2021. The AAB format uses Dynamic Delivery, where Google generates optimized, device-specific APKs from the bundle rather than distributing a single large APK to all users.
What Causes a Google Play Developer Account to Be Rejected or Terminated?

Rejection and termination are different outcomes with different consequences. Rejection applies to an app submission. Termination removes the entire account and all apps within it.
Google prevented 1.75 million policy-violating apps from being published and banned over 80,000 developer accounts in 2025 (Google, Help Net Security, 2026).
Account Rejection at Registration
False identity information is the fastest path to registration rejection.
Google cross-references submitted identity data against Dun & Bradstreet records (for organizations) and government databases. Mismatches trigger identity verification failure before the account goes live.
Submitting modified or fake documents causes immediate rejection. Google’s Play Console Help documentation lists this as the primary reason for developer verification failures.
Payment fraud also blocks registration. If the $25 registration fee triggers a chargeback or fraud flag, the account is placed under review and may be denied before any app is published.
Account Suspension Triggers
Suspension is a mid-level enforcement action. The account stays open, but the flagged app is removed from the Play Store.
Suspension causes:
- Single serious policy violation (malware, deceptive behavior, unauthorized data access)
- Repeated app rejections for the same violation type
- Data Safety form discrepancies confirmed by automated runtime checks
- Chargeback patterns or payment abuse linked to the account
Each suspension adds a strike. Multiple strikes trigger account termination review. Google flags related accounts using shared identifiers, including device fingerprints, IP addresses, and payment methods (Google Play Enforcement Process, 2024).
Permanent Account Termination
Termination removes all apps from the Play Store permanently. Existing users lose access to in-app purchases and billing features.
Any new account created after termination is also terminated without a registration fee refund (Google Play Console Help, 2024).
Inactive accounts face closure too, though under different conditions. Google closes dormant accounts that haven’t been used in 180 days, have fewer than 1,000 combined lifetime installs across all apps, and haven’t verified contact phone number and email (Google Play Console Help, 2024).
Reminder emails go out at 60, 30, and 7 days before closure. The registration fee is not refunded on inactivity-based closures either.
How Does Google Enforce Developer Account Requirements After Registration?

Registration is the beginning of compliance, not the end. Google’s enforcement runs continuously across the account lifecycle.
Google runs more than 10,000 safety checks on every app and continues checking apps after they are published, not just at submission (Google, 2025).
How to Appeal a Policy Violation or Account Suspension
Appeals are submitted through the Google Play Console Help Center. Account owners or admins are the only roles that can submit an appeal.
As of October 2025, the appeal window for account terminations is 180 days from the date of termination. This replaced the previous shorter window. Google states that most developers whose suspensions are overturned appeal well within that 180-day period (Google Play Policy Announcement, October 2025).
The appeal process steps:
- Log in to Play Console and access the Help section
- Select “I received a policy enforcement and want to appeal”
- Submit specific detail about the app, its functionality, and why the action may be in error
- Wait for review (timeline varies; Google does not publish average resolution times)
Google does not guarantee reinstatement. Accounts terminated for patterns of high-risk behavior or association with previously terminated accounts are rarely reinstated regardless of appeal quality.
Re-Verification Requirements for Inactive Accounts
Developers who haven’t engaged with Play Console within 180 days receive inactivity closure warnings.
To keep an account active, developers must log in to Play Console regularly, maintain verified contact information, and have at least 1,000 cumulative installs across all apps in the account.
Verified contact email and phone number must remain operational at all times. A bounced email or disconnected phone number removes a layer of Google’s ability to communicate enforcement actions, which itself puts the account at risk.
In 2025, Google also integrated generative AI models into its review process to help human reviewers identify complex malicious patterns faster, and prevented over 255,000 apps from gaining excessive access to sensitive user data (Google, Help Net Security, 2026).
For teams managing mobile application development across multiple apps, the most practical way to avoid enforcement surprises is to treat Play Console as a live dashboard rather than a one-time submission portal. App status changes, policy updates, and enforcement notices all appear there before email notifications go out.
Google also offers Play Academy training courses covering Developer Program Policies. Completing these courses as part of the Strike Removal Program can reduce strike counts for eligible accounts, though eligibility requires a direct invitation from Google.
FAQ on Google Play Developer Account Requirements
How much does it cost to create a Google Play developer account?
The registration fee is $25 USD, paid once. There is no annual renewal. The fee is non-refundable, even if your account is later closed or you never publish an app.
What is the minimum age to register a Google Play developer account?
You must be at least 18 years old. Minors cannot hold a developer account directly. Google Family Link accounts are not eligible for developer account registration.
Do I need a D-U-N-S number to create a developer account?
Only organization accounts require a D-U-N-S number. Personal accounts do not. The D-U-N-S number is a free 9-digit identifier from Dun & Bradstreet and can take up to 30 days to obtain.
What identity documents does Google require for individual accounts?
Personal accounts require a government-issued ID such as a passport, national ID card, or driver’s license. PDF scans are not accepted. Google requires a photo image of the document during the verification process.
Can I create a new Google Play developer account after my old one was terminated?
No. Google terminates any new account linked to a previously terminated account. This includes accounts sharing the same device, IP address, or payment method. The $25 registration fee is not refunded.
What happens if I don’t complete the Google Play developer account verification?
Unverified accounts cannot publish apps. If an existing account misses its assigned verification deadline, all apps are removed from the Play Store and the developer profile is deleted.
Is a privacy policy required to publish an app on Google Play?
Yes. Every app must link to a privacy policy hosted on a publicly accessible, non-geofenced URL. Apps that collect no user data still need a privacy policy stating that no data is collected.
What is the Google Play Data Safety section and is it mandatory?
The Data Safety section is a mandatory form in Play Console disclosing how your app collects, shares, and secures user data. All apps must complete it, including apps that collect no data at all.
What Android API level do new apps need to target in 2025?
New apps and updates submitted from August 31, 2025 onward must target API level 35 (Android 15). Existing apps must target API level 34 to remain discoverable on devices running Android 15 or 16.
How do I appeal a Google Play developer account suspension?
Submit an appeal through the Google Play Console Help Center. Only account owners or admins can file. The appeal window is 180 days from the termination date, introduced in October 2025.
Conclusion
This conclusion is for an article presenting Google Play developer account requirements as they stand after the major policy overhaul that began in August 2023.
The registration process now involves identity verification, D-U-N-S number submission for organization accounts, Data Safety form completion, and ongoing API level compliance.
Each layer connects directly to account standing. A lapse in any one of them, whether a missed verification deadline, an inaccurate data safety declaration, or a policy strike, puts your entire app catalog at risk.
The developer program enrollment process is stricter than it used to be, but the logic is straightforward: meet every requirement upfront, keep your contact information verified, and treat Play Console as an ongoing compliance tool rather than a one-time setup step.
- Google Play Developer Account Requirements - September 14, 2026
- Laravel Cheat Sheet - September 13, 2026
- AI Agent Development for Healthcare and Financial Services: A Compliance Playbook - September 13, 2026



