Dashboard guide

What each section of the signed-in dashboard is for and how to get started.

Overview

After sign-in you land on Overview. It shows high-level stats: how many wallets you monitor, how many notifications were sent, and how many monitors are active. Below that you see recent notification activity with delivery status (sent, pending, failed).

Illustrative layout: overview counters and recent activity.

Wallet monitoring

Wallet Monitoring is where you add blockchain addresses and choose network, tokens, minimum amount, and optional webhook URL. You can pause or resume a monitor, edit tokens and thresholds, or remove a monitor. Addresses must match the selected network format.

Illustrative layout: table of monitors with address, network, tokens, and status.

Notifications

This page lists notification history with filters for status, channel, and network. Use it to confirm webhook or Telegram delivery and inspect payloads when debugging.

Credits

Credits power deliveries (for example webhooks and channel alerts). See your balance, buy packs, and review usage from the Credits section.

Payments (dashboard)

The Payments section lets you create crypto payment pages and attach receiving addresses per network. Use it from the dashboard after you sign in.

  1. Open Dashboard → Payments and click New payment page. Enter a name (for example, a store or campaign) and create the page.
  2. Open the page from the list. The dashboard shows counters for wallets in the pool, payments waiting, paid, and expired.
  3. Go to the Address pool tab and click Add wallet. Choose the blockchain network, paste the public receiving address for that network, and confirm. You can add multiple addresses; each row shows whether an address is free, in use for a payment, or disabled.
  4. Use the Payments tab to see incoming payment records for this page: status, linked wallet, webhook payload preview, and creation time.
  5. Share or embed the public payment page link where customers should pay; incoming transfers to your pool addresses are tracked according to your service settings.

Addresses must be valid for the selected network. Only add wallets you control.

API keys & webhooks

Create API keys for server-to-server calls. The first time you create a key, a webhook signing secret (whsec_…) may be shown once—store it safely. You can disable or rotate keys from the same page.

Illustrative layout: masked API key and webhook secret area.

Full REST API reference →