Why Your D-U-N-S Number Must Exactly Match to Verify Your Google Play Developer Account
If you're setting up a Google Play developer account for an organization, there's a single detail that causes more verification failures than anything else: your D-U-N-S number and your Google payments profile need to say exactly the same thing.
What a D-U-N-S number is
A D-U-N-S number is a unique nine-digit business identifier issued by Dun & Bradstreet, a company that maintains commercial records on businesses worldwide. Google Play requires organization developer accounts to provide one as part of verifying that your business is what it claims to be — it's the link between your Play Console account and an independently verified business record.
This only applies if your developer account represents an organization. A solo developer publishing under their own name goes through a different, D-U-N-S-free identity check.
The rule that trips up most developers
Here's the part that causes the most failures: the legal name and address associated with your D-U-N-S number must be exactly the same as the legal name and address in your Google payments profile. Not "close enough" — exactly the same.
In practice, this catches developers on small formatting differences they wouldn't think twice about: "ABC Tech" versus "ABC Tech Pvt. Ltd.", a missing suite or floor number, an abbreviated street name, or a locality spelled differently between the two records. Google's system compares these fields directly, and it doesn't infer that two slightly different strings refer to the same business.
What happens if it doesn't match
If Google detects an inconsistency between your D-U-N-S record and your payments profile, you'll get a notification — an email and a banner in Play Console — and a 28-day window to fix it. If the mismatch isn't resolved within that window, your developer account and every app tied to it are removed from Google Play.
It's worth being clear about what "removed" means here: this isn't a warning on one listing, it's the entire account. If you publish more than one app under the same organization, all of them go down together.
A mismatched suite number is a small clerical detail. Losing every app on the account isn't. Treat this check as seriously as you'd treat any other policy review.
How to avoid the problem
A few practical steps, in the order they're useful:
Get your D-U-N-S number early. If your business doesn't already have one, obtaining it from Dun & Bradstreet can take up to roughly 30 days. Request it well before you plan to start Play Console verification, not the day you sit down to do it.
Compare the two records character by character before you submit. Pull up your D-U-N-S business information and your Google payments profile side by side. Check the legal entity suffix ("Ltd.", "Pvt. Ltd.", "LLC"), suite/floor numbers, abbreviations, and spelling — these are the details that most often differ even when both records are technically correct.
If they don't match, fix the D-U-N-S side first. You can request an update to your business information directly with Dun & Bradstreet at service.dnb.com. If the information Google already has is what's actually correct, update your D-U-N-S record to match it, rather than the other way around.
Who actually needs this
This entire process applies only to organization developer accounts — not personal accounts. If you're publishing as an individual rather than as a registered business, you won't encounter D-U-N-S verification at all; your identity check follows a separate path.
Check your listing before Google does
SubmitSafe reviews your title, descriptions, metadata and screenshots for policy risks — free, in about 60 seconds. Account verification issues like D-U-N-S mismatches happen at a different stage and are resolved directly with Google and Dun & Bradstreet, not through SubmitSafe.
Check for freeWhat is a D-U-N-S number?
A unique nine-digit identifier assigned to a business by Dun & Bradstreet. Google Play requires organization developer accounts to provide one as part of identity verification.
What happens if my D-U-N-S details don't match my Google payments profile?
Google will flag the inconsistency and give you 28 days to fix it. If it isn't resolved in that window, your developer account and all your apps will be removed from Google Play.
Do personal Google Play developer accounts need a D-U-N-S number?
No. The D-U-N-S requirement applies only to organization accounts. Personal accounts go through a different identity verification process.
How long does it take to get a D-U-N-S number?
Obtaining one from Dun & Bradstreet can take up to roughly 30 days if your business doesn't already have one, so request it well before you plan to verify your Play Console account.