Google Play identity verification usually fails for a readable reason: a blurry or glared photo the automated scan cannot read, an expired or unsupported document, a name that does not match your account, or, for organization accounts, a D-U-N-S record that does not match your Google payments profile. Fix it by retaking the ID photo in good light with every corner visible, using a document type accepted for your country, and making the name and address on the document match your account exactly. For organization accounts, align the legal name and address in your payments profile with your Dun & Bradstreet record before resubmitting.
Short answer
Most verification failures come from an unreadable photo, an unsupported or expired document, or a name and address mismatch. Per Google's developer identity verification, you submit a government-issued photo ID, and the accepted document types depend on your country. Retake the photo sharp and glare-free with all corners visible, use a document accepted for your region, and match the name to your account. For organization accounts, per Google's account requirements you also need a D-U-N-S number, and the legal name and address in your Google payments profile must match your Dun & Bradstreet record, so align them before resubmitting.
Why identity verification fails
Verification fails when the automated check cannot confirm your identity from what you submitted, and that usually traces to the document or the details, not to you being ineligible. The most frequent cause is a photo the scan cannot read: glare, blur, a cropped corner, or poor lighting. Close behind are documents that are expired or not accepted for your country, and a name on the document that does not match the name on your account.
Seeing it this way tells you where to look first. Before assuming your account is blocked, check the quality of the image, whether the document type is one Google accepts for your region, and whether the name matches exactly. For organization accounts, add a fourth check: whether your D-U-N-S record and payments profile agree. Most failures are one of these specific, fixable problems rather than a permanent rejection.
Passport vs ID card: which document to use
Which document to use depends on your country, because Google accepts different government-issued photo IDs by region rather than one universal list. Per Google's required documents by country, the accepted types vary, so a national ID card or driver's license that works in one country may not be accepted in another. A passport is the most widely accepted document across regions, which makes it the safer choice when you have one.
So if an ID card or driver's license was rejected, do not assume the whole process is broken; check your country's accepted list and try a different accepted type, often the passport. Make sure whichever document you choose is current and that the name on it matches your account. Choosing an accepted, valid document up front avoids a rejection that has nothing to do with the photo quality and everything to do with the document type.
Fixing a rejected photo or document
When the document type is fine but verification still fails, the photo is the usual culprit, and retaking it fixes most cases. Photograph the ID in even, bright light with no glare or reflection across the surface, keep it in sharp focus, and include all four corners with nothing cropped or covered by a finger. Use the original document rather than a photocopy or a photo of a screen, since those often fail the scan.
Check the document itself as well: it must be current, not expired, and legible, with the name and details clearly readable. If the automated check keeps rejecting a document you believe is valid and accepted for your country, that is the point to contact Google Play developer support through the Help option in the Console, describe the issue, and ask them to review it. A clear, well-lit photo of a valid, accepted document resolves the large majority of failures.
D-U-N-S mismatch on organization accounts
For organization accounts, a D-U-N-S mismatch is a leading cause of failure. Per Google, an organization account requires a D-U-N-S number, a unique nine-digit identifier from Dun & Bradstreet, and the legal name and address in your Google payments profile must match those in your Dun & Bradstreet record. When the two disagree, even by a small difference in the business name or address, verification fails because Google cannot reconcile the organization's identity.
Fix this by making the two records agree. Look up your organization with Dun & Bradstreet to see the exact legal name and address on file, then either correct the details in your Google payments profile to match that record, or, if the D-U-N-S record itself is outdated, update it with Dun & Bradstreet. Updates to a D-U-N-S record take time to propagate before Google sees them, often up to about two weeks, so make the change, allow it to sync, and then resubmit rather than retrying immediately.
Name and address must match exactly
Across both account types, the theme is that the details have to match exactly, and small differences cause failures. For personal accounts, the name on your photo ID must match the name on your developer account; a middle name present in one place and absent in another, or a different spelling, can be enough to fail. Correct whichever side is wrong so the two read identically before you resubmit.
For organization accounts, the same applies to the legal name and address across your payments profile and your D-U-N-S record. Treat exact matching as the goal rather than close-enough, including punctuation and address formatting where it matters. Because these details flow into how Google verifies you, getting them consistent is often the single change that turns a repeated failure into a pass, so review them carefully before assuming the problem is something harder.
Causes and fixes
Matching each cause to its fix keeps you from resubmitting the same failing document. The table below pairs the common causes with their fixes.
| Cause | Why it fails | Fix |
|---|---|---|
| Blurry or glared photo | The scan cannot read the document | Retake in good light, all corners visible |
| Expired or unsupported document | Not valid or not accepted | Use a valid type accepted for your country |
| Name mismatch | ID name differs from the account | Make the names match exactly |
| D-U-N-S mismatch (organization) | Payments profile differs from the D&B record | Align both, then allow sync time |
| Missing organization documents | An org needs two document types | Provide a registration document and a representative's ID |
Read the table against your own submission. Personal accounts usually fail on the top three rows; organization accounts add the bottom two.
Fix checklist
Working through the checks in order resolves most failures. The checklist below covers the steps.
| Check | Action | Done? |
|---|---|---|
| Document type | Accepted for your country | [ ] |
| Photo quality | Sharp, no glare, all four corners | [ ] |
| Name match | ID matches the account name exactly | [ ] |
| Validity | Document is current, not expired | [ ] |
| D-U-N-S (organization) | Legal name and address match the D&B record | [ ] |
| Organization documents | Registration document plus a representative's photo ID | [ ] |
The two that resolve most personal-account cases are a clean photo of an accepted document and an exact name match. For organizations, aligning the D-U-N-S record with the payments profile is usually the deciding fix.
After you verify, secure the build
Passing identity verification lets you get your account fully set up and publish, which makes the next concern the app you ship. Clearing verification confirms who you are; it does not tell you whether your build carries risky third-party code, leaked keys, or over-broad permissions that could draw a policy rejection later.
A scanner like PTKD.com analyzes your build and reports findings by severity, mapped to OWASP MASVS, so security issues surface before you submit rather than after. To be clear about the boundary: PTKD does not handle identity verification, your documents, or your D-U-N-S record. It checks the build, which is the next thing that matters once your account is verified.
What to take away
- Identity verification usually fails for a readable reason: an unreadable photo, an expired or unsupported document, or a name and address mismatch.
- Which documents are accepted depends on your country, and a passport is the most widely accepted type, so try it if an ID card was rejected.
- Retake the ID photo in good light with all four corners visible and in sharp focus, using the original document rather than a copy or a screen.
- For organization accounts, the legal name and address in your Google payments profile must match your Dun & Bradstreet record; align them and allow sync time before resubmitting.
- Once verified, scan your build with PTKD.com so a security or policy issue does not undo the account you just set up.
