The three major telecom operators regulate in-app billing and add SDK review

The "Draft Initiative for In-App Billing Standards" jointly released by China Mobile, China Unicom and China Telecom proposed billing standards for the in-App billing system for the first time. In addition to reiterating that in-app billing requires secondary confirmation, SDK review content has also been added.

On June 5, the game operating companies under China Mobile, China Telecom and China Unicom, together with 15 mobile game and channel companies including 360, Baidu, Xiaomi, Huawei, Ledo, Chukong and Zhongyouyou, announced the establishment of the "Sunshine Mobile Game Self-Discipline Alliance". At the establishment ceremony, the "Draft Initiative on In-Application Billing Specifications for APP" (hereinafter referred to as the "Specifications") was announced, which includes four parts: provision of billing capabilities by operators, use of billing capabilities, billing supervision, and user experience.

The "Specifications" reiterated that "the billing confirmation page must have a clear secondary confirmation process" and added content such as SDK review. "A web page or SDK that is secured by the SDK must be used to carry billing prompts and obtain user confirmation to ensure that the SDK code cannot be cracked and the SDK interface cannot be skipped." In response to other common speculative behaviors, the "Specifications" require that "before calling the billing capability, the item name, price, content and other information must be clearly stated through the item store or pop-up window," and "users cannot be misled into consumption by deliberately downplaying or reducing the font size. Other words must not be used instead of 'buy' in the button that triggers billing to induce users to consume." In terms of penalties for illegal applications, the "Specifications" require that the corresponding billing capabilities should be stopped and additional processing should be taken when necessary.

Wang Gang, rotating secretary-general of the Self-Discipline Alliance and general manager of China Mobile Migu Interactive Entertainment Co., Ltd., made three commitments on behalf of the alliance member companies: 1. Never set up misleading billing, attach importance to user experience, and advocate healthy consumption; 2. Never undermine billing security and advocate safe consumption; 3. Never tolerate any malicious deductions and jointly combat illegal and criminal activities.

The Alliance has clearly put forward five self-regulatory measures:

1. Alliance members will issue a self-discipline manual based on in-app billing regulations to set a new standard for mobile games;
2. We are committed to promoting the establishment of a multi-dimensional optimization mechanism in the market, and will focus on user experience and advocate healthy consumption as the standard for channel promotion of games;
3. Establish a reporting mechanism for malicious software deductions and other bad behaviors, as well as a rights protection mechanism to pursue legal responsibilities in accordance with the law;
4. Establish a special technical supervision team to timely analyze market trends, establish a complete technical supervision and monitoring system, actively discover bad behavior in the market, and provide technical support to improve the safety of the game;
5. Promote the transformation of telephone bill payment in the market from pure SMS payment to online payment in a timely manner.

This is the first time that the three major operators have systematically proposed billing standards for APP applications. Prior to this, operators had each proposed billing standards, but they were relatively scattered. This time, clear regulations have been made for core links in the industry, such as operators, developers and channel providers. However, no matter how detailed the regulations are, the key to effectiveness still lies in execution. The following are the business operation rules and regulations:

1. Operator billing capability provision specifications

1. The billing capability provided to the application must use a web page secured by the SDK or the SDK to carry the billing prompt and obtain user confirmation. The billing interface shall not be provided directly in any way.
2. The SDK must undergo high-level security reinforcement at the technical level to ensure that the SDK code is obfuscated, encrypted, protected by runtime memory, and protected by call security. The SDK code cannot be cracked and the SDK interface cannot be skipped.
3. The billing confirmation page must have a clear secondary confirmation process. The secondary confirmation page uses the operator's unified standard interface, and the billing interface displays prompt information such as "prop name, rate, customer service phone number", and must also include clear and identifiable confirmation and cancellation paths.

II. Application Usage Billing Capability Specifications

1. Use the billing capabilities you apply for strictly in accordance with the user manual provided by the operator;
2. Any technical means may not be used to bypass the operator's billing process;
3. During the use of the application, the billing page guiding the user shall not be popped up automatically and continuously.

3. Application Experience Specifications

1. During the billing interaction process, the application must remind users of their consumption through confirmation, including: before calling the billing capability, the application must clearly indicate the item name, price, content, etc. through the item store or pop-up window;
2. When users use billing services, the font, color and size of the application fee prompt must be eye-catching. It is not allowed to mislead users by deliberately diluting or reducing the font size. The button that triggers billing must not use other words instead of "buy" to induce users to make purchases;
3. After the user uses the billing item, a SMS message notifying the user of successful deduction must be sent. The reminder information includes explicit fee information such as "application name, purchased service name, customer service phone number, deduction amount", etc. This information is sent by the operator to the user.

IV. Regulatory Specifications for the Use of Billing Capabilities

1. In addition to providing billing capabilities in accordance with the specifications, the operator entity that provides billing capabilities shall supervise whether the applications using the billing capabilities provided by the entity comply with the specifications;
2. For applications that are found to violate relevant regulations during supervision, the corresponding billing capabilities should be stopped and additional processing should be carried out if necessary.

V. Customer Service Standards

1. Retention of user consumption records: The operator will properly preserve the fee list of the user's use of information services and the customized relationship and behavior log generated when the user applies for customized monthly and subscription mobile information services until the user cancels the service, and then retain it for at least six months.
2. User detailed bill inquiry function: Operators provide customer service telephone, website, WeChat public account and other methods to provide users with information service charges inquiry function, so that users can check their payment amount and specific order content. At the same time, users will be clearly informed of the total amount of mobile information service charges used in the previous month on the monthly bill.