Public number Payment-scenario introduction (from official documents)

The merchant already has the H5 Mall website, when the user opens the webpage through the message or scanning QR code, can call the payment to complete the order purchase process.

Step (1): 7.1, the merchant issued a text message or through a custom menu to attract users to click into the Merchant Web page.

Step (2): 7.2, enter the merchant webpage, the user chooses to purchase, completes the purchase process.

Figure 7.1 Merchant Custom Message Interface Figure 7.2 Merchant Web page Order

Step (3): 7.3, adjust the payment control, the user starts to enter the payment password.

Step (4): 7.4, password verification passed, payment successful. The merchant backstage is notified of successful payment.

Figure 7.3 User Confirmation Payment, enter password Figure 7.4 User payment success Prompt

Step (5): 7.5, return to the Merchant page to display the purchase success. This page is custom-defined by the merchant.

Step (6): 7.6, the public issued a message indicating the successful delivery. This step is optional.

Figure 7.5 Return to Merchant page tip Figure 7.6 User receives shipping notification

Note: Merchants can also bring the chain of goods pages into two-dimensional code, the user sweep open can complete the purchase payment.

Interactive details:

Here are the interactive details of the payment scenario, please read carefully and design the logic of the Merchant page:

(1) The user opens the Merchant webpage to purchase goods, initiates the payment, invokes the Getbrandwcpayrequest interface via JavaScript in the webpage, initiates the payment request, the user enters the payment process.

(2) When the user successfully pays the Click Finish button, the merchant's front end receives the JavaScript return value. Merchants can jump directly to the static page where payment is successful.

(3) The merchant backstage receives a payment success callback notification from the open platform, which marks the successful payment of the order.

Note:

(2) and (3) triggers are not guaranteed to follow strict timing. JS API return value as a flag to trigger the merchant webpage jump, but the merchant backstage should only receive the backstage payment successful callback notification, only then does the real payment successful processing.

Public number Payment-scenario introduction (from official documents)