Google Play Console Developer Account: Verification, D-U-N-S and ID Checks

Play Console Store team

November 18, 2026

Share:

Table of Contents

Estimated progress
Interactive Guide

Identity verification is the gate every Google Play Console developer account must pass — and the step where more launches stall than anywhere except the 14-day testing requirement. Google verifies every developer, no exceptions: individuals with government ID, companies with D-U-N-S numbers and business documents. Get it right and you’re publishing in days; get it wrong and you’re stuck in a rejection loop that can stretch for weeks.

This guide goes deep on verification specifically: what Google asks for, the exact document standards, the D-U-N-S process for organizations, the ten most common rejection reasons with fixes, and what happens after you’re verified. For the broader account picture, see our Google Play Console account guide.

In short: Google verifies every Play Console developer account. Personal accounts need a valid government photo ID, an exact legal-name match, a mobile number and the $25 fee, with decisions in hours to two days. Organization accounts also need a D-U-N-S number and business documents, taking one to three weeks. Fix the exact issue named in any rejection email before resubmitting.

Why Google Verifies Every Developer Account

Verification exists to fight fraud, malware, and policy evasion. Before mandatory verification, banned developers simply opened new accounts in minutes; today, identity checks make ban evasion dramatically harder. The practical consequences for legitimate developers:

  • Every new account is verified — personal and organization alike.
  • Existing accounts created before the mandate were progressively required to verify.
  • Verification status affects review speed and trust signals — unverified accounts can’t publish at all.
  • Information you provide (legal name, address) appears on your public developer profile — choose what you’re comfortable disclosing.
Personal identity verification steps with ID and shield checks

Personal Account Verification: Step by Step

What you need: a valid government-issued photo ID (passport, driver’s license, national identity card) and a mobile phone number.

The process:

  1. At play.google.com/console/signup, select personal account and enter your legal name exactly as it appears on your ID — including middle names and exact transliteration. Mismatches here cause a large share of rejections.
  2. Upload a photo or scan of your ID: all four corners visible, no glare or shadows over text, not expired, minimum legible resolution (a modern phone photo in good light works; a blurry webcam shot doesn’t).
  3. Confirm your phone number via the SMS code.
  4. Enter your physical address and contact email. The address should be a real residential address — PO boxes and virtual addresses raise flags.
  5. Pay the $25 registration fee and accept the Developer Distribution Agreement.

Timeline: a few hours to 2 days for clean submissions. You’ll get an email when verification completes; until then, console features show as pending.

Document tips that matter: non-Latin-script IDs are accepted but slow things down — if your ID has a Latin transliteration field, make sure it’s legible. Expired IDs are rejected automatically with no human review, so check the date before uploading. And never submit someone else’s ID — that’s fraud, and it permanently poisons that identity for future registrations.

The table below summarises the personal verification requirements:

RequirementDetail
IDValid government-issued photo ID (passport, driver’s license, or national identity card), not expired
NameLegal name entered exactly as it appears on the ID, including middle names and exact transliteration
ID photoAll four corners visible, no glare or shadows over text, minimum legible resolution
PhoneMobile phone number confirmed via SMS code
AddressReal residential address; PO boxes and virtual addresses raise flags
Fee and agreementPay the $25 registration fee and accept the Developer Distribution Agreement
TimelineA few hours to 2 days for clean submissions

Organization Verification: The D-U-N-S Process

Organization accounts verify the business, not just a person. The cornerstone is the D-U-N-S number — Dun & Bradstreet’s unique business identifier.

Getting a D-U-N-S number

  1. Check if you already have one at dnb.com — many registered businesses do without knowing it.
  2. If not, request one (free, but the standard process takes up to 30 days; expedited options exist for a fee in some regions).
  3. Ensure your D&B record lists your exact legal business name and registered address — this record is what Google checks against.

The verification submission

  1. Enter your D-U-N-S number at signup — Google pulls your D&B record automatically.
  2. Upload business registration documents: articles of incorporation, certificate of incorporation, business license, or tax registration — whatever officially proves the entity in your jurisdiction.
  3. Provide an official company website and a contact email on that domain (info@yourcompany.com, not a Gmail).
  4. The authorized representative (the human completing signup) verifies their own identity with government ID.
  5. Pay the $25 fee and accept the agreements.

Timeline: 1–3 weeks total is realistic — D-U-N-S acquisition plus Google’s review. Start the D-U-N-S request before you need the account; it’s the longest pole.

The 10 Most Common Verification Rejections (and Fixes)

  1. Name mismatch (personal): the name entered doesn’t exactly match the ID. Fix: copy character-for-character, including middle names.
  2. Blurry/cropped ID photo: corners cut off or text illegible. Fix: retake in daylight, all corners visible, no flash glare.
  3. Expired ID: automatic rejection. Fix: renew first — no workaround.
  4. D-U-N-S name/address mismatch: your documents say “Acme Ltd, Suite 400” but D&B says “Acme Ltd”. Fix: update the D&B record first, then resubmit — resubmitting unchanged documents fails again.
  5. No D-U-N-S found: number mistyped or not yet in D&B’s database. Fix: verify at dnb.com and allow propagation time.
  6. Personal email for organization account: signals a non-serious business. Fix: use a domain email.
  7. Unofficial business documents: screenshots, self-made PDFs, or documents that don’t prove legal registration. Fix: submit the actual government-issued registration certificate.
  8. PO box / virtual address: fails address credibility checks. Fix: use the real registered business address.
  9. Representative not authorized: the person signing up can’t prove authority over the business. Fix: have a director/officer complete signup, or provide authorization documentation.
  10. Repeated rapid resubmission: spamming the same rejected documents can trigger manual review delays. Fix: fix the cited issue first, then submit once, cleanly.

Critical rule: read the rejection email — it names the specific problem. Fix that, not what you guess the problem is.

The table below summarises the ten common rejections and their fixes:

Rejection reasonFix
Name mismatch (personal)Copy the name character-for-character from the ID, including middle names
Blurry/cropped ID photoRetake in daylight, all corners visible, no flash glare
Expired IDRenew first — there is no workaround
D-U-N-S name/address mismatchUpdate the D&B record first, then resubmit
No D-U-N-S foundVerify the number at dnb.com and allow propagation time
Personal email for organisation accountUse a domain email
Unofficial business documentsSubmit the actual government-issued registration certificate
PO box / virtual addressUse the real registered business address
Representative not authorisedHave a director/officer complete signup, or provide authorisation documentation
Repeated rapid resubmissionFix the cited issue first, then submit once, cleanly

Verification for Regulated Categories

Certain app categories face additional verification layers beyond standard developer verification:

  • Financial apps (banking, lending, trading): Google requires additional documentation proving regulatory licensing in operating jurisdictions. Start this early — financial verification is the slowest category.
  • Health apps handling sensitive data: expect scrutiny of your privacy practices and, in some regions, proof of compliance with health-data regulations.
  • Government-affiliated apps: require proof of official authorization to publish on behalf of the agency.
  • News apps: ownership transparency declarations.

If your app falls in these categories, budget extra weeks beyond standard verification and prepare regulatory documents alongside your D-U-N-S package. Publishing a financial app on a fresh personal account with no licensing documentation is a guaranteed rejection — the category determines the timeline as much as the account type. Our policy compliance guide details the declaration side.

After Verification: What Changes

Once verified:

  • The 14-day closed testing clock can start (for new personal accounts) — verification is a prerequisite, so delays here push your whole launch.
  • Your developer name and contact details go public on your store listings — review them under Setup → Developer account → Details.
  • You can be invited to other developer accounts as a team user, and invite others to yours.
  • Re-verification can be triggered later if you change key details (legal name, country) or if Google runs periodic checks — keep your documents current.

Google documents the current requirements in the Play Console Help Center — check it before starting, since document requirements evolve.

Google Play Console Developer Account: Key Takeaways

Verification is the gate every Google Play Console developer account must clear: exact-name matching for personal IDs, a clean D-U-N-S record for organizations, and real addresses throughout. Submit once, cleanly — each rejection resets the clock. Use the waiting time productively: listings, privacy policy, testers, and payments setup can all advance while Google reviews.

Organization verification with business documents and company number

Frequently Asked Questions

What ID does Google accept for Play Console developer verification?

Government-issued photo ID: passport, driver’s license, or national identity card. It must be valid (not expired), fully legible, with all corners visible in the photo. The name must match what you enter at signup character-for-character.

Do I really need a D-U-N-S number for an organization account?

Yes — it’s mandatory for organization verification. Request one free at dnb.com (allow up to 30 days standard processing). Your D&B record’s legal name and address must exactly match your business registration documents.

How long does Google Play developer account verification take?

Personal accounts: hours to 2 days with clean documents. Organization accounts: 1–3 weeks including D-U-N-S handling. Rejections reset the clock, so submit correctly the first time using this guide’s checklist.

Can I publish apps while verification is pending?

No. Publishing, testing tracks, and most console features stay locked until verification completes. Plan your timeline accordingly — verification delay is the most common reason launches slip.

What happens if my verification is rejected multiple times?

Each rejection email names the specific issue — fix exactly that before resubmitting. Repeatedly submitting unchanged documents can trigger extended manual review. If you’re stuck after fixing the cited issue, the appeal/reconsideration path is in the rejection email.

Conclusion

Verification is a paperwork sprint, not a marathon — but only if you prepare: exact-name matching, clean ID photos, a correct D-U-N-S record for companies, and real addresses throughout. The developers stuck in verification limbo are almost always fighting one of the ten fixable issues above.

Play Console Store is an independent marketplace that helps Android developers get verified fast — document preparation, D-U-N-S guidance, and rejection recovery. Explore our Google Play services and clear verification on the first submission.

KNOWLEDGE BASE

Related Android Developer Field Manuals

Googleplaystore Console FAQ: Answers for Developers

Search for “googleplaystore console” and you’ll find developers asking the same cluster of questions: What is it? Is it the

Google Play Developer Console Account: Policy Compliance Guide

Policy compliance is the invisible half of running a Google Play developer console account. Your code can be flawless and

Google Play Account Console: Payments, Tax Forms and Payouts

The Google Play account console handles the money side of your developer business: the payments profile where earnings land, the

Get notified when Google updates Play Console policies or SDK requirements.

Join 12,000+ Android developers who receive our quarterly policy diff summaries, rejection workarounds, and ready-to-use boilerplate releases.