Identify the account type and relevant profile
Personal and organization accounts request different information. Organizations generally need a D-U-N-S record; Google documents limited alternative routes for unsupported regions and eligible government organizations. Do not assume a personal identity document replaces the organization's required record.
In the current guidance, the identity-linked payments profile can be located through Developer account → About you → Developer profile. This is important when a business has multiple payments profiles: editing an unrelated merchant profile may leave the verification problem untouched.
Reconcile the evidence before submission
Check legal name, address, organization identifier, contact email and telephone against the records Google requests. Use consistent transliteration and genuine supporting documents. Never alter documents to conceal a mismatch.
| Mismatch | Practical next step |
|---|---|
| Old organization address | Correct the authoritative business/payment record |
| Wrong D-U-N-S entity | Confirm which legal organization owns the account |
| Unreachable verification contact | Restore a monitored email or phone channel |
| Multiple payments profiles | Identify the profile linked to developer identity |
Retain the case number and deadline from the actual Console notification. Account-owner permissions may be needed for corrections that a release manager cannot perform.
Separate verification from other gates
Identity verification is not app review, closed testing, payment-method verification or proof that a bundle uses the right signing key. Completing one does not automatically complete the others.
Android's broader developer-verification rollout also has distribution and regional rules. Read that program separately rather than treating every notification as the same Play account workflow.
Protect sensitive material
Submit identity documents only through the official workflow. Do not upload them to APKLint's policy checker, public issue trackers or a shared release spreadsheet. The checker can organize policy questions but cannot verify a legal identity.
Use the current account information requirements and the account's own notice. If the evidence is correct but rejected, provide a concise explanation and requested supporting material through the official support channel, without guessing at an undocumented approval shortcut.
Sources and further reading
Reference review: 22 September 2026. Examples illustrate the workflow; check your installed versions, release artifact and account-specific Console requirements before applying them. This guide is not a claim that APKLint executed your project or verified your private account.
Android inspection tools and practical release guides. About APKLint · Report a correction
