# Check for reimbursement invoices information
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 English name: invoicebxgetinvoice
After the reimbursement party obtains the identification parameters of the electronic invoice selected by the user in the previous step, it can query the structured information of the electronic invoice through the interface and obtain the invoice PDF file.
# 1. How to call
# HTTPS calls
POST https://api.weixin.qq.com/card/invoice/reimburse/getinvoiceinfo?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 | Introductions |
---|---|---|---|
access_token | string | yes | Interface invocation credentials, using access_token , authorizer_access_token |
# Request BodyRequest Payload
nothing
# 3. Return Parameters
# Response Payload
Parameter Name | type | Introductions |
---|---|---|
card_id | string | Invoice id |
begin_time | number | The starting time of the validity period of the invoice |
end_time | number | Deadline of the invoice |
openid | string | User ID |
type | string | Type of invoice, such as Guangdong VAT General Invoice |
payee | string | The recipient of the invoice |
detail | string | Invoice details |
user_info | object | Main information that users can see on the face of the invoice |
# Res.user_infoObject Payload
Main information that users can see on the face of the invoice
Parameter Name | type | Introductions |
---|---|---|
fee | number | The amount of the invoice divided into units |
title | string | The rise of invoices |
billing_time | number | Invoice time, 10-digit time stamp (UTC + 8) |
billing_no | string | The invoice number of the invoice; Numerical invoice transmits 20 digit invoice number |
billing_code | string | The invoice code of the invoice; Electrical invoice The invoice code is empty |
info | objarray | Details of product structure |
fee_without_tax | number | Excluding the amount of tax, divided into units |
tax | number | The amount of tax, divided into units |
pdf_url | string | PDF for this invoice_URL |
trip_pdf_ur | string | URL corresponding to the attachments of other consumer vouchers, such as taxi tickets, water bills, etc. |
check_code | string | Check code, invoice pdf upper right corner, invoice date under the check code; Electrical invoice verification code is empty |
buyer_number | string | Buyer's Taxpayer Identification Number |
buyer_address_and_phone | string | Buyer's address, phone number |
buyer_bank_account | string | Buyer's bank account and account number |
seller_number | string | Seller Taxpayer Identification Number |
seller_address_and_phone | string | The seller's address and phone number |
seller_bank_account | string | The seller's account and account number |
remarks | string | Note, the beginning of the bottom right corner of the invoice |
cashier | string | Recipient, bottom left corner of the invoice |
maker | string | The invoicer, at the bottom of the invoice |
reimburse_status | string | Status of invoice reimbursement |
# Res.user_info.info(Array)Object Payload
Details of product structure
Parameter Name | type | Introductions |
---|---|---|
name | string | Name of the project |
num | number | Number of projects |
unit | string | Unit of the project, such as a |
price | number | Unit price of the project |
# 4. Note
The invoice status code and the meaning of the status are as follows:
state | meaning |
---|---|
INVOICE_REIMBURSE_INIT | Initial status of invoice, not locked, may be submitted for reimbursement |
INVOICE_REIMBURSE_LOCK | The invoice is locked and cannot be repeated to submit reimbursement |
INVOICE_REIMBURSE_CLOSURE | The invoice has been written off and removed from the user card package |
# 5. Code examples
Example Requests
{
"card_id": "pjZ8Yt7KKEXWMpETmwG2ZZxX2m6E",
"encrypt_code": "O/mPnGTpBu22a1szmK2 "
}
Return an example
{
"errcode": 0,
"errmsg": "ok",
"user_info": {
"fee": 123,
"title": "灌哥发票",
"billing_time": 1504085973,
"billing_no": "1504085973",
"billing_code": "aabbccdd",
"info": [
{
"name": "牙膏",
"num": 3,
"unit": "个",
"price": 10000
}
],
"fee_without_tax": 2345,
"tax": 123,
"detail": "项目",
"pdf_url": "http://pdfurl",
"reimburse_status": "INVOICE_REIMBURSE_INIT",
"order_id": "1504085935",
"check_code": "check_code",
"buyer_number": "buyer_number"
},
"card_id": "pjZ8Yt7KKEXWMpETmwG2ZZxX2m6E",
"openid": "oZI8Fj8L63WugQsljlzzfCcw3AkQ",
"type": "广东省增值税普通发票",
"payee": "测试-收款方",
"detail": "detail"
}
# 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 |
---|---|---|
0 | Ok or in a normal state | OK means to go from abnormal to normal in a normal state |
72015 | unauthorized create invoice | No authority to operate an invoice |
72017 | invalid invoice title | Invoices are rising inconsistently |
72023 | invoice has been lock by others | Invoice has been locked by other Official Account |
72024 | invoice status error | Invoices are incorrectly registered |
# 7. Scope of application
Weixin Mini Program | Official Account | Service Account | Mobile App |
---|---|---|---|
Certification only | ✔ | ✔ | ✔ |
- Authentication only: means that only authenticated accounts are allowed to be invoked by the enterprise entity, and accounts that are not authenticated or do not support authentication cannot be invoked.
- ✔: The account can call this interface
- Other account types that are not expressly stated may not be called on this interface without special instructions;