Google Play Developer Verification and DUNS Numbers for TWAs

Publishing a Progressive Web App on the Google Play Store using a Trusted Web Activity requires setting up a developer profile. To maintain a safe ecosystem, Google enforces developer identity verification. For companies, software-as-a-service providers, and agencies, this verification process requires a Data Universal Numbering System number. Navigating this administrative step correctly is critical to avoid verification delays or application rejection.

Why Developer Verification Matters for Trusted Web Activities

A Trusted Web Activity establishes a secure, cryptographically verified link between your web domain and your native Android application package. This connection is established using Digital Asset Links. Because a TWA is an extension of your website, Google Play policy demands absolute clarity regarding the legal owner of both the domain and the developer account.

If you register a developer account under a personal name but try to publish a TWA that points to a corporate web application, you risk running into verification flags or policy rejections. Google requires that the developer profile matches the legal entity owning the digital assets. Operating under a verified organization profile ensures that your application complies with commercial publishing standards and avoids the strict 20-tester testing phase mandated for new personal developer accounts.

Understanding the DUNS Number Requirement

A DUNS number is a unique nine-digit identifier managed by Dun and Bradstreet. It acts as a global standard for business identification. Google uses the Dun and Bradstreet database to cross-reference your business name, physical address, and legal status. You cannot register a corporate Google Play Console account without a valid DUNS number.

Obtaining a DUNS number is free, but the registration details must match your official corporate registration documents. When you submit your organization details to Google, automated systems check the Dun and Bradstreet database. If there is a single mismatch in the address formatting, the legal business spelling, or the entity status, the verification process will fail.

Personal vs Organization Accounts for TWA Publishing

Choosing between a personal and an organizational developer account affects both the registration requirements and the subsequent publishing lifecycle. Developers converting web applications often choose organization accounts to bypass the testing constraints imposed on personal accounts created after November 2023.

Step-by-Step Verification Process for TWA Publishers

To ensure a smooth transition from your web application to the Google Play Store, you must follow a systematic approach to developer verification. Failing to prepare the correct documentation beforehand can stall your publishing timeline by several weeks.

1. Secure and Verify Your DUNS Profile

Before initiating the Google Play registration, search the Dun and Bradstreet database to verify if your company already has a DUNS number. If your company is registered, review the exact spelling of your business name and address. If you do not have one, apply through their portal. The free registration process typically takes between five to thirty days. Ensure your physical address matches your local corporate registry perfectly.

2. Match Domain WHOIS Data and DNS Details

Google verifies your authority to publish apps for your target web domain. It is highly recommended that the administrative contact email on your domain name registration matches the corporate domain used for your Google Play Console developer account. For example, if your PWA is hosted at app.example.com, registering your developer account with an email address like developer@example.com dramatically simplifies the verification pipeline.

3. Pay the Google Play Registration Fee

Google charges a one-off developer registration fee of 25 USD. This fee must be paid using a credit card associated with the name of the developer registering the account or the legal representative of the organization. Using mismatched payment details can trigger immediate account suspensions for suspicious activity.

4. Submit Verification Documents

During the verification phase, Google will request official documentation. For organizations, this includes utility bills in the company name, tax registration certificates, or official articles of incorporation. The address on these documents must match the address listed in both your DUNS profile and your Google Play Console settings down to the apartment or suite number.

Common Verification Pitfalls for TWA Developers

TWA publishers often run into unique verification hurdles due to the hybrid nature of web-to-app deployment. The most common pitfall is registering a personal developer account to publish a commercial software-as-a-service web application. If Google identifies commercial transactions inside a TWA published by a personal account, the account may be flagged for operating under an incorrect profile type.

Another frequent issue is address mismatching. If your business moved recently and your local tax registry was updated but your Dun and Bradstreet listing still reflects your old address, the Google Play Console system will reject the submission. Always update your DUNS information before starting the Google Play verification process.

Maintaining Your Verified Status

Developer verification is not a one-time event. Google periodically re-verifies developer accounts to maintain store integrity. Ensure that your corporate email addresses remain active, your domain registrations do not lapse, and your Digital Asset Links file remains accessible at your PWA web origin. Any interruption in domain ownership or accessibility can prompt Google to mark your TWA as non-compliant, leading to temporary removal from search results inside the store.