Google’s developer risk control measures may be stricter after 2023

This is GGZC. In the past year, the problem of blocked Google Play developer accounts has not occurred on a large scale; the reason is not that Google has become benevolent, nor is it that many developers have improved their methods.

Because the newly registered problematic account is difficult to get on the right track (not detailed here);

In terms of risk control before 2021, Google will have a large-scale “massacre” almost every year, and the centralized banning of accounts has caused many developers to suffer heavy losses. Even some developer teams went bankrupt and quit Google.

Before the Google play developer real-name policy (identity verification), 95% of developer registration accounts would fill in random or false information.

After the start of the real-name policy in 2021, most developers still use false information for verification; some developers find it troublesome to register a Google Play account (or can’t figure out the problem of registering a Google Play account), and will go to the market to buy some registered finished products .

From 2022 onwards, I think many people have experienced the risk control of Google Play. They often verify payment information or stop payment information, and some problems cannot be solved. Failure to solve these problems means that all efforts are wasted. I believe that the future risk control strategy will be more stringent, so once something goes wrong, some accounts will be difficult to recover.

All of the above are great risks for all Google developers, equal to time bombs.

I believe that many google play developers (especially in-app purchase merchants) have experienced thousands of dollars, tens of thousands of dollars, or even hundreds of thousands of dollars in balances that cannot be obtained (google play suspends payment, suspends sales, does not pay, etc. ).

If something goes wrong, the smallest loss is almost ten thousand RMB. Therefore, although the cost of some risky behaviors mentioned above is very low, the probability of risk occurrence is indeed high.

Because newly registered problematic accounts are difficult to get on the right track, some developers try to acquire some stable old accounts (stable accounts that are idle by other developers). Because they think that although the acquisition cost of a stable old account is high, it is safe to use and has no risk.

Why are some Google Play developer accounts prone to problems, while others are stable? Is it a problem of true and false information, or other problems in the registration process?

How stable is the purchased Google Play account? Is the google play account without authentication stable or the google play account that has completed the authentication is stable? (The following uses the paid reading plan to analyze it for you)

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