Google Play Developer Verification: Evidence Checklist

Verification Overview

Google Play developer verification depends on account type, country, legal owner, public developer information, and the checks shown in Play Console. Personal and organization accounts do not use one universal document packet.

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.

Identity Verification

Play Console may ask the account owner or authorized representative to verify identity and contact information. Submit only a document type accepted for the country and account flow shown on screen.

Identity Evidence Checks

• Accepted type: use one of the identity documents listed in the current verification flow.
• Legal identity: reconcile the submitted name, date of birth, and representative role with the source record.
• Readable capture: include every requested side or page, with edges and security details visible.
• Validity: confirm that the document is current and that Play Console accepts its issuing country.

Address Verification

Enter the address of the real account owner or organization and keep it consistent with the evidence requested in the account. Public developer information, payments data, and verification records may have different display purposes, so do not copy fields without checking their labels.

If Address Evidence Is Requested

• Use a document category listed in the current verification prompt
• Check the permitted issue date or age shown for that document type
• Make the account name and address traceable to the same legal owner
• Preserve the submitted file and the Console request that defined the requirement

Do not assume that a utility bill, bank statement, tax record, virtual office, or P.O. box is accepted in every country. Verify the current list before obtaining or translating a document.

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

Google's organization-account flow uses a D-U-N-S Number to identify the legal entity, subject to the current eligibility and country rules in Play Console.

Compare the legal organization name and address in the linked Google Payments profile with the D&B record. Validate telephone, website, contact, and representative details against their own Play Console fields and supporting evidence. Resolve a substantive mismatch at the authoritative source rather than cycling through alternative spellings.

For the D&B record workflow, see our D-U-N-S Number Guide for Google Play.

Evidence Preparation Checklist

This is a preparation list, not a claim that Google requests every item from every account.

Personal Account Inputs

• Legal identity details and an accepted identity document if requested
• Current address and contact evidence if the verification flow asks for it
• Long-term account email and telephone access
• Record of the exact owner and public developer information entered

Organization Account Inputs

• Legal entity name and D-U-N-S record used by the current account flow
• Authorized representative and organization contact details
• Business registration, tax, or address evidence only when requested
• Public website and contact routes that accurately identify the publisher
• Account permissions showing who owns and maintains the verification record

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.

Mismatch Checks After a Verification Problem

These are diagnostic checks, not a ranked list of Google rejection causes:

• Identity mismatch — Account details do not resolve to the person or representative shown in the submitted evidence
• Unreadable or incomplete capture — A requested page, side, edge, or field is missing
• D-U-N-S discrepancies — Company name or address differs from D-U-N-S record
• Document validity — A submitted document falls outside the validity or issue-date rules shown in the request
• Address mismatch — Address proof does not match profile address
• Prior enforcement relationship — Ownership or account history requires a policy-specific review rather than a replacement registration
• Unclear account ownership — The identity, organization, payment, domain, or contact records point to different operators

Pre-Submission Review

• Capture the request first — Record the required field, accepted evidence type, deadline, and upload constraints shown in Play Console
• Check identity consistency — Resolve meaningful differences in legal name, address, telephone, and representative role
• Use readable files — Follow the current file format and quality rules; do not invent a DPI threshold that the flow does not state
• 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 the actual operating address — Confirm whether the requested evidence accepts the address type in the account's country
• Protect account access — Keep the primary email, telephone, recovery method, and authorized users current