Two cabinets, one platform
The admin panel is where a payment company runs its business: merchants and partners, payment settings, routing and providers, finance and reports, users and roles. The merchant cabinet is what its clients use: payments, balances, keys, team and support. Both are white-labelled and isolated per network, both speak English, Russian and Ukrainian, and both work on a phone when the person on duty is not at a desk.
Built for daily operations
- Find any payment in seconds by reference, order identifier, amount, card mask, e-mail or provider identifier; see its customer, card data masked, commissions, timeline, callbacks and the routing trace.
- Resend a webhook, change a status with a logged reason, refund in part or in full, create a manual transaction when a provider’s data came by e-mail.
- Onboard a merchant with its company data and KYB documents; review and approve; set fees, limits, methods and the webhook endpoint.
- Manage providers and terminals: accounts, currencies, limits, fees, and the routing rules in the flow builder, with versions and activation.
- Roles and direct grants, two-factor authentication, step-up checks for sensitive actions, an audit log of every change with the user, the time and the previous value.
- Support tickets with attachments and ratings, notifications in the cabinet and by mail, broadcasts to all merchants of a network.
A day in the admin panel
| Who | What they open | What they do |
|---|---|---|
| Support | A payment by its reference | Reads the trace, resends the webhook, answers the merchant’s ticket with the facts |
| Operations | Terminals and the flow builder | Moves traffic from an acquirer in maintenance, activates the new version, watches approval rates |
| Risk | A merchant’s payments by day | Sets limits, restricts a method, asks for documents |
| Finance | Balances and settlement requests | Approves settlements, exports the day in XLSX, checks the reserve |
| Administrator | Users and the audit log | Grants a role, enforces two-factor, reads who changed what |
What the merchant does in its cabinet
Watches payments arrive with their statuses and the callbacks it received; downloads reports for its accountants; manages API keys and the webhook endpoint; requests a settlement and sees the balance after fees and reserve; adds team members with their own roles; opens a ticket with a screenshot attached and rates the answer. Everything under the client’s brand, from the domain to the sender of the mail.
Support that sees the same screens
A merchant’s ticket opens next to the payment it is about: the support agent reads the trace, the callbacks and the webhook attempts without asking the merchant for screenshots, answers in the ticket with the facts, and the merchant rates the answer. Notifications tell the merchant when a settlement is approved, a document is requested or a webhook endpoint has been failing for an hour; broadcasts tell every merchant of a network about a maintenance window or a new method. The cabinet keeps the history, so a question asked in March is answered with the same facts in September.
And the numbers
Dashboards and analytics per merchant, method, provider and country; approval rates and the payments a cascade saved; reports in XLSX and CSV in the viewer’s language and time zone; balances, fees and settlements — on the finance page, described on its own product page.