Home >Backend Development >PHP Tutorial >WeChat payment scan code payment development: pitfalls I encountered and solutions (attached: Ecshop WeChat payment plug-in), ecshop_PHP tutorial

WeChat payment scan code payment development: pitfalls I encountered and solutions (attached: Ecshop WeChat payment plug-in), ecshop_PHP tutorial

WBOY
WBOYOriginal
2016-07-13 09:44:42931browse

Development of scan code payment for WeChat payment: pitfalls I encountered and solutions (attached: Ecshop WeChat payment plug-in), ecshop

Helped a friend some time ago The mall developed based on ecshop added the WeChat scan payment function. I thought it would be a very simple matter - download the official sdk or development help document and follow the instructions in it. Who knows that it took two or three days to get it done? , I also looked for a lot of technical articles on the Internet with questions, but found that they only wrote roughly how they developed the access, and did not solve the problems I encountered... Alas, sometimes I really feel 'You can only rely on yourself'. The purpose of this article is to write down the problems and solutions I encountered, so that friends who develop in this area can be helpful!

Before development, please check the official [Scan QR code payment] development document. Scan QR code payment is divided into the following two modes:

 △Mode 1:

 Problems encountered: The first scan of the QR code can still be scanned normally, but if you scan again without payment, it will prompt: ok or the request for merchant information has timed out and the HttpCode is not 200——I have tried to find a solution through various channels to no avail. I hope someone who knows can give me an answer. Thank you!

 △Mode 2:

 Note: You cannot directly use the mall’s order number as the transaction order number (out_trade_no), otherwise the WeChat scan code payment number will be generated again When entering the QR code, the interface will prompt: The merchant order number is repeated and cannot be regenerated.

So here comes Jiang Zi’s question, how should I set the transaction order number and ensure that the corresponding order information in the WeChat merchant platform can be queried through the interface later or reconciliation can be achieved? The feasible method is: use the unified order interface before scanning the QR code. Instead of passing in the order number of the mall order system for out_trade_no, regenerate a new unique flow; add another order number corresponding to the WeChat payment transaction order number (out_trade_no). Table, as follows:

WeChat payment scan code payment development: pitfalls I encountered and solutions (attached: Ecshop WeChat payment plug-in), ecshop_PHP tutorial There is a serial_is_paid field in the above table: used to mark whether this transaction has been completed, that is: in the payment success notification callback processing, the payment status is updated according to the returned out_trade_no; as for how to query the order payment Status, I think you should also know...

Okay, I have n’t written a technical blog that I ca n’t find my feelings for a long time. The writing may be rough. If you have unclear friends, you can pay attention to & communication! WeChat payment scan code payment development: pitfalls I encountered and solutions (attached: Ecshop WeChat payment plug-in), ecshop_PHP tutorial

Reference website>>

Ecshop WeChat payment plug-in.rar

My WeChat subscription account:

zxcknowmore, your attention and support are the motivation for me to write more blog posts!

http://www.bkjia.com/PHPjc/1048740.htmlwww.bkjia.comtruehttp: //www.bkjia.com/PHPjc/1048740.htmlTechArticleWeChat payment scan code payment development: pitfalls I encountered and solutions (attached: Ecshop WeChat payment plug-in) , ecshop Some time ago, I helped a friend’s mall developed based on ecshop to add WeChat scanning...
Statement:
The content of this article is voluntarily contributed by netizens, and the copyright belongs to the original author. This site does not assume corresponding legal responsibility. If you find any content suspected of plagiarism or infringement, please contact admin@php.cn