UnionPay

Updated: 8/2/26, 10:56:23 PM

Channel Overview

UnionPay (also known as Cloud QuickPass / Yunshanfu) is the all-channel payment service of China UnionPay, integrated directly via the UnionPay All-Channel Payment Platform (95516.com) ACP gateway. DaxPay supports the UnionPay direct gateway, covering QR scan, H5, and barcode (merchant-scan) scenarios.

UnionPay (Cloud QuickPass, channel union_pay) and UMS (UnionPay Merchant Services, channel ums_pay) are two independent channels — they differ in signature method, message format, gateway, and products. See Difference from UMS below.

Supported Payment Methods

• UnionPay QR (scan): Returns a QR link; the user scans it with the QuickPass App (union_qr)
• UnionPay H5: Redirects via a front-end form submission in a mobile browser (union_h5)
• UnionPay barcode (merchant-scan): The merchant scans the user's QuickPass barcode (union_barcode)

JSAPI not implemented

union_jsapi (UnionPay JSAPI) is enum-only and not yet implemented in the direct gateway channel. For UnionPay payments within an Official Account / mini-program, use an aggregate channel (e.g. Adapay, Lakala) instead.

Configuration

Add the UnionPay channel in the Admin panel under "Channel Management":

• Merchant ID
• PKCS12 private-key certificate (.pfx) and its password
• Intermediate certificate
• Root certificate

The UnionPay gateway uses RSA2 certificate signing (signMethod=01, SHA256withRSA). Messages are application/x-www-form-urlencoded (not JSON); all three certificates are required.

Callback Handling

• Supports both synchronous return and async notification
• Async notifications are form-urlencoded parameters; verify the signature with the UnionPay public-key certificate
• After verification, take queryId as the channel order number; refund callbacks reference the original transaction via origQryId
• The callback URL must be configured in the UnionPay merchant portal and be publicly accessible

Notes

• Gateway endpoints: sandbox test.95516.com / production 95516.com
• Keep the private-key certificate secure and renew it before expiry; an expired certificate breaks signing
• Merchant-scan barcodes are identified by the authCode prefix (UnionPay 62) and mapped to union_barcode before routing
• Some capabilities require separate activation with UnionPay

Difference from UMS (UnionPay Merchant Services)

UnionPay (Cloud QuickPass) and UMS are often confused, but they are entirely different channels:

Dimension	UnionPay (Cloud QuickPass)	UMS
Channel code	union_pay	ums_pay
Counterparty	China UnionPay All-Channel Platform (95516.com)	UnionPay Merchant Services Co. portal
Signature	RSA2 certificate signing (PKCS12 private key + intermediate/root certs)	HmacSHA256, no certificate (appKey + secretKey)
Message format	form-urlencoded	JSON
Products	Single product, 3 methods (QR / H5 / barcode)	6 products (C-scan-B / Official Account / APP / Mini-program / H5 / B-scan-C)

Which to choose

• UnionPay (Cloud QuickPass): Direct to the China UnionPay gateway, direct settlement. Best when you need native QuickPass QR / barcode payments.
• UMS: Acquiring via UnionPay Merchant Services; supports all-channel cashier including bank card / gateway / express pay, with richer onboarding options.

Docs for AI Assistants

LLM-friendly document formats for ChatGPT, Claude, Cursor and other AI tools to read and understand DaxPay docs.

llms.txt — Site index, page list with summaries for quick lookup
llms-full.txt — Full docs merged, complete content in one file for bulk AI input