Google Developer needs to submit a verified payment profile in Google Payments / Google Payment needs to verify and explain recent account activity

From Gogplay (gogplay.com); In my last article, I mentioned the drawbacks and risks of using virtual bank accounts for Google developers to pay and receive money. Today, I will analyze the frequent suspension of payment by Google play merchants in the past two months. Information (requires verification of identification documents, binding of all bank accounts/cards (including bank card photos, monthly statements), and verification instructions for some abnormal account activity.

After a google play developer account is suspended, Google Payments will send us an email notification on how to lift the suspension. The original text of the email is as follows:
We’ve noticed suspicious activity on your Google Account.
Please verify that you are an authorized user within 3 days to avoid service interruption or suspension of your Google payments profile.
You need to upload the following materials:
• Picture or scan of payment method or claim to confirm ownership
• Scanned copy of government-issued photo ID (same name as payer)
To learn more, visit the Google Payments verification help page.

At present, there are two different situations for the Google developer merchant account with this problem. One is that you only need to submit an ID document and explain the abnormal activity of the account (as shown in the figure below)

Regarding this verification, it explains the abnormal activity of the Google account, the relationship with the buyer, why the buyer paid me, etc. This verification description is quite cumbersome to handle (currently, the probability of passing the verification is very low).

Generally, this verification can only be lifted if qualified documentation is submitted with a 100% consistent explanation. Of course, most of the time, the “truthful” Google will ruthlessly refuse to verify. At this point, you need to try again. Reasons for refusal were roughly (reasons provided were unclear; reasons provided did not specify suspicious activity; reasons provided did not specify source of funds.)

The other is that two different verifications are required (in addition to the verification mentioned above), and some additional information needs to be verified and submitted on different verification pages;
The following information needs to be uploaded:

1. A photo of a valid government-issued ID card with a photo, 2. Upload the bank account card and statement (including the payment method and the bank account of the payment method) bound to the Google pay account;
   If our account is only bound to one receiving bank account, then we only need to complete the identity verification and the verification of the receiving bank statement.
   Here is a special note: if your account is bound with a payment card number (pay the developer registration fee of $25, or the card number is used for other purposes) and is a bound virtual payment card, then there is a high probability of no solution this time; Sign up for multiple different developer accounts, and most people will sign up for developer accounts in other countries. A virtual card will also be used to pay the $25 registration fee (third-party payment). At this time, Google needs to verify the statement of the payment card. If we don’t do our best, we can’t solve it.
   The relevant verification page, as shown below.

[Question about the payment of this article] Do all Google play developer accounts have the above problems?
First of all, this question is only for developers who do in-app purchases. If it is only for users who publish applications (for free applications), it will not affect them;
Most of the developers who have Google Payments verification problems have multiple accounts, the app products are similar, and more than one account has this problem (the first time it occurs, other accounts will also appear later). If it can’t be solved, even if The account balance has $1 million, and it’s all dead.
When this verification occurs for developers who do in-app purchases, is there any violation or association of the developer account? How to avoid this problem and what are the reasons for this problem? Below we will enable paid reading to answer it for you. (Free for subscription members)
How many gp developers have this problem, and is this problem widespread?
This data can be shared publicly, and such problems have appeared one after another since August 2022.
At present, this case, through Google query, is only published exclusively by us. According to my judgment, it is not a large-scale situation.
Less than 20% of users experience this type of issue, and more than one account with multiple accounts experiences this issue. Some in-app purchase users have never encountered this problem. Below we will explain the specific reasons for this problem in a paid way.
Hidden content below (not an explanation account activity explanation scheme to address this verification issue), updated on November 1, 2022

Why is the same note, submitted at different times, rejected for different reasons? Will this give us some misleading signal? (Hidden content for reference only)