Error Code | Error Description | Solution |
100 | Initialization error | Please check if your AppKey is correct |
101 | Initialization parameter error | Incomplete parameters when calling the initialization interface |
120 | No app information found | Please check if your AppKey is correct |
Error Code | Error Description | Solution |
600 | Login error | |
610 | Generate account error | |
611 | Quick login error/td> | |
620 | Binding error | |
621 | Binding phone error | |
622 | Mobile number is required | |
623 | Wrong format of phone number | |
624 | Verification code required | |
625 | Verification code error | |
626 | Verification code expired | |
627 | Please send a verification code first | |
631 | Bind email error | |
632 | Email required | |
633 | Incorrect email format | |
650 | Third:WFun login error | |
651 | Third:WFun login error the parameters are incorrect. | |
652 | Third:WFun login error, illegal source | |
653 | Third:WFun login error, signature error |
Error Code | Error Description | Solution |
200 | User has logged in | Normal status |
201 | User not logged in | This is the normal state, indicating that the currently authenticated user is not logged in to the SDK. If the player is logged in and returns 201 here, please check if the encrypted value is correct (refer to 302 error below). |
301 | verify_data decryption error | Please check: 1、Is the MG public key correct? 2、Is the process using MG encryption correct? |
302 | Token、userid or appkey parameters incomplete | Please check if the value to be encrypted is correct. The correct format is: token=AAAAAAAA&userid=BBBBBBB&appkey=CCCCCC |
303 | Developer did not upload public key | Please enter the developer background and upload the RSA public key in the application management. |
304 | Signature verification error, check whether the upload public key format is correct | Please check if uploading the RSA public key is correct in the application management. |
305 | The parameter value is null | Please check whether parameter verify_data、verify_sign is correct |
306 | Passing parameter error | Check whether the names of the parameters verify_data and verify_sign are correct. |
Error Code | Error Description | Solution |
350 | Store Error | |
351 | Store Parameter Error | |
352 | No store information found | |
360 | Store callback settings error | |
361 | No app information found | Please check whether the AppKey is correct. |
362 | Game public key is null | Please find your application in the">MG Developer Platform -> Application Management -> Application Listand check whether the application public key in the application information is filled in. |
363 | CallbackId is invalid | Please check if the value of CallbackID passed when you call the MG SDK payment interface is correct.You can check it in MG Developer Platform -> Store Information -> Application Callback Address. |
370 | Create goods failed | |
371 | Goods payment error | |
372 | No goods information found | Please check whether your GoodsKey exists in MG Developer Platform -> Store Information -> Product Management |
373 | Invalid session or no application information found | The login time is too long. whether you encounter such problems, please log out and log back in. |
374 | App, goods, callback address does not match |
Please check that you have passed two parameters GoodsKey when calling the MG SDK payment interface. The value of CallbackID is in the current application (the current application is based on the AppKey when you call the MG SDK initialization in the game. This AppKey can be checked in MG developer platform. -> Application Management -> found in the application list
|
375 | The app needs to call back to the developer, not uploading the RSA public key | Pleas find your app in MG Developer Platform -> Application Management -> Application List,and check whether the application public key in the application information is filled in. |
380 | Saving product information failed | Generally the goods name is too long, and the goods name is composed of "app name + goods name + goods quantity", which together does not exceed 50 characters. |
Error Code | Error Description | Solution |
700 | Advertising system error | |
701 | Parameter error | |
710 | No ad information,or the ad is closed | |
720 | No cached information for ad clicks |
Error Code | Error Description | Solution |
750 | websdk error | |
751 | Session expired | |
780 | H5 promotion link error | |
781 | H5 promotion link is invalid |
Error Code | Error Description | Solution |
470 | Payer error | |
471 | MOL payment error | |
472 | MYCARD payment error | |
473 | APACPAY payment error | |
4731 | APACPAY merchant number error | |
4732 | APACPAY subaccount error | |
474 | FORTUMO payment error | |
475 | XSOLLA支付错误 | |
476 | RIXTY payment error | |
477 | BOACOMPRA payment error | |
478 | ALIPAY2 payment error |