Skip to main content
WAP (H5) payment allows merchants to trigger wallet payment flows from mobile browsers such as Chrome or Safari.
For WAP/H5 payments, merchants should guide users to open the payment link in a mobile browser such as Chrome, Safari, or Edge. Due to restrictions in in-app browsers (for example WhatsApp, Facebook Messenger, or WeChat), QFPay cannot guarantee that these apps can invoke external wallet apps correctly.Example: Alipay cannot be automatically opened inside the WeChat in-app browser. This is a browser restriction beyond QFPay’s control.

​
HTTP Request

POST /trade/v1/payment You can find the corresponding pay_type for each wallet in the table below:
FPS 802010 uses pay_params and the platform-specific App/H5-to-App flow described in the FPS integration guide. It requires native app support; use that guide for request and response details rather than the generic pay_url flow below. For FPS QR code payments, use 802001 as listed under Web Payment.

​
Request Parameters

​
Response Parameters

Always confirm final payment status on your backend (for example via asynchronous notification and/or Transaction Enquiry), especially when respcd is not 0000.

​
Summary

  • Suitable for mobile browser environments (not recommended for in-app browsers inside social apps).
  • Set return_url and notify_url if you need user redirection and/or backend confirmation.
  • Use pay_url to redirect users (mobile) or display a QR code (desktop).
  • If respcd is not 0000, use asynchronous notification and/or Transaction Enquiry to confirm the final result.