Payment Platform Configuration
Platform configuration is site-wide global configuration. Menu path: System Management → System Configuration → Platform Configuration, with six tabs: Endpoint Configuration, Site Configuration, OSS Configuration, Mail Configuration, Sensitive Word Policy, MQTT Access.
Endpoint configuration directly affects the payment chain (must be configured before going live); the rest are optional — for what to pick per tab at go-live time, see the Go-Live Checklist.
Each tab can be opened directly by URL: append
?tab=to the address (values:url/website/oss/sensitive-word/mqtt), e.g./system/config/platform?tab=mqttopens MQTT Access — handy for bookmarks or pasting into a ticket.
Endpoint Configuration
Tells the system the external access URL of each panel — the foundation of payment callbacks and page redirects:
| Item | Purpose |
|---|---|
| Admin panel URL | Base URL of the operations admin panel; used to generate the callback URL for standard third-party login when client=admin |
| Merchant panel URL | Base URL of the merchant admin panel; must match the merchant frontend's access origin and be registered in the open-platform allowlist |
| Payment gateway frontend URL | URL of the cashier / gateway pages; payment page redirects depend on it; also the passthrough entry for third-party login callbacks of redirect-type platforms (Alipay / WeChat official account) |
| Backend API URL | Base API URL of the backend service; depended on by backend-initiated scenarios such as channel callback notifications; must be publicly reachable in production |
The "Check" button to the right of each URL verifies connectivity: the backend API URL goes through the deployment self-check probe (verifies the callback endpoint is reachable); the other URLs check HTTP reachability and show latency on success.
TIP
For the full addressing rules of each URL and placeholder tricks for local development, see From Deployment to First Payment - Step 2.
Site Configuration
Controls the system's external branding, mainly affecting outward-facing pages such as the login page and cashier:
| Item | Description |
|---|---|
| System name | System name displayed across the site |
| Logo / dark Logo | Site logo for the light and dark themes |
| Company full name / phone / email / WeChat | Contact information display |
| ICP filing info / link | MIIT ICP filing number and lookup link |
| Public security filing info / link | Public security network filing number and link |
| Payment & Clearing Association filing info / link | Payment and Clearing Association filing |
| Value-added telecom license info / link | Value-added telecom business license |
| Copyright | Copyright notice in the page footer |
When filing info is not configured, the related footer areas are hidden; functionality is unaffected.
OSS Configuration
Platform files (site assets, import/export files, etc.) all go through S3-compatible object storage, supporting MinIO, Aliyun OSS, Tencent COS, and more. It has many parameters (endpoint, path style, bucket policy, etc.) — see Storage Configuration for the full parameter guide, per-cloud examples, and troubleshooting.
Without OSS configured, features that rely on file upload are unavailable, but the core payment flow is unaffected.
Mail Configuration
SMTP mail service for scenarios such as password-recovery verification codes:
| Item | Description |
|---|---|
| SMTP server / port | The mail provider's SMTP address and port |
| Username / password | SMTP sender account credentials |
| Sender address / sender nickname | The sender shown in emails |
| Encryption | Default ssl |
| Timeout (seconds) | Default 10 seconds |
| Enabled | Master switch |
After saving, you can send a test email to verify. Without mail configured, the "recover password by email" channel is unavailable (the login page's recovery entry shows a notice); account-password login is unaffected.
Sensitive Word Policy
The master switch of sensitive-word detection. When on, entry fields such as merchant names and app names go through sensitive-word validation (the word list is maintained under "System Management → Sensitive Word Management → Word Library Management"; hit records are viewable in the same section). Generally keep it on by default.
MQTT Access
Access parameters for the device broadcast pipeline (device/terminal messaging such as Voice Broadcast (Virtual Device)). Ops-panel users copy the values from the Gateway Management - MQTT Access page:
| Item | Description |
|---|---|
| MQTT access URL | Full wss URL for devices, e.g. wss://mqtt.example.com; TLS is terminated at the outer gateway |
| Access account | The device access account on the broker, default app-device; subscribe-only on device topics |
| Access password | Must match the password of the app-device account on the broker; after changing either side, sync both — otherwise devices cannot connect |
No topic to fill in here
The device subscription topic is delivered by the activation API (slash form daxpay/device/audio/{deviceNo}); it is not configured on this page. Do not change it to the dot form on the client — on Artemis 2.33+ dots are escaped into a single-segment address, and the subscription is rejected by the ACL.
When it takes effect
The access parameters are delivered to the phone APP at device activation; after changing this configuration, already-activated devices do not update automatically — re-activate once in the APP to pick up the new values.
Related Sections
- Storage Configuration — OSS parameters in detail
- Go-Live Checklist — per-tab go-live decisions
- Configuration — deployment-level options (database, Redis, etc.)
- Voice Broadcast (Virtual Device) — deploying and using the device broadcast feature