WeChat JSAPI payment report bizarre missing parameter error

Using Jsapi V3 's demo page, click the Pay button to report the error: "2 call to pay Jsapi missing parameters: $key 0$get_brand_wcpay_request:fail", what is this $key0$?? I don't know what parameters are missing, so the feedback is too bad.

Reply content:

Using Jsapi V3 's demo page, click the Pay button to report the error: "2 call to pay Jsapi missing parameters: $key 0$get_brand_wcpay_request:fail", what is this $key0$?? I don't know what parameters are missing, so the feedback is too bad.

I have the same problem, the problem is that the timestamp parameter in the Payment API interface on the Web side, must be a string type, but PHP default generated timestamp is the int type. The solution is to modify the next lib/wxpay.data.php about 2731 lines Settimestamp method, revision to$this->values['timeStamp'] = (string)$value;
Can

Show me the code.

In addition the JS payment process is:
1. The server-side call interface generates a pre-paid order where a callback address is required (unified next-to-single interface)
2. Call method for generating JSAPI based on interface return data
3. Active or user Click to trigger the method (Web page end of the payment API)
4. The user pays successfully, JS returns to pay the success or not (the document says that the return result is not guaranteed to be completely reliable)
5. If payment is successful, the callback address interface (notification interface document) will be invoked on your own initiative.

Note: Pay a variety of pits, look at official documents, can not directly make, there are problems more Google.

The official SDK is available, but the configuration is cumbersome, basically the process is similar to @tking, in addition, I am also developing a third-party SDK, the payment section is testing:

Http://github.com/thenbsp/wechat

Hello, I also met the same problem, ask how the final solution, thank you

My payment solution was initiated in a jssdk way.

Is there a solution to this problem? I also met ~ Check the parameters, settings are no problem ~

That's my problem, too.

