Skip to main content
WeChat Pay is the wallet built into the WeChat app. Customers pay by scanning a QR code with WeChat, or by confirming the payment in the WeChat app on their phone. Payrails processes WeChat Pay through three payment service providers (PSPs). Each PSP shows the QR code in a different way, and the required request fields and the supported workflows differ. Pick a PSP below for its setup steps and request examples.

​
How a WeChat Pay payment works

WeChat Pay is a QR code payment method:
  1. The customer selects WeChat Pay at checkout.
  2. Payrails sends the payment to the PSP, and the PSP returns a QR code for the payment.
  3. The customer scans the QR code with the WeChat app and confirms the payment.
  4. Payrails receives the final result from the PSP and updates the payment.
With Checkout.com and Nuvei, Payrails returns a redirect to a page that shows the QR code. With Worldpay, there’s no redirect: the payment stays pending until Worldpay confirms it. Each payment is single-use: the customer confirms every payment on its own. Payrails captures WeChat Pay payments immediately, so a successful payment is final. To return funds, refund the payment.

​
Supported currencies and countries

The presentment currencies depend on the PSP:

​
Integrate WeChat Pay

Choose the PSP that processes WeChat Pay for you. Each guide covers the PSP-side setup, the Payrails configuration and the request fields that PSP requires.

Checkout.com

WeChat Pay via Checkout.com

Nuvei

WeChat Pay via Nuvei

Worldpay

WeChat Pay via Worldpay

​
Compare PSPs

​
Ways to integrate WeChat Pay

  • Payrails SDK: the Web SDK shows WeChat Pay when your workflow returns it as a payment option, and redirects the customer to the QR code page. To control how the redirect opens, listen for the actionRequired event.
  • Payrails API: call lookup payment options, then authorize with weChatPay as the paymentMethodCode. Each PSP guide lists the meta fields that PSP requires.
In both cases, confirm the final result through webhook notifications or the execution status. Don’t treat the customer’s return to your success URL as proof of payment.
Last modified on October 2, 2026