Risk reduction: password + 2FA protect access to funds and settings.
Faster reactions: notifications help you learn about issues without constantly monitoring the dashboard.
Action audit: sign-in history helps quickly detect suspicious activity.
Team transparency: name and avatar make it easy to identify who performed actions in the system.
Access: password change, 2FA settings.
Notifications: Telegram / custom Endpoint, rules and subscriptions.
Sign-in history: a list of sign-ins with details (date/time, IP, device).
Sign out: end session / switch account.
1.
In the 2FA block, enable the Telegram checkbox.
2.
Get a confirmation code and send it to the Telegram bot (as prompted by the UI).
3.
After linking, you will receive the confirmation/code in Telegram during sign-in.
Payments: manual status changes, adjustment transactions, “unknown orders”.
Merchants: merchant changes, endpoint changes, key rotations, flow changes (routing/cascading), channel changes.
Reconciliations: runs in the dashboard/bot.
Fees: fee and rule changes.
Team: team settings changes, user changes, time zone changes.
Limits: creating/deleting limits, limit triggers.
Orders Count — change in order volume vs the previous period.
Conversion — change in Created → Success conversion.
Stuck Orders — orders processed longer than the expected time.
Payment Status — notifications for selected statuses/events.
1.
Open the Orders Count block and click Add rule.
2.
Choose the tracking level: merchant / flow / channel.
3.
Set a threshold (e.g., -5% or +5%).
4.
Select the comparison period (day-to-day / hour-to-hour).
Telegram is linked and the bot is not blocked;
the required checkboxes/rules are enabled;
the Endpoint is reachable and responds to POST (2xx recommended);
events really occur (for alerts — the threshold and period conditions are met).