Detailed explanation of WeChat applet payment function development error summary-Mini Program Development-php.cn

Home

WeChat Applet

Mini Program Development

Detailed explanation of WeChat applet payment function development error summary

Mar 27, 2017 pm 02:06 PM

WeChat applet

This article mainly introduces relevant information on the summary of errors in the development of the payment function of WeChat Mini Program. Friends in need can refer to the following

Summary of errors in the development of payment function of WeChat Mini Program

WeChat Mini Program I finally got through the pitfalls in payment, and found that there are quite a lot of pitfalls inside. I’m posting a post now, hoping that students who will fall into the trap in the future can take a look at it:

https://pay.weixin.qq.com/ wiki/doc/api/wxa/wxa_api.php?chapter=7_4&index=2

The business process can be seen here when you read the document. The first pitfall is to obtain the user's openid. The parameters must be spelled in the url connection, otherwise an error of {"errcode":40013,"errmsg":"invalid appid, hints: [ req_id: iil1ba0504ns86 ]"} will be reported

 onLoad: function () {
  var that = this
  wx.login({
   success: function (res) {
    if (res.code) {
     //发起网络请求
     wx.request({
      url: 'https://api.weixin.qq.com/sns/jscode2session?appid=wxaacf22345345cfc7162fe3&amp;secret=83ebd41c3e6f34a49b3a34578063434548ff3f71&amp;js_code=' + res.code + '&amp;grant_type=authorization_code',
      method: "POST",
      success: function (res) {
       that.setData({
        openid: res.data.openid
       })
      }
     })
    } else {
     console.log('获取用户登录态失败！' + res.errMsg)
    }
   }
  });
 }

Copy after login

The second pitfall is the unified payment ordering interface. Signature pitfall is a pitfall that many people encounter. This is because MD5 encryption is often different from the encrypted signature in the signature tool.

Signature Encryption tool address: https://pay.weixin.qq.com/wiki/doc/api/jsapi.php?chapter=20_1

When signing and encrypting, it must be converted to utf-8 and encrypted I use my own interface to encrypt digest.update(data.getBytes("utf-8"));

 // 统一下单接口获取sign（签名）
 paysignjsapi: function (appid, attach, body, mch_id, nonce_str, notify_url, openid, out_trade_no, spbill_create_ip, total_fee, trade_type, key) {
  var self = this;
  //加密签名
  wx.request({
   url: 'http://localhost:8080/XinXingWXApi/wxXcxApi/Md5Encrypt.do',
   method: 'GET',
   data: {
    appid: appid,
    attach: attach,
    body: body,
    mch_id: mch_id,
    nonce_str: nonce_str,
    notify_url: notify_url,
    openid: openid,
    out_trade_no: out_trade_no,
    spbill_create_ip: spbill_create_ip,
    total_fee: total_fee,
    trade_type: trade_type,
    key: key
   },
   //统一下单
   success: function (res) {
    var sign = res.data.strMd5
    var formData = "&lt;xml&gt;"
    formData += "&lt;appid&gt;" + appid + "&lt;/appid&gt;" //appid 
    formData += "&lt;attach&gt;" + attach + "&lt;/attach&gt;" //附加数据 
    formData += "&lt;body&gt;" + body + "&lt;/body&gt;"    //标题
    formData += "&lt;mch_id&gt;" + mch_id + "&lt;/mch_id&gt;" //商户号 
    formData += "&lt;nonce_str&gt;" + nonce_str + "&lt;/nonce_str&gt;" //随机字符串，不长于32位。 
    formData += "&lt;notify_url&gt;" + notify_url + "&lt;/notify_url&gt;" //异步接收微信支付结果通知的回调地址
    formData += "&lt;openid&gt;" + openid + "&lt;/openid&gt;"  //用户Id
    formData += "&lt;out_trade_no&gt;" + out_trade_no + "&lt;/out_trade_no&gt;" //商户订单号
    formData += "&lt;spbill_create_ip&gt;" + spbill_create_ip + "&lt;/spbill_create_ip&gt;"
    formData += "&lt;total_fee&gt;" + total_fee + "&lt;/total_fee&gt;" //金额
    formData += "&lt;trade_type&gt;" + trade_type + "&lt;/trade_type&gt;"  //公共号支付
    formData += "&lt;sign&gt;" + sign + "&lt;/sign&gt;"//签名
    formData += "&lt;/xml&gt;"

Copy after login

Return data analysis xml

 //请求统一下单接口
    wx.request({
     url: "https://api.mch.weixin.qq.com/pay/unifiedorder",
     method: 'POST',
     data: formData,
     success: function (data) {
      wx.request({
       url: "http://localhost:8080/XinXingWXApi/wxXcxApi/xmlAnalyze.do?strXml=" + data.data,
       method: 'POST',
       success: function (res) {
        var pk = 'prepay_id=' + res.data.prepayId;
        var timeStamp = self.createTimeStamp();
        //获取支付签名，并支付
        self.getsignType(appid, timeStamp, nonce_str, pk, "MD5", key);
       }
      })
     }
    })
   }
  });
 }

Copy after login

The third is to call payment, here There are also a few pitfalls. The first is that many appIds cannot be written as appid. The second is that the parameter format of preoatid must be written correctly prepay_id=wx2017011711060194dccf725232155886323. The third is that a payment signature error is reported when calling payment, and you also need to check the signature interface. Check whether the signatures are consistent and check whether the parameters are correct. When calling WeChat payment, you must add the appId

getsignType: function (appid, timeStamp, nonce_str, pk, signType, key) {
  var that = this;
  wx.request({
   url: "http://localhost:8080/XinXingWXApi/wxXcxApi/getSignType.hn",
   method: 'GET',
   data: {
    appId: appid,
    timeStamp: timeStamp,
    nonceStr: nonce_str,
    pk: pk,
    signType: signType,
    key: key
   },
   success: function (res) {
    console.log(res.data.paySign)
    var paySign = res.data.paySign
    //调用微信支付
    wx.requestPayment({
     'appId': appid,
     'timeStamp': timeStamp,
     'nonceStr': nonce_str,
     'package': pk,
     'signType': 'MD5',
     'paySign': paySign,
     'success': function (res) {
      console.log(res);
      console.log('success');
     },
     'fail': function (res) {
      console.log(res);
      console.log('fail');
     },
     'complete': function (res) {
      // console.log(res);
      console.log('complete');
     }
    });
   }
  })
 }

Copy after login

Thank you for reading, I hope it can help everyone, thank you for your support of this site!

The above is the detailed content of Detailed explanation of WeChat applet payment function development error summary. For more information, please follow other related articles on the PHP Chinese website!

Statement of this Website

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