Website and Telegram notifications

Notification center#

The badge counts unread account events. Messages are grouped by date; Load more retrieves older records. Visitors are asked to sign in.

Read state is stored on the server. Visible pages refresh automatically and open tabs synchronize read marks. Events newer than the last displayed message are not marked read along with older ones.

1. 1

   Select the bell in the top bar.

2. 2

   Choose all events or unread only.

3. 3

   Open the related page or mark a message as read.

4. 4

   Use Mark all as read for events already loaded.

Event categories#

Support and security are enabled for a new account; payment categories are selected by the user. The center shows saved events for enabled categories. Browser demo events are not real fund notifications.

Configuring delivery#

Tests are limited to three per account per hour. A test does not change a balance or create a payment. Queueing a message does not prove delivery.

1. 1

   Sign in with Telegram and open Account → Notifications.

2. 2

   Enable the desired categories and save.

3. 3

   Select Test delivery.

4. 4

   Check the center status and the bot’s private chat.

Delivery and read state are separate#

Delivery depends on Telegram availability and user permissions. A lost response can lead to a repeated message, but not a repeated financial operation.

If delivery fails, check that the bot is reachable and not blocked. Application notification retries also run in background jobs; service interactions can trigger other queued deliveries. Check the notification center for the current status.

Action confirmations#

The website shows a short notification after a completed save, new link or similar action. It closes automatically and stays longer when hovered or focused.

This confirms the interface action. It does not replace a confirmed financial status or create a payment record. Field errors stay beside the form.

Reading and marking through the API#

GET /api/notifications returns up to 30 account events, unreadCount and nextCursor. Pass nextCursor unchanged as cursor to load another page. unread=1 selects unread entries. Sort order is createdAt descending, then id descending.

PATCH /api/notifications/read accepts either 1–100 ids, or all:true with before set to the timestamp in milliseconds of the last displayed event. A session, Origin and X-CSRF-Token are required. The client cannot set the record owner.

The response contains updated, readAt and unreadCount. Reading an already-read event keeps its original readAt. Listing events does not mark them read; Telegram status and sentAt remain unchanged.

{
  "ids": ["ntf_46d94180-492e-4c28-b15f-a70049161a63"]
}

Bot commands#

Feature availability#

The notification center requires sign-in. Telegram messages are sent to the verified private bot chat. If delivery is unavailable, check bot permissions and the message status.

A payment or payout notification is based on a confirmed server event. Selecting a category changes delivery preferences, not transaction availability.