Skip to main content

Use Cases

  • Payment initiated via mobile browsers (not inside native apps)
  • Suitable for mobile websites, WebApps, or flows where users open links in Safari/Chrome
  • Supported wallets:
    • Alipay Cross-Border (801107)
    • AlipayHK (801512)
    • Alipay Service Window H5 (800107) — requires user authorisation (openid)
Social apps (e.g. WeChat, Facebook Messenger) may block redirecting to external wallet apps.
For better conversion, guide users to open payment links in Safari, Chrome, or the system browser.

HTTP Request

Endpoint: POST /trade/v1/payment

PayType Reference


Request Parameters

For the full list of shared parameters, see:
Common Request Parameters
Below are Alipay WAP / H5 specific or commonly required fields:
Never hardcode or assume mchid is always required.
Include it only if QFPay has provided it for your store configuration.

Sample Request


Response Parameters

Refer to shared fields here:
Common Response Parameters

Sample Response


Asynchronous Notification

After payment completion, QFPay will notify your backend via notify_url.
Never rely solely on front-end redirection. Always verify the final result via backend notification and signature validation.

Security Considerations


Additional References

  • Official: Alipay H5 Authorisation Flow (Service Window)
  • Official: Alipay Cashier / WAP Documentation