The relationship between the payment information of Google Play merchants and the payment information of opening a Google Play account. Which Google developers can change their names after real-name certify?

This is GGZC. In the previous related article “How to check whether the payment information of Google developers has been verified by real name (identity verification), can the name be changed after the real name of Google Play?” We mentioned whether the name can be changed after Google developer account authentication (real-name authentication), and how to check that the name of your payment profile is locked and cannot be changed (read-only); today we will conduct a more comprehensive analysis on the issue of payment profile name lock .

In the Google payment profile, click the [Name] column of [Name and Address], if it is gray (read-only), it means that the payment profile has been authenticated and the name cannot be modified; as shown below

At this time, if there is only [Payment Information] information on the payment information page and no [Public Merchant Information]; it means that the developer account has not yet created merchant payment information, as shown below

[Payment information] is still the information when registering an account (the name of the information at this stage cannot be modified). As shown below

On the payment information page, there are [Payment Information] and [Public Merchant Information] at the same time, indicating that this type of account is an in-app subscription account, usually a developer of a paid application; when creating merchant payment information (payment information) , if you continue to use the payment information at the time of registration, the name option of the payment information will still not be able to be modified (read-only status), and the inability to modify the name of the payment information will have some disadvantages later.

When creating merchant payment information (payment profile), if you create another new payment profile (or new country information), the name of the payment profile can be modified in this case. Because the merchant payment information created later will overwrite the previously bound registration payment information, this behavior also has drawbacks. As shown below

What are the disadvantages of the payment information of the merchant being the same as the payment information of the registered developer account (the name cannot be modified)?

What are the disadvantages of using different information (which is inconsistent with the payment information when registering) when creating a merchant payment profile (payment information)?

Here are some other services or information that may be of interest to you:

A guide to Google Developer registration, security risks, tax collection and verification issues

Subscription membership activation and related conditions

About GGZC , If you have any ideas, you can post them on:GG Developer Community