Documentation release notes

28 October 2026

This edition introduces English guides for Payments, WeChat Login, and JPush.

Payments: target integration contract

The payment documentation describes the intended complete product, based on the customer contract 2.4.5 and subsequent documented changes. Some capabilities are still being implemented or activated. Confirm your application's enabled capabilities with NextAppMarket before sending live requests.

The target contract covers WeChat Pay, Alipay, Android HMS one-time purchases, refunds, webhooks, and financial reporting. Payment operations use the production environment. Historical sandbox examples have been retired from this edition.

The CN Payment API uses https://pay.appconnect.cn/payment/v1. Payment request examples and the downloadable Payment API schema use this production address. The US Business API uses the /api/business/v1 prefix; configure the complete Business API URL supplied by NextAppMarket. Its downloadable schema retains a non-routable example until that address is assigned.

The guides describe the full target behavior even where rollout is incomplete. Activation status does not change the meaning of an order state, a webhook signature, or an accepted asynchronous request.

Payments: app integration guides

The Payments navigation now follows the development sequence: backend setup, a dedicated guide for each payment entry, confirmation and fulfillment, refunds, recovery, and testing. The Payments API reference remains within Payments.

alipay_qr uses a signed Alipay cashier URL and returns redirect_url. The client encodes that URL as a QR code. This differs from WeChat Native's provider URI in qr_url.

At this review, the inspected CN adapter catalog implements Alipay App and hosted page checkout, with alipay_qr sharing the page-checkout mechanism. WeChat entries are currently disabled in that catalog; Alipay mobile web and HMS remain target integrations pending adapter completion/activation. Treat each application's activation as authoritative, rather than assuming that a published tutorial means an entry is available.

For HMS, this edition proposes a versioned huawei-iap-v1 JSON wrapper for the existing bounded evidence string and supplies an encoder. This is a documentation-level target design, not a confirmed live adapter format; implementation and a validated provider fixture are still required before production use. Alipay mobile web's activated adapter must establish its returned invocation kind and, if applicable, its form-rendering contract. The tutorials distinguish these target handoffs from verified availability.

The downloadable Node.js HTTP client is a server-side integration helper. Its request construction and failure handling are checked locally; native SDK snippets still require integration and verification in your own Android/iOS release builds with activated provider configurations.

WeChat Login and JPush

NextAppMarket supplies service credentials. These guides explain how to use those credentials in your app and backend. SDK installation and platform setup follow the providers' interfaces, with references on the relevant pages.

Use a pinned SDK release that you have validated with your application. Native snippets illustrate the integration points and do not constitute a complete sample application. Application-owned functions are identified beside each example.

Reading examples

All IDs, orders, secrets, and notification payloads in the examples are synthetic. A successful local example validates your handling of the example; it does not establish that a payment channel or app registration is active.