Build with NextAppMarket
Connect your application to payments, WeChat Login, and push notifications. Start with the service you need, then follow its integration guide through to a result you can verify.
| You want to… | Start here |
|---|---|
| Accept a payment in CNY | Payments quickstart |
| Let customers sign in with WeChat | WeChat Login |
| Send a notification to a device | JPush |
| Look up payment fields and endpoints | Payments API reference |
Before you begin
Have your NextAppMarket application details ready. NextAppMarket provides the credentials for WeChat Login and JPush. Use the credentials assigned to your application throughout these guides.
Keep the identifiers separate: your NextAppMarket application ID, WeChat AppID, and JPush AppKey identify different resources. Copy each value into the field that asks for it.
The payment guides describe the complete target integration. Read the documentation release notes for the contract edition and activation requirements before making live requests.
Find the right level of detail
Guides walk through a task and explain the decisions your application needs to make. API reference pages describe exact fields, authentication scopes, and responses. Troubleshooting pages start with the symptom you see and help you choose the next check.
Code samples use fictional IDs and environment variables for credentials. Replace those values with your application's configuration. The YOUR_BACKEND placeholder refers to infrastructure you operate.
Prepare your integration handoff
For mobile services, give NextAppMarket the application identifiers and build details needed to match the credentials to your release. For payments, confirm the enabled payment methods, Business API base URL, and the application ID authorized by each key. The CN Payment API is hosted at https://pay.appconnect.cn/payment/v1.
When asking for help, include the service, application ID, affected build or API version, time of the request, and a request or message ID. Keep passwords, private keys, and complete authorization headers out of the report.