Notifications

Notifications are the exchanger’s nervous system: the administrator learns about orders, failures, and risks in real time, and clients learn about the movement of their money. This page covers channels, events, and recommended setup.

Channels

Channel	Audience	Typical use
Telegram	Administrator and operators	New orders, payout errors, AML hits, balances — anything requiring fast reaction
E-mail	Clients and administrator	Order statuses, confirmations, service letters
SMS	Clients	Critical confirmations (verification codes, large operations) — via an SMS gateway

Administrator notifications

The minimum set of events that should arrive instantly (we recommend Telegram):

new_order              # new order created
order_paid             # order paid, payment credited
payout_sent            # auto-payout executed
payout_error           # auto-payout error (requires review)
manual_review_queue    # order entered the manual moderation queue
aml_alert              # AML hit / sanctions match
low_merchant_balance   # payout merchant balance below threshold
low_reserve            # direction reserve below threshold
aml_provider_balance   # AML provider balance running low
system_error           # integration/node/merchant failure
Setup: in the admin panel, open the notifications section, link a Telegram account (or an operator group chat), and enable the events you need. For shift-based operator work, use a shared chat with a pinned reaction playbook for each event type.

Client notifications

The client receives letters and messages about order statuses:

Order created — payment details, amount, rate-fixing timer.
Payment received — crediting and network confirmation count.
Payout sent — transaction hash.
Order completed / cancelled — outcome, cancellation reason, refund instructions.

Letters are sent from your domain and under your brand (white-label). Template texts are edited in the panel: make sure every template explains to the client what is happening with their money and what to do next.

Recommendations

Don’t fully disable “noisy” events — payout_sent on every order quickly reveals anomalies (payouts at odd hours, unusual amounts).
Separate channels by criticality: instant reaction — Telegram; archive and legally significant correspondence — e-mail.
SMS — sparingly: codes and critical confirmations only; every message is billed by the gateway.
Check e-mail deliverability: configure SPF/DKIM for the sending domain, otherwise order statuses will land in spam and generate support requests.

See also