Skip to main content
Rach monitors every WaaS and CaaS wallet 24/7. You don’t poll the chain or run indexers — when funds arrive at a monitored address, Rach detects the deposit, records it, and sends your backend a signed webhook. Monitoring runs on a dedicated always-on service, independent of your API traffic.

​
How it works

1

An address is monitored

WaaS: derive an address with enable_monitoring: true. CaaS: every provisioned wallet is monitored automatically.
2

Funds arrive on-chain

Rach’s monitor watches the relevant chains continuously and picks up the incoming transfer.
3

Deposit is recorded

The deposit is persisted (amount, token, tx hash, confirmations) and balances update.
4

You get a webhook

Rach POSTs a signed event to your configured URL so you can credit the customer.

​
WaaS monitoring

Turn monitoring on when you derive an address:
Monitored addresses report "monitored": true. Supported assets include native coins and USDT/USDC on the EVM chains. When a deposit confirms, Rach fires a wallet deposit webhook and the funds show up in GET /wallet/{id}/balances.
Enable your wallet webhook stream by configuring a URL with wallet_webhook_enabled: true (see Webhooks).

​
CaaS monitoring

CaaS smart-contract wallets are monitored from the moment they’re provisioned. An inbound transfer to a wallet you operate fires a transfer.received webhook — including transfers sent to a phone number that was never provisioned (Rach creates the wallet on the fly and notifies the recipient by SMS).

​
Reconciliation

If your endpoint was down, you won’t miss anything:
  • Rach retries failed deliveries.
  • Every delivery is recorded in a delivery ledger you can review.
  • You can always re-read the source of truth — GET /wallet/{id}/balances (WaaS) or GET /v1/users/balance (CaaS) — and reconcile by tx hash.
Next: wire up Webhooks to receive and verify these events.