Integration Testing

Test account login, third-party OAuth binding, and payment integration

Test Configuration

App ID -
Channel Key -
API Base URL
-
Login Status 🔴 Not Logged In
Enter the App ID to test, or load from your applications list
Select channel for OAuth to avoid ambiguity when app has multiple channels

Account Login

Third-Party Account Binding

Bound Accounts

No bound accounts. Login first to bind accounts.

Login or Bind Account

Account SDK V2 Demo

Test init, login, logout, is_logged_in, get_user_info, get_token, user_center. Uses App ID from Test Configuration.

Payment Testing

Webhook Callback Configuration
Webhook URL is loaded from the selected app's payment settings. Edit and save here, or in App Detail → Payment Config.
Recommended for this app (integration test)
—
Business webhook event types

Platform POSTs signed JSON to your webhook URL. Handle at least order.completed; use traceId with delivery logs when debugging.

Event When Your server
order.completed Payment succeeded Grant access / ship
order.refunded Order status refunded Revoke or shorten entitlement
subscription.renewed Web/store renewal succeeded Extend access until validUntil
subscription.deactivated Subscription ended Downgrade membership
subscription.grace_period Renewal payment failed Limit features; prompt payment update
subscription.expiring 7 / 1 days before validUntil In-app renewal reminder

WeChat subscription: OpenDev manages validity; each period is a separate Native payment (not WeChat auto-debit). Renewals extend validUntil from the current end date.

Idempotent on (orderId, event). Do not use test-callback in production.

Payment API Base URL
-
When multiple channel bindings exist, choose the config_key explicitly (e.g. premium_tier_products).

1. Select Product

2. Payment Metadata

Used to identify the buyer in the webhook callback payload

3. Initiate Checkout

4. Webhook Callback Verification

Detailed Information 

No data yet. Perform a login test to see detailed information.