Hi all,
Back in February, we
announced new trader verification requirements which applied to new accounts, and that these would be required for existing traders in the future. These changes are now rolling out to existing traders as part of our work to comply with EU regulations.
If your account is marked as a trader, you’ll be prompted to start verification when you next sign in to the Developer Dashboard. This includes verifying and displaying publicly a phone number and organization DUNS number if applicable alongside the physical address and contact email shown today.
Currently, this verification is not mandatory, and you can leave the process to continue in the Developer Dashboard. Starting in September, we will require developers to have started the process and submitted their details for verification, and you will not be able to access the dashboard until this is complete.
We’ve seen some feedback in the mailing list already. In particular:
- We’re aware that some organizations use phone numbers where SMS verification is not available. We don’t currently have any plans to provide alternative options, but we hear the feedback.
- Some developers have mentioned not having a personal ID to verify on behalf of their business. This means you are in the individual verification flow based on the payment profile you selected. In this case, you can mark your account as a non-trader, and then opt-in as a trader again. This will restart the process, and by using an organization payment profile rather than an individual one, you will be able to see alternative verification options requiring a DUNS number or company documents instead.
Thanks for your patience and understanding with these changes. We weren’t expecting quite as much feedback on this so early, so we’re actively discussing the feedback and will make changes where we can to clarify the flow. We have an obligation to verify traders but want to make this as straightforward as possible and the team has been working hard on this for several months to avoid asking for more information than is necessary.
Thanks,
Oliver on behalf of Chrome Extensions DevRel