Error Analysis: The merchant has no authority.
Solution: Contact appropriate business personnel to enable payment authority.

For error analysis and solutions for when "-1" is returned when calling up app to pay fails, please refer to [article]

Error Analysis: Incorrect information provided in ID field.
Please rectify according to the following guidelines. Unify the order-placing interface, the field name returned to initiate the payment interface is "prepay_id", the field name imported is "prepayid".

Configuration path of App application signature: go to [Management Center - Modify Application - Modify Development Information] in [Open Platform]

The App payment app signature uses md5. Please refer to the access guide for the app signature algorithm.

Due to the verification rules of the interface, no verification of the package name or signature was made in the first request.
Please check them. Please check if the package name of the app is consistent with the package signature configured on the open platform.

Error Analysis: Repeated merchant's order number.
Solution: Please check with the merchant if the order number was submitted more than once.

Error Analysis: Order does not exist.
Solution: Please check if a transaction was indeed initiated under the order.

Yes. The app can be docked with merchant's accounts with different subjects, but this has to be done through an offline application. Please contact relevant business personnel for help.

Link the relevant appid with the corresponding merchant number under the merchant's platform.

Error Analysis: Business rules restrictions.
Solution: The request frequency was restricted by business , please try again after lowering the request frequency.

Error Analysis: Insufficient balance.
Solution: Insufficient balance in the user account, please prepay or change the card for payment.

Error Analysis: Merchant's number does not exist.
Solution: Please check if the merchant's number is correct.

Error Analysis: Out of frequency limits.
Solution: Please lower the interface request frequency.

Error Analysis: Abnormality detected in the account.
Solution: No operations can be done as the account is abnormal.

Error Analysis: Order closed.
Solution: The current order is closed, please place another order.

Error Analysis: Wrong order number.
Solution: Please check if the WeChat Pay order number is correct.

Error Analysis: Invalid request.
Solution: Please check against the details returned by the interface.

Not necessarily.

Please check if the appid for initiating payment by the merchant and the appid obtained when sending the order request is consistent.

1. Please check if the application package name configured on the open platform is consistent with the package settings in the androidmanifest files.
2. If the two are consistent, please manually wipe the cache and try again.
3. Check if the letters of the package name of the open platform is in lowercase.

Please check according to the following process:
1. Check if there is any space between the order placement parameters.
2. Check if the CNY parameter in the fee_type field is in uppercase.

When the app initiates payment request, "Incorrect appid parameters uploaded by merchant, please contact the merchant for help" is returned, this is caused by inconsistency between the parameter appid for initiating payment request and the parameter appid submitted through the unified order placement interface.

For the appid and partnerid initiating payments, sub-merchant parameters need to be provided, i.e. the appid of the sub-merchant's app and the sub-merchant number.

Not under the V2 and V3 interface rules. Please strictly adhere to the app payment methods.

Please check the following items:
1. If the parameter prepayid initiated for payment is correct. Please check if it is a character string, and if the transcoding is correct.
2. A secondary signature is required when initiating payment, so please check if the parameters used when submitting the secondary signature is correct.

The app does not support embedded H5, please use the app to initiate the payment interface.

Please check against the following items:
1. Check whether the merchant ID and appid are used correctly.
2. Check whether the request address is correct and whether the applicable object of the interface matches the merchant ID type.
3. Use the same parameters and call it again later.
4. Please check whether the merchant API certificate serial number of Authorization in the request header matches the merchant ID of the request header

Yes, the user can not pay for the order anymo

Please check whether the parameter "fee_type" uploaded in the unified order is caused by a filling error