Use the Payments Console
Open the application in NextAppMarket Console and select Payments → China Payments. The payments area is scoped to that application and the production environment.
Prepare the application
Check the application binding, accepted policies, payment entries, and readiness information. An application binding connects records across services; channel activation is a separate requirement. Resolve the configuration items reported for your application before making live requests.
Manage integration settings
| Area | What you manage |
|---|---|
| Credentials | Create, rotate, and revoke Business API keys within your authorized scopes. |
| Webhook endpoints | Configure the receiver, obtain signing-key details, verify the endpoint, and manage changes. |
| Webhook events | Inspect events and delivery attempts; request an explicit replay or delivery where available. |
| Contacts | Maintain the people and addresses used for payment communications. |
| Policies and notices | Review applicable policy details and record decisions where required. |
Use application permissions appropriate to the action. Read access does not grant permission to rotate keys, change receivers, or approve financial changes. Sensitive actions use the Console's authentication and two-factor checks.
Follow an order or refund
Search the relevant records, open the detail view, and compare the platform ID, current state, version, and amounts. Use refund eligibility to obtain an authoritative check before requesting a refund. Reporting data can be delayed; the displayed freshness matters when reconciling a recent payment.
Review funds and settlements
Inspect balances, release stages, financial entries, and settlement records by application and currency. Manage beneficiary details and settlement requests through their Console workflows. A bank submission, a confirmed bank result, and funds arriving in the recipient account are separate events.
Handle policy changes
Read the full policy and its changes before submitting a decision. The accepted revision identifies the exact policy content. Historical orders retain their applicable policy snapshots.
The target policy requires notice and explicit acceptance for unfavorable changes; silence does not replace acceptance. Follow the effective dates and decision requirements presented in Console for your account.
For the complete target scope and activation status, see Documentation release notes.