App Management
An app (appId) is the invocation and configuration isolation unit under a merchant: unipay requests are attributed per app, and configurations such as channel routing, gateway payment, and the cashier all hang at the app level. Menu path: Merchant Center → Payment Config → App Management.
The app configuration model is exactly the same as the admin panel's Application Configuration (the admin panel manages the same data on the merchant's behalf from its merchant workbench); this page describes it from the merchant panel self-service perspective.
App List
The app list is a card grid (not a table): each card shows the app name, appId, and enable status; the default app is pinned to the top with a "Default" tag; click a card to enter that app's App Workbench.
Add / Edit has only three fields: app name, status, and the default app switch (changeable only in edit mode). The appId is generated automatically by the system (starting with A) and cannot be changed after creation.
Default App Rules
- The merchant's first app is automatically set as the default at creation; there is at most one default app;
- A unipay request without an appId falls back to the default app; an explicit appId routes by the given value;
- A warning "there are apps but no default app" appears at the top of the list — in that state, orders without an appId will fail; just set a default.
| Scenario | Consequence |
|---|---|
| Disable the default app | Orders that specify no appId are blocked (the page prompts a confirmation) |
| Delete the default app | Forbidden — transfer the default first, then delete |
| Delete an app | Dangerous operation; requires manually typing the app name to confirm |
App Workbench
Enter from an app card; the tab title is "{app name} · App Config", and the tiles are in two groups:
Payment Config (each card has independent permission control):
| Card | Function | See |
|---|---|---|
| Channel Routing | Decide which channel merchant each pay method of this app goes through | App Payment Config |
| Gateway Payment Config | Routing depth of QR plates / aggregate pay under each client environment | App Payment Config |
| Cashier Config | Which pay methods the cashier page displays in each environment | App Payment Config |
| Async Notify Config | Business event callback URL and subscribed events | Under development, see the next section |
| EasyPay Config | EasyPay V1/V2 protocol compatibility integration | EasyPay Plugin |
App Management: edit basic info, set / unset the default app (with confirmation), delete the app (red card, strong confirmation).
Async Notify Config (Under Development)
In the current version this UI is under development; the workbench card carries a badge and is not clickable. Once available, it will support configuring a callback URL (HTTP) or an MQ subscription (a topic isolated per app) and checking the events to subscribe. For now, callback troubleshooting can start from the Merchant Callback Push page.
Related Links
- App Payment Config: details of channel routing / gateway payment config / cashier config
- Application Configuration (admin panel): the admin manage-on-behalf view of the same configuration
- From Deployment to the First Payment: where apps sit in the integration main line