How to configure cryptocurrency transaction notifications in Discord

Cryptanio can send cryptocurrency transaction messages to a Discord text channel. Connect Discord in account settings, authorize messages to the selected channel, and add the connection to the relevant project’s notifications. Delivery uses an incoming webhook, but you do not need to copy its URL manually or write your own Discord bot.

This option suits a team that already works in Discord and wants to see incoming funds to its operational wallets in a separate channel. For example, you can create a project payments channel and give access to the people who reconcile incoming transfers.

Prepare the channel and permissions

You need a Cryptanio account with permission to change settings, active wallet monitoring, and a text channel in your Discord server. Creating a webhook requires Manage Webhooks permission in the relevant channel. This permission allows creating and changing these connections. Discord's channel permissions documentation describes it.

Decide beforehand who should see the messages. They can contain a wallet address, amount, network, and transaction identifier. For the team's internal incoming payments, use a channel with the appropriate membership.

Connect Discord from the dashboard

Open “Settings” → “Notifications” and the Discord tab. Click “Connect Discord”. Cryptanio redirects you to Discord: choose an available server and text channel, review the permissions, and authorize the connection.

After returning, check the server and channel in the connection row. Authorization creates a connection for sending messages; a normal channel link or server invitation cannot replace it. Discord’s official guide explains how webhooks work.

A secret webhook URL grants access to sending messages, so do not publish it in documents or screenshots. Cryptanio handles the data exchange for the connection described here. If the connect button is absent and Discord authorization is shown as unavailable, contact support about availability.

Select the project in Cryptanio

Open Monitoring, enter the project with the relevant addresses, and open its “Notifications”. Check the project name in the settings.

With “Use account notification settings” enabled, the project uses shared channels. “Account settings” opens the shared settings; changes affect inheriting projects. Turn inheritance off to choose this project’s recipients separately.

For a dedicated channel for this particular project, choose custom settings. Check the other recipients when switching: the custom set applies to the project's notifications 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.

Add a route and select events

If the route is already present, go straight to event selection; use the plus button only when the route is absent. Find the connection in the Discord card and click the plus button “Use … for this project”. Event selection appears after you add the route.

For incoming payments, select “Confirmed payments”. Use “Confirmed and rolled back” if you also need blockchain rollbacks. For a different set, use “Choose event types”. The Webhook card is for your application’s receiver, not for connecting Discord.

Route and event selections are saved when changed. To test the connection itself, open it in account settings and click “Test”. A queued message is not yet delivered: wait for the message in Discord. The test does not create a transaction or prove that monitoring works.

Check address monitoring rules

Return to the addresses in Monitoring. Make sure the required address is attached to this project and monitoring is active. There is no separate discord checkbox to enable for an address: the project route selects the events for the connection.

Address settings determine which transfers to monitor; the notification route determines which events to send to Discord. Incoming payments require “Incoming”. Spending requires “Outgoing” in the address rule and the corresponding event type in the route.

Check the asset. For incoming USDT, use its supported identifier on the selected network; the catalog also recognizes supported aliases. An empty asset field means the network’s native coin, which is a different asset.

For confirmed outgoing transfers, select “Outgoing transfer confirmed” through “Choose event types”: the confirmed-payments policy does not include them automatically. Outgoing monitoring must be supported for the selected network and mode.

Check delivery with a new transaction

Wait for a new transfer on an actively monitored address. If you test with a small amount yourself, allow for the fee and check the network and recipient before sending.

Find the transaction in Events, then open the selected Discord channel. Compare the amount, network, asset, and transaction identifier. Check that the intended team members can see the message.

One transaction can produce several messages as its state changes. Detecting a transfer and confirming it are different stages. When deciding whether to fulfil an order, check confirmed payment and its current state; the first message about a detected transaction does not complete payment verification.

What to check if there are no messages

If the transaction is absent from “Events”, check monitoring activity, the network, address, asset, and direction. If it is recorded, check the project, inheritance, event policy, and whether the route or connection is paused. Find the delivery for that event in “Deliveries”.

If Discord access has been revoked or the channel is unavailable, use “Reconnect” in connection settings and test again. If the message is in the channel but a member receives no alert, check their channel access and personal Discord settings.

To stop this project’s Discord messages, remove the connection route in its notifications. “Disconnect” in account settings disables the connection itself and its routes for every project that used it. Address monitoring and other channels remain.