BlogVerification

Google Play Developer Verification Requirements: What You Need in 2026

Google has significantly tightened developer verification since 2023. This guide covers every verification step — identity, address, D-U-N-S, and business documents — so you can pass on the first attempt.

D
|Founder
|||
7 min read

Verification Overview

Every Google Play developer account must pass verification before publishing apps. The process varies by account type but generally includes identity verification, address verification, and (for organizations) D-U-N-S business verification.

Verification depends on account type, country, current documents, entity records, and follow-up requests. Build the schedule around those dependencies rather than a universal reviewer turnaround.

Decision boundary

The delivery team can check evidence consistency and prepare responses. Google and Dun & Bradstreet control their own verification times and outcomes.

Identity Verification

All developer accounts require identity verification. Google uses this to ensure the person registering is a real individual and to link the account to a verifiable identity.

What Google Checks

  • Government-issued photo ID — Passport, national ID card, or driver's license
  • Name match — The name on your ID must exactly match the name on your developer profile
  • Photo quality — Clear, unobstructed photos of both sides (if applicable)
  • Expiration — Your ID must not be expired at the time of submission

Identity consistency

Enter the legal name from the requested identity evidence and preserve meaningful characters, suffixes, and ordering. Resolve a mismatch with the source document or account instructions rather than guessing another format.

Address Verification

Google verifies your physical address to ensure you are reachable and operating from a legitimate location. This applies to both personal and organization accounts.

Accepted Address Proof

  • Utility bill (electricity, water, gas) from the last 3 months
  • Bank statement from the last 3 months
  • Government-issued letter or tax document
  • Business registration certificate (for organizations)

The address on your proof document must match the address in your developer profile. P.O. boxes are generally not accepted unless they are your registered business address.

D-U-N-S Verification (Organizations Only)

Organization accounts require a valid D-U-N-S number issued by Dun & Bradstreet. This 9-digit identifier verifies that your business is a real, registered entity.

Google cross-references your D-U-N-S record with your developer profile. The company name, address, and phone number must match exactly between your D-U-N-S profile and your Google Play developer profile.

For a complete walkthrough, see our D-U-N-S Number Guide for Google Play.

Exact Match Required

Even small differences like "Ltd" vs "Limited" or abbreviated street names can cause rejection. Verify your D-U-N-S profile matches your Google Play information character-by-character before submitting.

Required Documents Checklist

Personal Account

  • Government-issued photo ID (passport or national ID)
  • Proof of address (utility bill or bank statement, last 3 months)
  • Active phone number for 2FA setup

Organization Account

  • All personal account documents (for the account holder)
  • D-U-N-S number
  • Business registration certificate or articles of incorporation
  • Company website URL
  • Business phone number (must match D-U-N-S record)
  • Tax identification number (EIN, VAT, etc.)

Verification Stages

Track each stage and its owner:

  • Account setup: Select the correct owner type and enter current contact details.
  • Identity request: Submit only the evidence and format requested in Play Console.
  • Organization record: Confirm D-U-N-S and legal-entity data before cross-reference.
  • Follow-up: Preserve the case ID, requested correction, response, and document version.
  • Decision: Record approval or the exact reason and route supplied for remediation.

Reduce avoidable delay

Prepare one consistent evidence packet and respond while the documents are current. Our registration service checks the packet before submission; Google controls the review time.

Common Rejection Reasons

  • Name mismatch — Profile name does not match ID exactly
  • Blurry or incomplete ID photos — Both sides must be clearly visible
  • D-U-N-S discrepancies — Company name or address differs from D-U-N-S record
  • Expired documents — All documents must be current
  • Address mismatch — Address proof does not match profile address
  • Previously banned identity — Google detects links to a previously terminated account
  • Suspicious patterns — Multiple accounts from the same identity or device

Tips to Pass Verification on the First Attempt

  • Prepare everything first — Gather all documents before starting registration
  • Triple-check name consistency — Use the exact same name format across all documents and profiles
  • Use high-quality scans — 300 DPI minimum, no glare, all text legible
  • Update your D-U-N-S profile — If information changed, correct it with Dun & Bradstreet first and wait until the authoritative record reflects the update
  • Use a real address — Avoid virtual offices or P.O. boxes if possible
  • Set up 2FA early — Enable two-factor authentication on your Google account before applying

Professional Help

Our account registration service checks document consistency, account type, contact details, and D-U-N-S alignment before submission. The goal is to remove avoidable mismatches; Google makes the verification decision.

Evidence standard

Primary references

These first-party sources support the changeable platform requirements in this guide. Your current Play Console notice remains authoritative for account-specific steps.

Review your next Play Console step

Tell us what the account shows, where the release is blocked, and what has already been submitted. We will scope the work around the evidence in your case.

Discuss Your Release