About Chainhook

To credit an on-chain payment, an app first has to notice it. Doing that yourself means an RPC provider for every chain, a process that reads each new block without skipping one, logic that waits for enough confirmations, and a way to catch up after an outage. None of it is specific to your product, and all of it has to keep running.

Chainhook runs that pipeline as a service. You create a webhook for an address, and we take care of scanning blocks, tracking confirmations, signing requests, and retrying failed deliveries. Your side of the integration is a single HTTP endpoint.

Chainhook is useful anywhere funds arriving at or leaving an address should trigger something in your system:

• Payment gateways and checkouts that confirm a customer has paid.
• Exchanges, wallets, and games that credit user deposits.
• Treasury and accounting tools that record movements on company wallets.
• Alert bots that post to Discord, Telegram, or Slack when a wallet moves funds.

Confirmed transfers only

We send a transfer once its block reaches the network's confirmation depth, so you aren't acting on blocks that could still be replaced. The depth for each network is listed in the API reference.

Signed, retried, and replayable

Every request is signed with HMAC-SHA256 and carries an ID that stays the same across retries. Failed deliveries are retried automatically, and you can replay any delivery from the dashboard or the API.

One payload for every chain

EVM chains, TRON, and Bitcoin send the same JSON shape, so one handler covers every network you use.

Monthly plans by volume

Each paid plan includes a monthly allowance of detections and a limit on active webhooks. Extra detections on any plan are paid from prepaid credit at a per-detection rate. Retries and replays are free, and every plan is listed in our pricing section.

For product questions, account help, or to request a network, email [email protected] or see the contact page.