Why Google Added This Requirement
Google introduced expanded verification for Play Console developer accounts as part of a broader push to boost trust and transparency on the Play Store. When you create a new Organization developer account, Google now asks for a D-U-N-S number to confirm your business is legitimate before you're allowed to publish apps.
This isn't an isolated checkbox — it sits alongside a whole cluster of identity checks Google has been rolling out over the past couple of years: verified phone numbers, verified emails, and, for organizations specifically, a public developer profile that shows verified contact details to anyone browsing your app listing. The stated goal is to cut down on fake developer accounts, copycat apps, and scam listings that have historically been hard to trace back to a real, accountable entity. A D-U-N-S number, tied to Dun & Bradstreet's global business database, gives Google a third-party-verified anchor for "who is actually behind this app."
What a D-U-N-S Number Actually Is
A D-U-N-S (Data Universal Numbering System) number is a unique nine-digit identifier issued by Dun & Bradstreet to a specific business entity at a specific address. It's been around since long before app stores existed — originally built for credit reporting and supply-chain verification — and it's now been repurposed by Apple, Amazon, Google, and various government and B2B systems as a standardized way to prove "this business is real and this is where it's registered."
Who Issues It
Only Dun & Bradstreet issues D-U-N-S numbers. No third party, agency, or platform generates its own version — every D-U-N-S number you see referenced by Google, Apple, or anyone else traces back to the same D&B database.
Is It Free
Yes. Requesting a D-U-N-S number directly through Dun & Bradstreet's official channel costs nothing. If an agency is charging you a fee purely for "getting you a DUNS number," that fee is for their time filling out the form on your behalf — not for the number itself, which D&B never charges for.
Who Needs One — Personal vs Organization
Play Console offers two account types, and the DUNS requirement only touches one of them. Here's the practical difference:
| Account Type | Who It's For | DUNS Required? |
|---|---|---|
| Personal | An individual publishing apps under their own name | No |
| Organization | A registered company, studio, or legal entity publishing under a business name | Yes |
If you're a solo developer publishing a hobby or side-project app under your own name, you can skip this entire process. The requirement only kicks in the moment you register — or try to register — as an Organization, because that's when Google needs proof that the business name you've entered actually corresponds to a real, registered company.
What Google Verifies Against Your DUNS Record
- Organization name and address — must match what Dun & Bradstreet has on file for your D-U-N-S number.
- Contact email and phone — verified via one-time password, and kept current for the life of the account.
- Public developer profile — organizations must show a verified phone number and email publicly on their Play Store listing.
If Google can't verify these details, your developer presence and apps can be removed from Google Play until you re-verify — so it's worth getting this right the first time rather than rushing it. A mismatch as small as a suite number missing from your address, or a slightly different legal name than what's registered with D&B, is enough to stall verification.
How to Set It Up
- Search before you apply. Many organizations already have a D-U-N-S number without realizing it, especially if the business has ever dealt with government contracts, credit checks, or international trade. Check the official Dun & Bradstreet lookup before requesting a new one — requesting a duplicate for an entity that already has one just creates confusion later.
- Request one if needed. If you're not listed, you can request a free D-U-N-S number directly from Dun & Bradstreet. Google's own documentation notes this can take up to 30 days, so plan ahead of any launch deadline — don't leave this until the week before you intend to submit your app for review.
- Create your organization developer account. Enter the D-U-N-S number and confirm the organization details Google retrieves from your D&B profile. Double-check that the retrieved name and address exactly match your business registration documents before proceeding.
- Complete identity verification. Verify your contact email and phone via one-time password, and submit any business documents Google requests. Keep scanned copies of incorporation certificates and address proof handy — Google occasionally asks for supporting documentation during review.
Common Mistakes That Delay Approval
Most rejections and delays in this process come down to a handful of avoidable errors:
- Name mismatches. Entering "ABC Technologies Pvt Ltd" on Play Console when D&B has "ABC Technologies Private Limited" on file. Even minor formatting differences can trigger manual review.
- Stale D&B records. If your business moved offices or changed its legal name and never updated Dun & Bradstreet, Google will verify against the outdated record — not your current one.
- Using a personal account's D-U-N-S expectation. Some developers assume they need a DUNS number even for a Personal account and get stuck on a step that doesn't actually apply to them.
- Skipping the D&B lookup step. Requesting a brand-new D-U-N-S number when one already exists for the entity creates duplicate records that D&B and Google both need to reconcile manually.
- Ignoring the 30-day buffer. Starting the DUNS request the same week as a planned app launch is the single most common cause of missed release dates in this process.
Timeline and Cost Expectations
Getting the D-U-N-S number itself is free and, per Google's guidance, can take up to 30 days if you don't already have one. Beyond that, Play Console's own identity verification — email, phone, and document review — typically adds a few more days once your D-U-N-S number is in hand and your details match cleanly. Organizations that already have an existing D-U-N-S number on file with D&B usually move through Google's verification much faster, since the lookup-and-match step is nearly instant.
Large Organizations: Watch for Multiple DUNS Numbers
If you're part of a larger group, you may have several D-U-N-S numbers across different entities within the organization — a parent company, subsidiaries, and regional branches can each carry their own separate number. Make sure the specific number you use matches the entity details you actually want associated with your developer account. Using the wrong one is a common source of mismatched verification, and it's not always obvious which subsidiary's D-U-N-S number is "correct" without checking internally first.
What If Dun & Bradstreet Doesn't Cover Your Region?
If you're in a region D&B doesn't support, Google's support team offers an alternative verification path — but only for organizations that are genuinely unable to obtain a D-U-N-S number, and incomplete requests won't be considered. Be prepared to explain clearly why a D-U-N-S number isn't obtainable and to supply whatever alternative business documentation Google's support team asks for.
How This Compares to Apple and Amazon
Google isn't the only platform that leans on Dun & Bradstreet for verification. Apple has required a D-U-N-S number for its Organization-type Apple Developer Program enrollments for years, and the underlying logic is nearly identical — same database, same nine-digit identifier, same name-and-address matching requirement. Amazon's approach differs by service; some Amazon business verifications ask for it, others don't. The upside of getting your D-U-N-S number sorted once is that the same number carries over to every platform that recognizes it, so this isn't a Google-only chore if you're planning to publish across multiple app stores or business platforms under the same entity.