Google's own review of the identity information you submit usually takes a few days, often up to about five, and you receive an email when it is done. The part that takes much longer applies only to organizations: obtaining a D-U-N-S number from Dun & Bradstreet can take up to about 30 days, which is why Google tells you to start early. Personal accounts are faster, since they verify your identity details rather than a business. Most verification failures come from a name or address that does not match your records.
Short answer
Google's review of your submitted details typically takes a few days, up to about five, per Google's account verification documentation. For a personal account, that is usually the whole wait. For an organization, the long part is getting a D-U-N-S number, which can take up to roughly 30 days from Dun & Bradstreet, so start early. Verification most often fails when your legal name or address does not exactly match your D-U-N-S record, which shows as a banner in Play Console. Resubmitting after you correct the mismatch is the fix; there is no fixed guaranteed time, so allow a few days for the re-review.
How long does each part take?
The timeline has two very different halves: Google's review of your submission, which is measured in days, and, for organizations, obtaining or correcting a D-U-N-S number, which can be measured in weeks. Confusing the two is why the wait feels unpredictable. The table below separates them.
| Step | Who it applies to | Typical time | Notes |
|---|---|---|---|
| Google identity review | Personal and organization | A few days, up to about 5 | You get an email when complete |
| Get a D-U-N-S number | Organizations only | Up to about 30 days | Free from Dun & Bradstreet, start early |
| D-U-N-S detail update | Organizations | Days to weeks | Changes take time to reach Google |
| Fix a mismatch and re-verify | Both | A few days after the correction | No fixed guarantee |
The practical takeaway is that if you are a personal developer, plan for a few days, and if you are an organization without a D-U-N-S number yet, plan for weeks and begin immediately. The D-U-N-S step, not Google's review, is almost always what makes verification slow.
Personal vs organization verification
Which path you are on determines how long you wait. A personal account verifies you as an individual, checking your identity details, and Google's review of that is typically a few days. There is no D-U-N-S number involved, so it is the faster route by a wide margin.
An organization account verifies a business, and that requires a D-U-N-S number, plus a legal name and address that match your Dun & Bradstreet record. The added step, and the time to obtain or align the D-U-N-S number, is what makes organization verification longer. If you have a genuine choice and do not need an organization account, personal is simpler; if you need an organization account, expect the D-U-N-S timeline.
The D-U-N-S number: the long pole
A D-U-N-S number is a nine-digit business identifier issued by Dun & Bradstreet, and it is the single biggest source of delay in organization verification. If your business does not already have one, requesting it can take up to about 30 days, and Google specifically recommends starting the process early so it does not block your account. You enter it through your Google payments profile.
The wait is on Dun & Bradstreet's side, not Google's. Once you have a valid D-U-N-S number whose details match your payments profile, Google's own review is back to the few-days range. So the strategy is simple: get or confirm the D-U-N-S number first, well ahead of when you need to publish, and treat Google's review as the short step at the end.
Why did it fail?
The most common failure is a mismatch between your Google payments profile and your D-U-N-S record. Google requires the legal name and address in your payments profile to match those in your Dun & Bradstreet profile exactly, and if they differ, you get an email and a banner in Play Console saying your organization name or address is no longer verified. A small discrepancy, like an abbreviation or an old address, is enough.
For personal accounts, failures usually trace to identity details that do not match or documents that cannot be read, such as a blurry government ID or a name that differs from your account. In both cases, the fix is alignment: make the information you submit match your official records precisely, rather than resubmitting the same mismatched data and hoping.
Does resubmitting reset it?
Resubmitting does not carry a penalty, but it only helps if you actually corrected the problem first. Simply sending the same details again will fail the same way, because the review is comparing against a record that has not changed. The productive move is to fix the mismatch, on whichever side is wrong, and then resubmit.
Keep in mind that some corrections take time to take effect. If you update your D-U-N-S details with Dun & Bradstreet, the change can take days or weeks to propagate before Google sees it, so re-verifying immediately may still fail. Correct the data, allow it to propagate, then resubmit and wait for the confirmation email.
Fix a name or address mismatch
When you hit a mismatch, work the two records into agreement rather than guessing. The checklist below gives a clear order to follow.
| Step | Action | Why |
|---|---|---|
| 1 | Note the exact wording of the banner or email | It names whether it is the name or address |
| 2 | Check your record at Dun & Bradstreet | The source of truth for organizations |
| 3 | Compare it to your Google payments profile | Legal name and address must match exactly |
| 4 | Update whichever side is wrong | Fix the D-U-N-S record or the payments profile |
| 5 | Allow time for the update to propagate | Days to weeks for Dun & Bradstreet changes |
| 6 | Re-verify and wait for the email | Google re-reviews the corrected details |
The core idea is that there are two sources of truth for an organization, your Google payments profile and your Dun & Bradstreet record, and verification passes only when they match. Decide which one is correct, fix the other to match it exactly, and give any Dun & Bradstreet update time to reach Google before you re-verify.
When to escalate or contact support
Escalate when the timeline clearly exceeds the norms and nothing on your side explains it: an organization review sitting well beyond a few days after your D-U-N-S details already match, or a personal review stuck far past a week. Use the Play Console Help and support flow to open a case, and include your account details and what you have already verified.
Set expectations realistically. For the D-U-N-S number itself, support cannot speed up Dun & Bradstreet, so contacting Google will not shorten that step. Google support is the right channel for its own review being stuck or for a mismatch you cannot resolve, not for the parts that are genuinely on Dun & Bradstreet's side.
What happens if you miss the deadline
Verification is not optional, and there is a deadline attached. If your organization name or address becomes unverified and you do not fix it by the date Google gives, your developer account can be restricted, which removes all of your apps from Google Play. That is a serious outcome, so a mismatch banner is not something to leave for later.
The way to avoid it is to treat any verification email or banner as time-sensitive and act while you have margin. Because Dun & Bradstreet updates can take weeks, starting the correction early is what keeps a fixable mismatch from turning into a removal. If you are close to a deadline, prioritize the fix over anything else on the account.
After verification: the next gate is a secure app
Once your identity is verified and you can publish, the work shifts from account admin to shipping, and the next gate is a policy-compliant, secure app. Identity verification has nothing to do with app security, but it is one of several checks between you and a live listing, and the later ones look at what your app actually does.
A scanner like PTKD.com analyzes your .apk and returns findings ordered by severity and mapped to OWASP MASVS, so once you are verified you can catch embedded secrets, insecure configurations, and risky permissions before you submit. To be clear about the boundary: PTKD has nothing to do with identity verification, D-U-N-S numbers, or Google's review of your details. It is simply the security step that comes after your account is cleared to publish.
What to take away
- Google's review of your submitted identity details usually takes a few days, up to about five, with an email when complete.
- For organizations, the long pole is the D-U-N-S number, which can take up to about 30 days from Dun & Bradstreet, so start early.
- Verification most often fails on a legal name or address that does not exactly match your D-U-N-S record.
- Resubmitting helps only after you fix the mismatch and let any Dun & Bradstreet update propagate.
- Fix a mismatch before the deadline to avoid account restriction, and after verification, scan your build with PTKD.com.
