Scenario Description

In this solution, the institution should develop a POS software for merchants. For example, an app can be installed on mobile devices. Merchants can then install this app on their mobile phones or tablets to collect payments.

This app provides two payment modes. The first is that merchant makes the payment through scanning customer’s payment code via a mobile device. So the product payment is done via QuickPay.

Quick Pay refers to the payment code of the WeChat client that users presents, and the merchant uses the barcode scanning device to obtain the user's payment code bar code (the code is 18 digits, starting with 10, 11, 12, 13, 14, 15). The payment code is then carried to request the WeChat payment interface to complete the deduction. In this payment mode, if the payment amount is less than 3000 RMB or the number of payments on the day is less than 10 times, the request will be deducted directly without requiring the user to enter a password. If any of the above conditions are not met, the user will be required to enter a password to verify the deduction.

In the second mode, the app generates an order and requests WeChat pay to get a QR code, and the dynamic order-based QR code is displayed for users to scan for payment. So the product payment is done via native payment.

Native payment refers to the institution carrying order information to request WeChat payment. The WeChat system will generate a pre-payment order and return a dynamic QR code link code_url to the institution. The institution can generate a QR code based on the content of the code_url for the user to scan to complete the payment.

Parameter Configuration

In this scenario, no extra parameter configuration is needed no matter which payment mode is used. The institutions only need to apply for the required parameters and configure development parameters by referring to Parameters needs to be applied, API key configuration and Certificate configuration.

Precautions

Note that this solution is not In-App Payment. In-app payment is where users select products in a merchant's app and then WeChat is launched by the app for user payment. (For details, visit In-APP payment introduction.)

As this solution completely separates the developed app with the merchant's existing acquiring system, workload in bill checking is increased.

Scenario Description

This solution applies to merchants with no POS terminal or mobile cashier device available, which are usually small-sized physical supermarkets or food courts.

In this case, the Official Account Payment mode can be used to collect payments via a fixed QR code.

Official Account Payment refers to the user opening a webpage in WeChat webview and loading the WeChat payment plugin through this webpage.

When users need to pay for products, the merchant can present its fixed QR code for users to scan with WeChat, and a web page will be displayed in the WeChat app. Users can then enter the required payment amount on the web page, confirm the payment, and enter the payment password to complete the payment.

To use this mode, the institution must do the following:

1. Develop a web page for users to enter the payment amount and complete the payment.

2. Generate an independent page URL for each of its sub-merchants, which can be differentiated by page parameters.

3. Connect with WeChat Pay through Official Account Payment.

4. Generate fixed QR codes based on the page URLs of merchants for collecting payments.

5. Complete

Parameter Configuration

In this scenario, the institutions need to apply for the required parameters and configure development parameters by referring to Parameters needs to be applied, API key configuration and Certificate configuration. In addition, they must configure two more parameters:

1. Authorization domain name: In this scenario, before the payment is initiated, the user's openid needs to be obtained via web authorization (auth2) to verify whether the order placement and payment are done by the same person. The domain name for auth2 authorization must be configured on the institution's Official Account platform, as shown below. For details, visit Webpage Authorization.

2. Payment directory: In this solution, WeChat Pay is launched by a web page in WeChat using the frontend JSAPI. For security reasons, the web directory that launches WeChat Pay also needs to be configured in the development configuration, as shown below.

Note: The payment directory refers to the part before the last slash (/) in a page URL. For example, if the page URL is "xxx.xxx.com/xx/x/xx", then the payment directory wll be "xxx.xxx.com/xx/x/".

Precautions

This solution is generally applicable to small and micro merchants in mainland China. It helps merchants to quickly access WeChat Pay with high duplicability.

However, with no device or frontend system at all, the merchants will not receive notifications after users make payments. Institutions are thus advised to develop some result notification channels for merchants, such as an Official Account message template or an app dedicated for result notification.