How networks and tokens differ
Why an asset name and address alone do not identify a payment route.
Why an asset name and address alone do not identify a payment route.
Why a detected transfer and a completed payment have different states.
Connect Telegram to your account and choose the relevant project’s events for transfer notifications.
Connect Discord through account settings and choose project events for messages in your team’s channel.
Connect Slack to Cryptanio, route Monitoring events to the right channel, choose confirmed receipts, and check message delivery.
Bring public addresses from several wallets into Monitoring, choose networks, assets, and transfer directions, view combined events, and receive the notifications you need.
Where to copy a TXID in a wallet or on an exchange, how to check it in an explorer, and how it differs from an address, a withdrawal request and an invoice number. The ID alone does not prove that an order has been paid.
Find a notification in Deliveries, review the sending result, and queue another delivery of the same event if needed.
Set up separate Telegram, Discord, and Slack routes for one project’s confirmations, rollbacks, and outgoing transfers.
Set a minimum amount for one asset in Monitoring: base units, an inclusive threshold, and checks using artificial data.