How to receive cryptocurrency transaction notifications in Telegram

To receive Telegram messages about incoming wallet transfers, add the address to Cryptanio monitoring, connect the chat to your account, and select it in the relevant project’s notifications. You do not need your own bot or any programming. Funds arrive in the specified wallet, while Cryptanio reports detected transfers and changes in their state.

We will use a common scenario: you accept USDT and want to hear about new incoming payments without opening a blockchain explorer each time. You can use the same process to configure notifications for another supported asset.

What you need

You need a Cryptanio account with permission to change settings, Telegram, and a public wallet address on a network available for monitoring. For USDT, you also need the token identifier on the selected network. For tokens identified by a contract address, that address distinguishes the intended asset from other tokens with similar names. USD₮ identifiers are listed in Tether's official reference.

Monitoring does not require a private key or recovery phrase. You can receive notifications for a public address without connecting a wallet to sign transactions.

Select a project and add the address

Open Monitoring in your Cryptanio account and select the project that owns the wallet. A project keeps the addresses and notifications for a website or line of work together.

If the address has not been added, click Add addresses. Choose the network, paste the recipient's public address, and check that it belongs to that network. If useful, give it a clear name such as “Consultation payments”.

For USDT, select “One asset” and enter the supported token identifier for the selected network in “Asset”. The catalog also recognizes supported aliases such as USDT. An empty field means the network’s native coin, not USDT. Save the address and make sure monitoring is active.

For incoming-payment notifications only, enable “Incoming” and leave “Outgoing” off. Select both for both directions, if outgoing transfers are available for the chosen network and mode.

Open the project's notification settings

Open “Notifications” for the relevant project. Check its name so that events for the correct group of addresses reach the chat.

“Use account notification settings” determines whether the project uses the shared set of channels. “Account settings” opens those settings; changes affect inheriting projects. Turn inheritance off in the relevant project to use a separate set of recipients.

Choose custom settings if messages for this wallet need to go to a separate chat. After switching, check every recipient: the project starts using its own notification settings as a whole. A new connection is also added to shared account notifications. Changing one project does not stop delivery to this channel for other projects inheriting the shared settings; check those separately if needed.

Connect Telegram from your account

Open “Settings” → “Notifications” and the Telegram tab. Click “Connect Telegram”, then “Open Telegram”, and confirm starting the bot in Telegram. If the dashboard shows a command instead of a link, send the complete command to the bot.

The linking code can be used once and expires after 15 minutes. Do not send it to other people: it is intended to connect your chat. If it expires, obtain a new one from your account.

The bot confirms the connection to your account. /whoami shows which account the chat is connected to; it does not select a project. Return to the dashboard and click “Check connection”. Open the bot from the dashboard to use the link prepared for your connection.

Enable Telegram for the project

If the route is already present, go straight to event selection; use the plus button only when the route is absent. Return to “Notifications” for the project using its own settings. Find the connected chat in the Telegram card and click the plus button “Use … for this project”. Select “Confirmed payments” for ordinary incoming payments, or “Confirmed and rolled back” for confirmations and rollbacks. Route and event selections are saved when changed.

The connection determines the recipient; the route determines which project events to send there. There is no separate Telegram checkbox to enable for an address. In account settings, click “Test” beside the connection to queue a test message. It does not create a crypto transfer or test address monitoring.

For outgoing transfers, use “Choose event types” and include “Outgoing transfer confirmed”: the confirmed-payments policy does not include them automatically. The address rules must also allow that direction, and the network and asset must match the transfer.

Check a new transfer

Wait for the next incoming transfer after monitoring is active. If you send a small transfer yourself, allow for the network fee and check the address, network, and token beforehand.

Find the transaction in Events and match it with the Telegram message. Compare the amount, asset, network, and transaction identifier. The message includes the event status; some networks also provide a link to the transaction in an explorer.

A detected transfer and a confirmed transfer are different stages of the same transaction. Messages reporting state changes do not necessarily mean there were two payments. A rollback can also change the transaction state. Decide whether to fulfil a paid order based on confirmed payment and its current state.

If messages do not arrive

First check whether the transaction appears in “Events”. If not, check the network, asset, direction, and monitoring state. If the event exists, check the project, inheritance, selected chat, event policy, and whether the route or connection is paused. Delivery information is available in “Deliveries”.

If the bot was muted with /mute, send /unmute. Muting retains the link and does not stop events from being recorded. Also check whether the bot is blocked in Telegram and whether the application is allowed to show notifications on your phone.

View recent events in the dashboard: /last is unavailable for new account connections. /unlink disconnects the chat from the account and stops delivery through that connection, including for projects that used it. Address monitoring and other channels remain.