# Apply for Merchant Number Authorization

Debugging tools

Interface should be called on the server side, seeHattori API

# Interface Dxplaination

# Interface name

GetWechatPayAuth

# Functional description

Through this interface, you can apply for business number authorization, if you encounter problems in the process of use, you canOpen Platform Service Provider ZonePosting exchanges.

# Note

  • The Mini Program needs to authorize [cloud development permission set] or [cloud development WeChat payment permission set] to a third party, and the third party can call this interface on behalf of the Mini Program.

# Other additions

  • Small programs need to open WeChat payment, and bind the merchant number. referenceAccess Guidelines

  • The supermanagement of the merchant number needs to pay attention to the merchant assistant Official Account message template。

  • After adding the merchant number, you need to bind the account and jsapi separately. and api Refund authority granted. Please note:

  1. Account binding: The super administrator of the merchant number needs to confirm authorization on the [WeChat Pay Merchant Assistant] mini program provided by WeChat Pay.

2)jsapi and api Refund permission, need to go to WeChat Pay merchant platform My Authorized Product to confirm authorization.details

  • After completing the authorization, you can call WeChat payment related interface capabilities.

# Calling mode

# HTTPS call


POST https://api.weixin.qq.com/tcb/wxpayopenauth?access_token=ACCESS_TOKEN 

# Third Party Invocation

  • The calling method and parameters are the same as HTTPS, only the calling token is different

  • The permission sets to which this interface belongs are: 49, 64, 102

  • After the service provider has been authorized with one of the permission sets, it can do so by usingauthorizer_access_TokenCalling on behalf of the merchant

# Request parameters

attribute type Required Introductions
access_Token string yes Interface invokes the certificate, which is URL Parameters, non Body Parameters. useauthorizer_access_Token
action string yes bind/openjsapi/openrefund
merchant_code string yes Merchant No.

# Return parameters

attribute type Introductions
errcode number Error code
errmsg string Error message

# Call Example

Example Dxplaination: HTTPS requests

# Sample Request Data


{
    "action": "bind",
    "merchant_code": "1900006511"
} 

# Return Data Example


{
    "errcode": 0,
    "errmsg": "ok"
} 

# Error code

Error code Error code Solutions
0 ok ok
-1 system error The system is busy, please wait for the developer to try again
-1000 system error System error
40014 invalid access_Token Illegal access_Token Please take the developer seriously. access_Token Of the validity (such as whether it is expired), or to see if you are working for the appropriate Official Account message template Call interface
40097 invalid args Parameter error
40101 missing parameter Missing required parameters
41001 access_Token missing lack access_Token parameter
42001 access_Token expired access_Token Timeout, please check access_Token Of the validity period, please refer to the Basic Support - Obtain access_Token Middle, right. access_Token Detailed mechanism explaination of the
43002 require POST method Need POST request
44002 empty post data POST The packet is empty.
47001 data format error analysis JSON/XML Content errorpost Missing parameters in the dataCheck for corrections and try again.
85088 no qbase privilege The app is not open for cloud development