WeChat payment service provider model (acceptance agency model) development considerations, jsapi payment

1. The demo you download first usually has some bugs, so you need to change it first.

2. It seems that WeChat has not developed a separate demo for the service provider model, and the downloaded ones are all payment demos for ordinary merchants. In fact, there is no need to write them separately here, because the difference between them is just a few parameters.

(0) All parameters set in the demo must be filled in with those of the service provider, not the sub-merchant.

(1) The first difference is openid. The openid is passed directly in the demo. In the service provider mode, sub_openid needs to be passed. The method of obtaining it is not explained. In short, what is needed to obtain it is the appid and appsecret of the sub-merchant, that is, the special merchant.

(2) You need to pass one more sub_mch_id parameter on the incoming page.

(3) Comment out the code that determines openid in the calling class, otherwise you will never be able to proceed to the next step.

(4) Set up the authorization directory in the WeChat payment merchant backend of the service provider, instead of setting it up in the public platform backend like ordinary merchants.

The demo has been updated. Those who still don’t understand it can download it and have a look.

If there are no other special requirements, you can use it directly if the parameters are filled in correctly.

Address:

The above has introduced the development considerations for the WeChat payment service provider model (acceptance agency model), jsapi payment, including aspects of the content. I hope it will be helpful to friends who are interested in PHP tutorials.