Trader ID Verification - Name Mismatch Between ID and Supporting Documents

[Daniel Kloss]

Hi,

I'm trying to complete trader identity verification for my Chrome Web Store developer account but have hit a problem.

My UK driver's licence shows my full legal name including my middle name. However, UK bank statements typically only show a first initial for middle names, or omit them entirely. I submitted my verification with these documents and it was rejected - I assume due to this name mismatch.

I'm now hesitant to use another verification attempt without guidance, as I don't have any documents where the name formatting matches exactly.

Could you advise:

1. Is the name format discrepancy definitely the issue?
2. Are there alternative supporting documents that would be accepted for UK residents?
3. Is there any way to flag this to the verification team before resubmitting?

I haven't been able to submit any extensions yet as I can't get past this verification step.

Thanks for any guidance.

Regards,

Daniel

[Loizou Christakis]

It is highly likely that the middle name discrepancy is the root cause. Google’s verification systems (shared across the Chrome Web Store and Play Store) use automated OCR (Optical Character Recognition) that is notorious for rejecting documents if the name on the Payment Profile does not match the ID and Proof of Address character-for-character.

Here is a breakdown of how to handle this for a UK-based account.

1. Is the name format discrepancy the issue?

Almost certainly. Google requires an "exact match." If your UK Driving Licence says "John Michael Smith" and your bank statement says "John M Smith" or "John Smith," the system often flags this as a mismatch.  

2. Alternative Supporting Documents for UK Residents

Since UK banks are notoriously consistent about shortening middle names, your best bet is to find a document that naturally includes your full name or to use a document where the name is less likely to be truncated.

• Council Tax Bill: These often include your full legal name and are highly trusted by Google’s verification team.

• Utility Bill (Water, Gas, Electricity): Check your latest bill; some providers allow you to update your "Account Name" online to include your full middle name. If you can edit it and then download a new PDF, this is a strong option.

• HMRC Correspondence: A P60, coding notice, or official letter from HMRC will almost always have your full legal name and is an acceptable "Government-issued document."

• Insurance Statements: Home or car insurance documents often show the full name of the policyholder.

3. How to fix this before resubmitting

Do not resubmit the same documents. Instead, follow this workflow:

1. Update your Payments Profile first: Go to your Google Payments Settings and ensure the "Legal Name" there matches your ID (the driving licence) exactly, middle name included.

2. Source a "Full Name" Address Document: If your bank statement only shows an initial, do not use it. Switch to a Council Tax bill or a Utility bill where you have verified your full name is present.

3. The "Trader" Toggle Trick: If you are stuck in a loop, some developers have found success by temporarily toggling their status to "Non-Trader," saving, and then toggling back to "Trader" to "reset" the verification task (though use this with caution as it can trigger new timelines).  

4. Flagging it to the Team

You cannot "flag" a specific issue during the automated upload, but you can seek manual intervention if you are rejected again:

• One-Stop Support: Use the Chrome Web Store One-Stop Support form.

• Select "My Developer Account" > "I have an issue completing trader verification."

• In the description, explicitly state: "My UK Driving Licence contains my full middle name, but UK banking standards truncate this to an initial. I have provided a [Council Tax/HMRC] document to bridge this gap."

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/cd80a22a-04fb-4f29-a510-242ba8e5c66an%40chromium.org.