Chinese Payment Providers Explained: A 2026 Integration Guide

China's payment market is not a list of interchangeable wallets. WeChat Pay and Alipay combine consumer wallets with merchant products; UnionPay connects card and bank payment infrastructure; banks and licensed institutions acquire merchants; aggregators or service providers can onboard sub-merchants. This guide is for developers choosing the legal merchant model and technical checkout.

What you need to know

• Choose the merchant and settlement model before choosing an SDK.
• Mainland and cross-border merchant products have different eligibility, currencies, documents and permitted scenarios.
• WeChat Pay, Alipay and UnionPay offer distinct app, web, QR and in-platform products.
• Fees and settlement depend on product, category, contract, acquirer and risk, so a single universal rate is not meaningful.
• External payments for iOS digital goods are restricted by Apple's current rules; physical goods and services are different.
• Payment success must be established server-to-server with verified, idempotent notifications—not from the client return screen.

Map the ecosystem

JD Pay and Douyin Pay can matter inside their ecosystems, but coverage should follow customers and channels, not a “support every wallet” goal.

Product types

WeChat Pay

WeChat Pay's merchant documentation covers products for Mini Programs, Official Account/JSAPI contexts, mobile apps, H5 and QR/in-store scenarios, subject to merchant eligibility. The Mini Program AppID and merchant account must be properly associated. Native QR can let the merchant display a code; scan/pay modes cover customer-presented or merchant-presented codes.

Alipay

Alipay Open Platform provides app, mobile-web, computer-web and face-to-face/QR products. The merchant application, app identifier, signing key/certificate and gateway notification configuration belong to the selected product. An app-payment SDK is therefore not automatically suitable for a web checkout.

UnionPay and banks

UnionPay's official product catalogue includes online gateway, WAP, QR and mobile checkout products. Its online checkout can launch Cloud QuickPass, bank apps and mobile-pay options. Direct bank acquiring can be useful for enterprise or specialised settlement but has separate integration and reconciliation.

Merchant eligibility

A mainland merchant normally supplies business registration, legal/authorised representative details, business bank account, contact, website/app and category evidence. The provider reviews the sales scenario, domain/app, fulfilment and prohibited/restricted industries.

Foreign companies should evaluate an official cross-border merchant product or a supported acquirer/partner. Cross-border does not mean “use any overseas account for domestic acquiring.” Confirm supported incorporation countries, settlement currency, bank account, product category, refund route and reserve/risk terms.

If a service provider uses a sub-merchant model, identify who contracts with the buyer, receives settlement, handles refunds, issues invoices and bears disputes. The regulated acquiring entity should always be visible in the arrangement.

Documents and platform review

Prepare incorporation and beneficial/authorised-person evidence, bank proof, domain/app ownership, privacy and refund policies, product screenshots, fulfilment description, customer support, category permits, APP/ICP filing information where relevant, and the binding between the platform AppID and merchant ID.

Requirements change by category and product. Ask the provider for the current onboarding checklist and contract. Fees, settlement timing and reserves should be quoted in writing rather than copied from a comparison blog.

Direct integration versus aggregator

Verify that the aggregator is authorised for the product and settlement path. Technical convenience does not cure an ineligible merchant model.

Technical integration pattern

1. Create the order on your server with an immutable merchant order ID, amount, currency, buyer context and expiry.
2. Call the provider API from the server and return only the client parameters needed to invoke the approved SDK/page.
3. Keep private keys and merchant certificates in a managed secret/HSM boundary and outside the distributed app.
4. Verify provider signatures and certificate serials on asynchronous notifications.
5. Process notifications idempotently; duplicate and out-of-order delivery is normal.
6. Query the provider when state is ambiguous rather than trusting the user's screenshot or redirect.
7. Fulfil only after authoritative success and record the provider transaction ID.
8. Implement partial/full refunds, close/cancel, reconciliation and exception queues.

Use separate sandbox/test and production credentials where offered. Some wallet journeys, bank routing and Mini Program bindings cannot be fully reproduced in a sandbox, so schedule controlled low-value production acceptance tests.

Webhooks, refunds and disputes

Return a fast acknowledgement after durable receipt, then process fulfilment asynchronously. Store the raw signed event, normalised state transitions and attempts. Protect against amount/currency mismatch and replay.

Refunds are not database edits. Submit through the provider, track their independent status and reconcile settlement files. Chargeback/dispute models differ among wallets, bank cards and cross-border acquiring; define evidence and customer-support owners.

Subscriptions and recurring payments

Recurring debit and auto-renewal are product-specific. User authorisation, category, cancellation, retry and advance notice rules differ. Retaining credentials or repeatedly creating ordinary transactions is not a substitute for an approved subscription product. Confirm whether the merchant and category are eligible for entrusted or automatic deduction.

iOS and digital goods

Apple's In-App Purchase rules govern digital content and functionality in iOS apps. A WeChat Pay or Alipay button is not a general substitute. Physical goods and real-world services are treated differently. Apple changed mainland storefront commission rates in March 2026; confirm current programme terms and review rules for your app.

Mini Program virtual goods and games also face WeChat-specific category/payment restrictions. Map what is sold, where consumed and which platform controls the checkout.

Invoicing and tax

A payment receipt is not automatically a Chinese fapiao (发票). Decide which legal entity supplies the product, recognises revenue and issues the applicable invoice. Cross-border withholding, VAT, permanent establishment and transfer pricing require professional tax advice. Payment-provider approval is not tax approval.

Recommended combinations

Frequently asked questions

Can a foreign company accept WeChat Pay or Alipay?

Potentially through supported cross-border merchant products or acquirers. Eligibility depends on incorporation, category, settlement and product.

Should we integrate both wallets?

For a broad mainland consumer checkout, often yes. Start with the wallet native to your channel—WeChat Pay inside a Mini Program—and add based on demand.

Can I trust the client success callback?

No. Verify server notification or query the provider, validate the signature and amount, and process idempotently.

Do international cards replace local wallets?

They help international customers and some visitors, but do not match local-wallet coverage for many mainland consumer journeys.

Conclusion

Select the lawful merchant and settlement path first. Then integrate the smallest provider set that covers the channel, using a server-owned state machine, verified webhooks and daily reconciliation. Add wallets only when their users or platform contexts justify the operational load.

This article is for general informational purposes and is not legal, tax, accounting, or regulatory advice.

Sources and official documentation

• WeChat Pay merchant documentation
• Alipay Open Platform documentation
• UnionPay product catalogue
• UnionPay online checkout
• UnionPay gateway payment
• Apple 2026 China storefront announcement
• MIIT mobile-app filing notice