The Google Play message "we couldn't verify your identity" means the identity check on your developer account did not pass, and for most people it comes down to one of two things: a document photo the scanner cannot read clearly, usually because of glare or blur, or a name on your ID that does not match the name on your Google payments profile or bank details. Recapture the document in even light with no glare and every corner visible, and make sure the name on your ID matches your payments profile exactly. Fixing the capture and the name match resolves the large majority of these errors.
Short answer
The error means your identity could not be confirmed from what you submitted, most often due to a glared or blurry document photo or a name mismatch with your payments profile. Per Google's identity verification guidance, you verify with a government-issued photo ID, so the scan must be clearly readable. Per Google's account requirements, the name and details on your account must be consistent, so the ID name has to match your Google payments profile and bank information. Recapture the document glare-free with all corners visible, align the name across your ID and payments profile, and retry. If a clearly valid document still fails, contact Google Play developer support.
What "we couldn't verify your identity" means
The message is Google telling you the automated identity check on your developer account did not succeed, so the account cannot proceed until it does. It is not a policy strike or a ban; it is a verification step that failed, usually because the check could not read your document clearly or could not reconcile your details. Because identity verification gates the account, the error blocks you from continuing setup until you pass, which is why it feels more severe than it is.
Reading it that way points you at the fix rather than the fear. You are not appealing a decision about your app; you are correcting the inputs so the check can confirm who you are. The two inputs that most often cause this specific error are the document image and the name consistency across your identity and payment details. Working on those, rather than assuming your account is in trouble, is what clears the message.
Fixing document glare and capture
Document glare and poor capture are the most common reason the check cannot read your ID, so recapturing the photo cleanly fixes many cases. Glare is the usual culprit: a reflection across the surface of the card or passport, often from a flash or an overhead light, washes out part of the document so the scanner cannot read it. Blur, low light, and a cropped edge cause the same failure by making details unreadable.
Recapture the document with technique in mind. Use even, indirect light rather than a direct flash, which is what creates glare, and tilt the document slightly if a reflection persists until the surface reads clearly. Keep the whole document in frame with all four corners visible and nothing covered by a finger, hold the camera steady so the text is sharp, and use the original physical document rather than a photocopy or a photo of a screen. A flat, evenly lit, in-focus capture of the entire document is what the scanner needs, and it resolves most glare-driven failures.
Name mismatch with your bank or payments profile
A name that does not match across your ID and your payment details is the other leading cause of this error. Google links your developer account to a Google payments profile, and the name on your government ID needs to match the name on that profile and the associated bank or payment information. When your ID says one name and your payments profile or bank shows another, for example a maiden name versus a married name, a missing middle name, or a different spelling, the check cannot reconcile them and reports that it could not verify your identity.
Fix this by making the names consistent. Compare the name printed on the ID you are submitting against the name in your Google payments profile and the bank details on file, and correct whichever is wrong so they read identically. If your legal name genuinely changed, update the record that is out of date to your current legal name rather than forcing a mismatch. Because the payment and identity details are checked together, aligning the name across all of them is often the single change that turns a repeated failure into a pass.
Other reasons the check can fail
Beyond glare and name mismatch, a few other issues cause this error, and they are worth ruling out. The document must be current and of a type Google accepts for your country; an expired ID or a document type that is not accepted for your region will fail regardless of how clean the photo is. If you have tried several times with a readable image and a matching name, the document type or its validity is the next thing to check against your country's accepted list.
For organization accounts, the same consistency requirement extends to your business details and, where required, your Dun and Bradstreet record, which must match your payments profile. That organization-specific side has its own depth, but the same principle holds: the check fails when the details do not reconcile. If none of the common personal-account causes apply and you are certain the document and names are correct, that is the point to contact Google Play developer support and ask them to look into the verification.
How to retry cleanly
Retrying works best when you change what caused the failure rather than resubmitting the same inputs. Before you try again, fix the specific problem: recapture the document to remove glare and include all corners, or correct the name so it matches across your ID and payments profile. Submitting the identical photo or the same mismatched name again will produce the same result, so make a real change first.
When you retry, submit one clean attempt rather than many rapid ones. Use good lighting, a steady hand, and the original document, and double-check the name consistency before you send. If repeated, genuinely-corrected attempts still fail, stop retrying and contact support, because at that point the issue may need a human to review rather than another automated attempt. A deliberate, corrected retry is far more likely to pass than a fast repeat of the same submission.
Causes and fixes
Matching the cause to a fix keeps you from resubmitting the same failing inputs. The table below pairs the common causes with their fixes.
| Cause | What it looks like | Fix |
|---|---|---|
| Document glare or reflection | Washed-out area, unreadable scan | Recapture in even light, no flash |
| Blur or cropped capture | Fuzzy or missing corners | Hold steady, include the whole document |
| Name mismatch with payments or bank | ID name differs from the payments profile | Align the names across ID, profile, and bank |
| Expired or unsupported document | Rejected regardless of photo quality | Use a current, accepted document |
| Photocopy or photo of a screen | Fails the scan | Capture the original physical document |
Read the table against your attempt. The top two rows are capture problems, and the name row is a consistency problem, and together they cover most of this error.
Capture and consistency checklist
Working through both the capture and the name consistency resolves most failures. The checklist below covers the steps.
| Check | Action | Done? |
|---|---|---|
| Lighting | Even, indirect light with no flash glare | [ ] |
| Framing | All four corners in frame, nothing covered | [ ] |
| Focus | Text sharp and readable | [ ] |
| Original document | Physical ID, not a copy or screen | [ ] |
| Name match | ID matches payments profile and bank | [ ] |
| Validity | Document current and accepted for your country | [ ] |
The two that resolve most cases are a clean, glare-free capture and a name that matches across your ID, payments profile, and bank details. Confirm both before retrying.
After you verify, secure the build
Passing identity verification lets you finish setting up your account and move toward publishing, which makes the app you ship the next thing worth checking. Clearing the identity check confirms who you are; it says nothing about whether your build carries risky third-party code, leaked keys, or over-broad permissions that could cause trouble at review or after release.
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 payments profile. It checks the build, which is the next thing that matters once your account is verified.
What to take away
- The "we couldn't verify your identity" message means the identity check failed, not that your account is banned, so fix the inputs rather than panic.
- The most common cause is a glared or blurry document photo, so recapture in even light with no flash, all corners visible, and the text sharp.
- The other leading cause is a name that does not match across your ID, Google payments profile, and bank details, so align them exactly.
- Rule out an expired or unsupported document, retry with one clean corrected attempt, and contact support only if a valid, matching submission still fails.
- Once verified, scan your build with PTKD.com so a security issue does not undo the account you just set up.
