1.1 Obtaining access_token
1.2 Receiving Callbacks
2.1 Obtaining a Ticket
2.2 Obtaining Authorization Page URL
2.3 Receiving Authorization Completion Event
2.4 Querying Authorization Information
2.5 Rejecting Collection of E-Bill
3.1 Obtaining Finance Bureau s_pappid
3.2 Receiving Authorization Completion Event

# 1. Common APIs

# 1.1 Obtaining access_token

API description
The access_token is the globally unique credential for an Official Accounts to call APIs. It is required for every API request of an Official Account, so developers need to keep it secure. To store the access_token, you need to reserve space for at least 512 characters. The access_token is valid for 2 hours and needs to be refreshed regularly. If you obtain a new access_token, the previous one will become invalid. We recommend that you obtain and refresh access_tokens using a central control server. All the access_token values used by other business logic servers come from this central control server and should not be refreshed separately. Otherwise, the access_token may be overwritten, which will affect services. For more information about access_tockens, see the Official Account development documentation. Request method
Request URL: https://api.weixin.qq.com/cgi-bin/token?grant_type=client_credential&appid=APPID&secret=APPSECRET
Request method: GET

Request parameters

Response Data format: JSON

Sample code

Response:
{
	"access_token":"ACCESS_TOKEN",
	"expires_in":7200
}

# 1.2 Receiving Callbacks

Log in to the Official Accounts Platform, go to Developer Center Settings, and set the URL for receiving callbacks. When a user authorizes the collection of an e-bill or the e-bill status is updated, the Weixin server notify the developer via this URL.
If the Weixin server does not receive the response within five seconds, the connection is broken and the request is initiated again. A maximum of three retries are made. If developer's server cannot ensure the request is processed within five seconds, it can return an empty string. When receiving the string, the Weixin server will not take any action or make a retry.

# 2. APIs for a Payee Organization

# 2.1 Obtaining a Ticket

API description
A ticket is used to improve security. It is valid for 2 hours and must be refreshed regularly. We recommend that Official Account developers obtain and refresh all tickets using a central control server. Request method
Request URL: https://api.weixin.qq.com/cgi-bin/ticket/getticket?access_token=ACCESS_TOKEN&type=wx_card
Request method: GET
Response
Data format: JSON

Sample code

{   
	"errcode": 0,   
	"errmsg": "ok",   
	"ticket": "m7RQzjA_ljjEkt-JCoklRM5zrzYr-6PI09QydZmNXXz-opTqMv53aFj1ykRt_AOtvqidqZZsLhCDgwGC6nBDiA",   
	"expires_in": 7200 
}

Notes

1. A ticket is valid for 7200 seconds. During the validity period, the ticket remains unchanged regardless of repeated requests.
2. A ticket must be cached at the payee organization's backend to be called normally.

# 2.2 Obtaining Authorization Page URL

API description
This API is used to obtain the authorization page URL to allow users to go to the authorization page. Request method
Request URL: https://api.weixin.qq.com/nontax/getbillauthurl?access_token={access_token}
Request method: POST Request parameters

Response Data format: JSON

If the error code is 0, the following information is returned:

Sample code

Request:
{
    "s_pappid": "wxabcd",
    "order_id": "1234",
    "money": 11,
    "timestamp": 1474875876,
    "source": "web",
    "redirect_url": "https://mp.weixin.qq.com",
    "ticket": "tttt"
}
Response:
{
    "errcode": 0, 
    "errmsg": "ok", 
    "auth_url": "http://auth_url",
    "expire_time": 7200
}

# 2.3 Receive Authorization Completion Event

API description
After the user's authorization, the Official Account of the payee organization receives the authorization completion event. For more information about the event push, see Receiving Callbacks.
Response
Data format: XML

Sample code

<xml>
	<ToUserName><![CDATA[gh_fc0a06a20993]]></ToUserName>
	<FromUserName><![CDATA[oZI8Fj040-be6rlDohc6gkoPOQTQ]]></FromUserName>
	<CreateTime>1475134700</CreateTime>
	<MsgType><![CDATA[event]]></MsgType>
	<Event><![CDATA[user_authorize_invoice]]></Event>
	<SuccOrderId><![CDATA[1202933957956]]></SuccOrderId>
	<FailOrderId><![CDATA[]]></FailOrderId>
	<AuthorizeAppId><![CDATA[]]></AuthorizeAppId>
	<Source><![CDATA[]]></Source>
</xml>

# 2.4 Querying Authorization Information

API description
The payee organization can call this API to query whether the user have granted authorization for the order.
Request method
Request URL: https://api.weixin.qq.com/card/invoice/getauthdata?access_token={access_token}
Request method: POST
Request parameters

Response Data format: JSON

Sample code

Request parameters
{
    "s_pappid": "{s_pappid}",
    "order_id": "{order_id}"
}
Response Data:
{
  "errcode": 0,
  "errmsg": "ok",
  "invoice_status": "auth success",
  "auth_time": 1480342498
}

# 2.5 Rejecting Collection of E-Bill

API description
After the user's authorization, if the payee organization finds that the information provided by the user is incorrect or a refund occurs, they can call this API to reject the e-bill collection and notify the user of the rejection.
Request method
Request URL: https://api.weixin.qq.com/card/invoice/rejectinsert?access_token={access_token}
Request method: POST
Request parameters

Response

Sample code

Request:
{
    "s_pappid": "d3JCEfhGLW+q0iGP+o9",
    "order_id": "111229",
    "reason": "1234",
    "url": "avb"
}
Response:
{
    "errcode": 0, 
    "errmsg": "ok"
}

# 3. APIs for a Finance Bureau

# 3.1 Obtaining Finance Bureau s_pappid

API description
This API is used to obtain the Finance Bureau s_pappid and pass it to the payee organization, which can use the s_pappid parameter to specify the finance bureau that provides billing services. A finance bureau only has one s_pappid so you only need to call the API once and save the s_pappid for later use.
Request method
Request URL: https://api.weixin.qq.com/card/invoice/seturl?access_token={access_token}
Request method: POST

Request parameters
The request parameters are in a JSON format and the input data is null, i.e. {}.
Response

Sample code

Request
{}
Response
{
  "errcode": 0,
  "errmsg": "ok",
 "invoice_url": "https://mp.weixin.qq.com/bizmall/authinvoice?action=list&s_pappid=d3xxxxxxxxxxxxxGLSS0wrL14No8c1"
}

# 3.2 Creating Financial E-Bills

API description
A finance bureau can use this API to help the payee organization create a financial e-bill template. A single finance bureau can work with multiple payee organizations, and each payee organization can only have a unique card_id.
Request method
Request URL: https://api.weixin.qq.com/nontax/createbillcard?access_token={access_token}
Request method: POST
Request parameters
Data format: JSON
"invoice_info" field of a financial e-bill

base_info field

Response

If the error code is 0, the following information is returned:

Sample code

Request:
{
    "invoice_info" : {
        "payee" : "Test non-tax revenue e-bill",
        "base_info" : {
            "logo_url": : "http://mmbiz.qpic.cn/mmbiz/iaL1LJM1mF9aRKPZJkmG8xXhiaHqkKSVMMWeN3hLut7X7hicFNjakmxibMLGWpXrEXB33367o7zHN0CwngnQY7zb7g/0"
        }
    }
}
Response:
{
    "errcode": 0, 
    "errmsg": "ok", 
    "card_id": "pjZ8Yt9WoOePThU0NfUKz5-tBEWU"
}

# 3.3 Uploading PDF File

API description
The finance bureau can use this API to upload the PDF file of an e-bill to the Weixin Financial E-Bill Platform for billing. The uploaded PDF is valid for three days and the "Adding an E-bill to Cards & Offers" API must be called before it expires.
Request method
Request URL: https://api.weixin.qq.com/card/invoice/platform/setpdf?access_token={access_token}
Request method: POST
Request parameters
Data format: multipart/form-data

Response Data format: JSON

Sample code

Request:
------WebKitFormBoundary2exwM16BY25kVBgf
Content-Disposition: form-data; name="pdf"; filename="1133090578170938.pdf"
Content-Type: application/pdf
Pdf content
------WebKitFormBoundary2exwM16BY25kVBgf--
Response:
{
  "errcode": 0,
  "errmsg": "ok",
  "s_media_id": "3015806758683707"
}

# 3.4 Obtaining PDF File

API description
This API is used to obtain the PDF file of a financial e-bill. Request method
Request URL: https://api.weixin.qq.com/card/invoice/platform/getpdf?access_token={access_token}
Request method: POST
Request parameters
Data format: JSON

Response
Data format: JSON

Sample code

Request:
{
         "action": "get_url",
         "s_media_id": "75195574948725301"
}
Response:
{
    "errcode": 0,
    "errmsg": "ok",
    "pdf_url": "https://mp.weixin.qq.com/intp/invoice/getpdf?action=media_pdf&media_key=dFRnTkV6WCswNjB1V1czZ0tVU3MhaX4yb2pxeEVSY0teSCtuflY6UXAifD5rL09kTjFpOFVWKyJGNCgxTCtkJER6VjFlRCtVU2JKcS5FZw",
    "pdf_url_expire_time": 7200
}

# 3.5 Adding an E-Bill to User's Cards & Offers

API description
After the user's authorization for collecting the e-bill, the payee organization requests the e-bill for an order from the finance bureau, which then issues the e-bill to the user using this API.
Request method
Request URL: https://api.weixin.qq.com/nontax/insertbill?access_token={access_token}
Request method: POST
Request parameters
Data format: JSON

"card_ext" includes the following information:

"user_card" includes an invoice_user_data object, which contains the following fields:

Response Data format: JSON

If the error code is 0, the following information is returned:

Sample code

Request:
{
    "order_id" : "1511169724",
    "card_ext" : {
        "user_card" : {
            "invoice_user_data" : {
                "billing_time" : "1511169724",
                "billing_code" : "aabbccdd",
                "billing_no" : "1511169724",
                "s_pdf_media_id" : "s_pdf_media_id",
                "fee" : 123,
                "title" : "Guan Ge's Bill"
            }
        }
    },
    "card_id" : "pjZ8Yt7xiy3b9UfffRIA4Tm2xTnw",
    "appid" : "wxc0b84a53ed8e8d29"
}
Response:
{
    "errcode": 0, 
    "errmsg": "ok", 
    "code": "682xxxx661927", 
    "openid": "ojZ8Ytz4lESxxxx_R1TvB2Kds"
}

# 3.6 Status Update Event Push

API description
When the reimbursing organization updates the status of a financial e-bill, the Official Accounts Platform pushes an Official Account message to the URL set by the finance bureau for receiving callback events. For more information about event push, see the section 6.1.2.
Response
Data format: XML

Sample code

<xml>
<ToUserName><![CDATA[gh_9e1765b5568e]]></ToUserName>
<FromUserName><![CDATA[ojZ8Ytz4lESgdWZ34L_R1TvB2Kds]]></FromUserName>
<CreateTime>1478068440</CreateTime>
<MsgType><![CDATA[event]]></MsgType>
<Event><![CDATA[update_invoice_status]]></Event>
<Status><![CDATA[INVOICE_REIMBURSE_INIT]]></Status>
<CardId><![CDATA[pjZ8Yt7Um2jYxzneP8GomnxoVFWo]]></CardId>
<Code><![CDATA[186921658591]]></Code>
</xml>

# 3.7 Updating E-Bill Status

API description
If the status of a financial e-bill of the finance bureau changes, this API should be called to sync the status to the Official Accounts Platform to ensure the financial e-bill status is consistent between the two sides.
Request method
Request URL: https://api.weixin.qq.com/card/invoice/platform/updatestatus?access_token={access_token}
Request method: POST
Request parameters
Data format: JSON

Response

Sample code

Request:
{
    "card_id": "pjZ8Yt7Um2jYxzneP8GomnxoVFWo",
    "code": "186921658591",
    "reimburse_status": "INVOICE_REIMBURSE_INIT"
}
Response:
{
    "errcode": 0, 
    "errmsg": "ok"
}

# 4. Remarks

# 4.1 Authorization Status for the Order

# 4.2 Error Codes