[FAQ] common reasons and solutions for the failure of in app payment services to pull up the payment page

Huawei In app payment services （In-App Purchases） Provide users with a good in app payment experience through a simple access process , However, in the actual access process , Some developers report that the payment page cannot be pulled up normally during the test , The following will analyze the problems in detail 5 Kinds of situations , And give the solution , Hope to provide reference for developers who encounter similar problems .

situation 1：AGC On the console API Payment in management API Already opened , The created product is also effective , But check the log and find an error 60002

Cause analysis ： Yes IAP The payment public key is required for the verification of the request result of , Conduct SHA256WithRSA Signature verification , This public key developer is not configured .

resolvent ： Please carefully check whether the following three points are set ：

（1）API Payment in management API Already opened （ Be careful ： The user is opening IAP service , It takes about half an hour to take effect ） Please refer to Official documents

（2） Make sure the public key switch is activated on , And the public key is used correctly

（3） stay AGC backstage PMS（ Commodity management system ） Corresponding types of goods are configured on , And activation succeeded

situation 2： Developers enter the membership center to edit the subscription page , Display exception , Report errors 60051

see Official document , Error code 60051 It means purchased goods or subscription goods , Cannot buy again ;

Cause analysis ：

When we reproduce the problem, we find , After the subscription is completed, there is a refresh action when returning to the Member Center , Clicking on the subscription before refreshing will cause an exception , Clicking after refreshing is normal . This is because if there is no refresh or the refresh is not timely , There will be the last cached data . After clicking on a subscription product , Click to subscribe to another product now , Will put the first subscription products id Into the , But it's time to id It's not the latest subscription product id, Thus causing data mismatch , It eventually leads to an error report , Unable to display the edit page .

resolvent ：

It is suggested that developers optimize the timing of page effect refresh , Avoid renewing without refreshing .

situation 3： An error is reported when using Huawei mobile phones for payment debugging 60003, but PMS Products in the system ID No problem found in the configuration .

Cause analysis ： First of all, report an error 60003 Usually in PMS There is a problem with the commodity information configuration in the system , You can go to AGC Website backstage , In my app -> operating -> Commodity management -> List of goods , Check whether the corresponding product exists or whether the required information is correct and complete （ E.g. product name , goods ID, Price , Commodity type , Whether to activate ）.

In addition, you can check the goods ID Whether it is correctly filled in the client code , Whether or not AGC Backstage goods ID bring into correspondence with , Please focus on checking whether there is a problem with the fields passed in the client code .

Another thing to note is whether the service location of the Huawei account logged in on the device is IAP Within the scope of coverage . You can call Task isEnvReady() The interface determines the service country of the current device login account / Whether the region is Huawei IAP Countries where payment services support settlement / Regional .

Solution ：

after CP The investigation found that it was the product imported by the client-side code ID and AGC Products configured in the background ID atypism , The problem has been solved after modification .

situation 4： Call the payment pull up cashier interface , Successfully pull up the successful payment page for the first time , Then click Cancel to return , Why can't I pull up the payment page the second time I continue to call this interface ？

Cause analysis ： After purchasing consumable goods , The consumption of goods must be completed first , Then you can buy again , Otherwise, an error will be reported 60051 Wait for the error code .

resolvent ： Make up orders for consumable goods

Developers need to trigger the replenishment mechanism in the following four scenarios ：

· When app starts

· Purchase request return -1（OrderStatusCode.ORDER_STATE_FAILED） when

· Purchase request return 60051（OrderStatusCode.ORDER_PRODUCT_OWNED） when

· Purchase request return 1（OrderStatusCode.ORDER_STATE_DEFAULT_CODE） when

If IAP The refund callback address configured in the background is wrong , Need to reconfigure . For details, please refer to file

In addition to the problem of being unable to pull up the payment page , How to confirm whether to enter the sandbox environment is also a common problem .

situation 5： Test with sandbox account , There is no prompt pop-up box at the end of the sandbox environment , How to confirm whether to enter the sandbox environment ？

Cause analysis ： First, enter the sandbox test environment , Under normal circumstances, the following pop-up box will be prompted

But in meeting the sandbox environment 2 After three necessary conditions , Still unable to prompt the dialog , Does it mean that you have not entered the sandbox test ？

The following is what the developer passed isSandboxActivated Relevant data printed out by the interface

From the printed logs ： Meet the sandbox environment 2 Necessary conditions .

1. The currently logged in Huawei account belongs to the sandbox account

2. VersionCode Greater than the online version of the application market （ The APK The application market has not been released yet , So the version number returned by the application market is 0）

Obviously, from the results, in theory, it should enter the sandbox testing environment . Is there any other way to confirm ？

resolvent ： Whether you have successfully entered the sandbox environment , You can check through the following methods

a) View the returned purchase data , Refer to the below ：

If Huawei order number payOrderId With SandBox start , Then it seems that this order belongs to the order generated by sandbox test .

b） View the payment report

You can see Payment statement , If there is no such order in the payment report , Explain that the order comes from the sandbox test .（ notes ： Payment report data is not updated in real time , If the order purchased on the same day , To judge accuracy , You can refresh the report for verification the next day ）

c） eliminate HMS Core cache You can try to clear HMSCore cache , The end side pop-up frame is judged according to the corresponding field identification , This value may not be refreshed in time due to caching . By setting –> Applications and services -> Application management ->HMS Core Do cache cleanup .

Learn more >>

visit Official website of Huawei developer Alliance
obtain Development guidance document
Huawei mobile service open source warehouse address ：GitHub、Gitee

Pay attention to our , The first time to understand HMS Core Latest technical information ~