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)
- Alipay Cross-Border (
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.
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:
Sample Request
Response Parameters
Refer to shared fields here:Common Response Parameters
Sample Response
Asynchronous Notification
After payment completion, QFPay will notify your backend vianotify_url.
- Notification format: Asynchronous Notifications
- Verify final status via API: Transaction Enquiry
Security Considerations
- Follow signature rules: Signature Generation
- Never expose secret keys in front-end code
- For errors: Status Codes
Additional References
- Official: Alipay H5 Authorisation Flow (Service Window)
- Official: Alipay Cashier / WAP Documentation

