Crypto deposit notifications for merchants: USDT & USDC on BSC and TRON
If you accept stablecoins, the hard part isn’t taking the payment — it’s knowing it arrived. Polling balances on a timer is slow and racy, and missing a deposit means a frustrated customer. A push-based deposit notification fixes that.
The pattern
Create a watch on each deposit address with a simple rule: direction in. Every time that address receives the token, SCMon delivers a signed webhook to your backend so you can credit the order immediately.
{
"chain": "bsc",
"token": "0x55d398326f99059ff775485246999027b3197955",
"address": "0xYourDepositAddress",
"rule": { "direction": "in", "minAmount": "1" },
"channel_type": "webhook",
"channel_target": "https://your-app.example.com/scmon"
}Reconcile safely
The webhook payload includes everything you need to match a deposit to an order:
amount— raw base units, exact (no floating point).from/counterparty— who paid.tx_hash+log_index— a unique key for idempotency. Store it and ignore duplicates, so a retried delivery never double-credits an order.
Because SCMon only emits confirmed transfers (15 confirmations on BSC, 25 on TRON), you won’t credit a deposit that later vanishes in a reorg.
Verify it’s really us
Every webhook is signed. Check the x-scmon-signature header — an HMAC of the body with your account secret — before trusting the request. The webhook docs include a copy-paste verification snippet.
No card, no lock-in
Billing is prepaid credits topped up in crypto, charged per delivered alert. That keeps deposit notifications cheap and predictable as your volume grows.
See the deposit-notifications use case for the bigger picture, or jump straight to the Quickstart.