How to solve-1 returned by WeChat payment APP

In the development documentation,-1 "possible causes: Incorrect signature, unregistered APPID, incorrect Project Settings APPID, mismatch between registered APPID and settings, and other exceptions .", However, I have checked whether there is a problem. The APP can pay for the test using the DEMO, but the service end cannot send the test to the APP... possible causes of-1 in the Development Documentation: Signature error, unregistered APPID, incorrect Project Settings APPID, mismatch between registered APPID and settings, and other exceptions. ", But I have checked whether it is correct. The APP can pay for the test using the DEMO, but the server cannot send it to the APP.
It is also good that unified payment has been tested.
["Result"] => array (9 ){

["Return_code"] => string (7) "SUCCESS" ["return_msg"] => string (2) "OK" ["appid"] => string (18) "******" // bind the paid APPID ["mch_id"] => string (10) "******" // merchant ID ["nonce_str"] => string (16) "OCTmjzp0A8v7UnbD" ["sign"] => string (32) "9F50899D68ABE30F7E311D477D6C0383" ["result_code"] => string (7) "SUCCESS" ["prepay_id"] => string (36) "wx201507301633164e148bfddb0142377854" ["trade_type"] => string (3) "APP"

}

The value sent to the APP is:
{

Appid = ******; // APPIDnoncestr = fdcb60638d9e6e54cb702f5d5b67a4d7; package = "Sign = WXPay"; partnerid = ******; // merchant ID prepayid = wx20150730151416e2a37094d20267969653; sign = 834740f9670051d37bde95a44e8138df; timestamp = 1438240456;

}

Click pay to jump in, and then return to the APP immediately

Solved. The order is wrong. It should be in the document order.

Reply content:

In the development documentation,-1 "possible causes: Incorrect signature, unregistered APPID, incorrect Project Settings APPID, mismatch between registered APPID and settings, and other exceptions .", But I have checked whether it is correct. The APP can pay for the test using the DEMO, but the server cannot send it to the APP.
It is also good that unified payment has been tested.
["Result"] => array (9 ){

["Return_code"] => string (7) "SUCCESS" ["return_msg"] => string (2) "OK" ["appid"] => string (18) "******" // bind the paid APPID ["mch_id"] => string (10) "******" // merchant ID ["nonce_str"] => string (16) "OCTmjzp0A8v7UnbD" ["sign"] => string (32) "9F50899D68ABE30F7E311D477D6C0383" ["result_code"] => string (7) "SUCCESS" ["prepay_id"] => string (36) "wx201507301633164e148bfddb0142377854" ["trade_type"] => string (3) "APP"

}

The value sent to the APP is:
{

Appid = ******; // APPIDnoncestr = fdcb60638d9e6e54cb702f5d5b67a4d7; package = "Sign = WXPay"; partnerid = ******; // merchant ID prepayid = wx20150730151416e2a37094d20267969653; sign = 834740f9670051d37bde95a44e8138df; timestamp = 1438240456;

}

Click pay to jump in, and then return to the APP immediately

Solved. The order is wrong. It should be in the document order.

We also encountered the same problem. Have you solved it?

According to your description, the pre-payment id is successfully generated, but the payment information is incorrect when it is submitted. Check the payment information verification and encrypt the information to be submitted and the merchant's payment key, generate a new sign, and then submit

Has the landlord solved the problem? I encountered the same problem in App payment development.

I also encountered this situation.
Finally, we found that it was a cache problem (this problem also exists for similar sharing and so on ).
You only need to clear the cache in the settings.
I spent N days in the dark. (Greeting penguin)