# Get List of Merchant Numbers for Authorization Binding

Interface should be called on the server side, seeHattori API。

# Interface Dxplaination

# Interface name

GetWechatPayList

# Functional description

Through this interface can query the list of authorized binding merchant numbers, if you encounter problems in the process of use, you canOpen Platform Service Provider ZonePosting exchanges.

# Note

Dxplaination: 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.

# Calling mode

# HTTPS call


POST https://api.weixin.qq.com/tcb/wxpaylist?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	初始值	Required	Introductions
access_Token	string	yes	Interface invokes the certificate, which is URL Parameters, non Body Parameters. useauthorizer_access_Token

# Return parameters

attribute

type

Introductions

errcode

number

Error code

errmsg

string

Error message

list

array

Merchant Number Information

attribute	type	Introductions
merchant_code	string	Merchant id
merchant_name	string	Merchant Name
company_name	string	Principal name
mch_relation_state	number	Binding relationship
jsapi_auth_state	number	Jsapi authorization status
refund_auth_state	number	Refund Authorization Status

# Call Example

Example Dxplaination: HTTPS requests

# Sample Request Data

{
}

# Return Data Example


{
    "errcode": 0,
    "errmsg": "ok",
    "list": [
        {
            "merchant_code": "1900006511",
            "merchant_name": " MIOKKK Municipal Government - test_mdm",
            "company_name": "weappgovernment111,"
            "mch_relation_state": "RELATION_BINDED",
            "jsapi_auth_state": "AUTH_AUTHORIZED",
            "refund_auth_state": "AUTH_AUTHORIZED"
        },
        {
            "merchant_code": "1800008315",
            "merchant_name": WeChat Official Platform,
            "company_name": "Shenzhen Tencent Computer Systems Company Limited,"
            "mch_relation_state": "RELATION_WAIT_CONFIRM_WXTPL",
            "jsapi_auth_state": "AUTH_WAIT_CONFIRM_WXTPL",
            "refund_auth_state": "AUTH_UNAUTHORIZED"
        },
        {
            "merchant_code": "11485517",
            "merchant_name": "short for businessmen."
            "company_name": "guangping street 2,"
            "mch_relation_state": "RELATION_WAIT_CONFIRM_WXTPL",
            "jsapi_auth_state": "AUTH_WAIT_CONFIRM_WXTPL",
            "refund_auth_state": "AUTH_UNAUTHORIZED"
        }
    ]
}

# Error code

Error code	Error code	Solutions
40001	invalid credential access_Token isinvalid or not latest	Obtain access_Token time AppSecret Error, or access_Token Invalid. Please take the developer more seriously. AppSecret Of the correctness, or to see if you are working for the appropriate Official Account message template Call interface
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