Developer Debugging
The four debugging tools let you make real calls from the page without writing code, verifying that your configuration and signatures are correct. Menu path: Developer Debugging.
The tools call with your real merchant and app configuration (not a sandbox simulator); the orders they create are real orders — remember to close or refund them after verification.
The Merchant-Panel Convenience: No Merchant Selection
Compared with the same tools on the admin panel, the biggest difference in the merchant panel is that the login session is automatically bound to the current merchant: the merchant field in payment debugging, gateway payment debugging and auth debugging is auto-filled and shown read-only — you don't need to (and can't) select another merchant; the app dropdown also lists only the current merchant's enabled apps. Self-testing is one step shorter than on the admin panel, with no risk of picking the wrong merchant.
Payment Debugging (Normal)
Simulates your system calling the unified payment API to initiate a payment, verifying the whole "credential config + signature + routing + channel merchant" chain:
- Set the merchant private key: fill in the merchant private key from API Credentials (stored only in this browser; re-enter it on another computer);
- Pick the routing mode:
- Follow channel routing: pick an app + pay method, resolved per Channel Routing — the first choice for verifying routing configuration;
- Specify directly: pick a channel merchant + capability, skipping routing — isolates issues with the channel merchant itself;
- Fill in the order: the order number can be generated with one click; the amount unit is cents; JSAPI / mini-program methods need an openId first (obtain it with Auth Debugging); in the barcode scenario, fill in the authCode and leave the pay method empty (auto-detected by the code prefix);
- Submit the payment: the request is signed locally in the browser and sent straight to the API; the result dialog renders per the returned form (redirect link / QR code / JSAPI parameters); business failures also show the error code.
Gateway Payment Debugging
Verifies the pre-order of gateway payment (cashier / aggregate scanning): pick gateway type → app → order info → submit; the result page gives the landing page link and the mini-program link (each with a QR code) — scan to experience the full cashier flow.
Signature Debugging
A standalone tool for troubleshooting signature problems, independent of merchant configuration:
| Tab | Input | Output |
|---|---|---|
| Signature generation | Parameter JSON to sign + RSA private key | String-to-sign + signature value |
| Signature verification | Parameter JSON (without sign) + signature value + RSA public key | Pass / fail |
When callback signature verification fails or the API reports a signature error, use it to compare whether both sides build the string-to-sign identically (usually a parameter-sorting or encoding difference).
Auth Debugging
Verifies that the OAuth authorization chain can obtain an openId (a prerequisite for JSAPI / mini-program payments): pick the auth type → generate an authorization link as a QR code → scan and authorize with your phone → the page polls every 3 seconds and shows the openId / userId on success (copy it into the openId field of payment debugging). The QR code becomes invalid once authorization succeeds — regenerate it for repeated tests.
Related Links
- Business System Integration — the full integration walkthrough and error reference
- API Signature — the canonical signature rules
- Developer Debugging (admin panel) — tool notes including platform-level app scenarios