Testing & Troubleshooting
Errors and Troubleshooting
Inspect top-level result_code/error_code, then biz_response.result_code/error_code/error_code_standard. These are common verified defaults; deployment mappings can change messages and standard codes. Do not branch on human-readable text.
Support Diagnostic Package
- Environment and devices: environment, merchant/store IDs, caller
terminal_snand target device. - Orders and transactions:
out_trade_no/client_sn,sn,tsnand refund ID. - Request and response: time with timezone, API path, HTTP status, both result-code layers and any returned trace identifier.
- Investigation: queries attempted and device symptoms.
Share redacted samples only; exclude keys, full card numbers and sensitive personal data. Use the technical-support channel provided during onboarding and keep the operation pending reconciliation.
Integration Tests and Launch
Run these cases in an authorized test environment and retain redacted evidence. Documentation verification does not mean they passed on actual devices/channels; arrange controlled integration tests where no simulator exists.
Before Launch
- Production merchant/store, target device and caller binding are consistent; currency and payment methods are enabled.
- Test/production endpoints, keys and callback domains are separated; secure key storage and valid TLS are in place.
- Payment, refund, notification, timeout and duplicate-operation tests have evidence; unknown outcomes have a human recovery path.
- Confirm rate limits, firmware, refund limits/permissions/fees, cancellation callbacks and reconciliation/settlement rules.
- Set monitoring and support ownership; complete the agreed small-value production validation before scaling up.
See Sources and Open Items for capability owners, required evidence and the original code verification scope.
