# Refused to open tickets
Interface should be called on the server side, not in the front end (Weixin Mini Program, web pages, APP, etc.) directly called, specific reference interface call guide
Interface name: invoicebizrejectinsert
After the user completes the authorization, the merchant can call the interface to refuse billing and inform the user if the user submits the information incorrectly, or if a refund has occurred.
After the denial of a billing, the order cannot be billed again to the user. Has refused to invoice orders, can not be used again, if you want to re-invoice, need to use a new order_id, get the authorization link, let the user to authorize again.
The notification message received by the user side after the interface is called is as follows:
# 1. How to call
# HTTPS calls
POST https://api.weixin.qq.com/card/invoice/rejectinsert?access_token=ACCESS_TOKEN
# Cloud Calls
- This interface does not support cloud calls
# Third party invocation
This interface supports Third Party Platform generation business call.
The permission set to which this interface belongs is: 26
When a service provider is authorized by one of the permissions set, it can call on behalf of the merchant by using authorizer_access_token , which can be viewed in the third-party call documentation.
# 2. Request parameters
# Query parametersQuery String parameters
Parameter Name | type | Required to fill in | Example | Introductions |
---|---|---|---|---|
access_token | string | yes | ACCESS_TOKEN | Interface invocation credentials, using access_token , authorizer_access_token |
# Request BodyRequest Payload
Parameter Name | type | Required to fill in | Introductions |
---|---|---|---|
s_pappid | string | yes | The identification of the billing platform on WeChat, and the billing platform informs the merchant |
order_id | string | yes | Order id |
reason | string | yes | The merchant explains the reasons for refusing to open the bill, such as repeated billing, invalid lifting, returned goods and unable to open a bill. |
url | string | no | Jump to a link to guide the user to the next step, such as re-initiating a ticket, refilling a raise, showing the status of the order, etc. |
# 3. Return Parameters
# Response Payload
Parameter Name | type | Introductions |
---|---|---|
errcode | number | Error code |
errmsg | string | Error Description |
# 4. Note
There are no special considerations for this interface
# 5. Code examples
Example Requests
{
"s_pappid": "d3JCEfhGLW+q0iGP+o9",
"order_id": "111229",
"reason": "1234",
url": "http://URL地址"
}
Return an example
{
"errcode": 0,
"errmsg": "ok"
}
# 6. Error code
The following is a list of error codes for this interface, other error codes can refer to General error codes
Error code | Error Description | Solutions |
---|---|---|
40001 | invalid credential access_token isinvalid or not latest | access_token Invalid or not recently acquired access_token, please confirm the validity of the access_token |
# 7. Scope of application
Official Account | Service Account |
---|---|
✔ | ✔ |
- ✔: The account can call this interface
- Other account types that are not expressly stated may not be called on this interface without special instructions;