Chaingateway webhooks are HTTPS notifications that report blockchain events, such as deposits and token transfers, to your server. You register an address and a URL, Chaingateway watches the chain, and every delivery carries an HMAC signature. Failed notifications are listed and can be re-sent through the API.

Real-Time blockchain events delivered to your backend

Supporting major blockchains

Bitcoin, Ethereum, TRON, BNB Smart Chain, Polygon, Arbitrum.

Easy Setup

Quick and simple configuration for any use case.

Secure & Scalable

Built to handle high volumes with security in mind.

Developer Friendly

Comprehensive docs and support for seamless integration.

Launch with Confidence

How do instant payment notifications work?

Chaingateway sends an HTTP POST to your endpoint when a transaction matches a webhook you registered. The payload carries the sender, receiver, amount, token contract and transaction ID, so you can reconcile the payment without polling the chain.

You can track incoming and outgoing transactions and filter by address, token contract, token ID or type. A webhook needs a url and at least one of from or to.

1. Create a Webhook Receiver

Create a secure endpoint on your server to receive and process webhook notifications.

Show Receiver tutorial

Add a Webhook

Add a webhook to your application to receive real-time notifications for blockchain events.

Show API Docs

Get notified

Receive real-time notifications for blockchain events, ensuring you're always informed of important updates.

View Demo

Add Security

Secure your webhooks with signatures and authentication to prevent unauthorized access.

Security Guide
On-chain event a transfer reaches a watched address POST to your URL JSON payload + X-Signature header Your server verifies the HMAC, credits the payment Delivery not accepted? It is not re-sent automatically. Listed as failed; you re-send it with the retry call.
  1. Chaingateway watches the address you registered and reacts to matching transfers.
  2. Each notification is one HTTP POST. The X-Signature header is a Base64 HMAC SHA-256 over the transaction ID and your secret.
  3. Verify the signature, then credit the payment once per transaction ID, because a retry delivers the same event again.
From on-chain event to your database, including the manual retry path.

Which webhook features does Chaingateway include?

Webhooks cover Bitcoin, Ethereum, TRON, BNB Smart Chain, Polygon and Arbitrum. You can filter by address and token, review every notification in the dashboard and verify each delivery with its HMAC signature.

Browse Docs

Non-custodial delivery

Webhooks fire across Ethereum, Bitcoin, TRON, BSC, Polygon and Arbitrum without our system ever custodying your keys or funds.

Manual retry

Failed notifications can be retried on demand through the API.

Extensive Filtering

Easily filter webhooks to receive only the data you need.

Major Blockchain Support

We support most major blockchains for your convenience.

Logging

Our system logs all webhook events and displays them in a UI.

Retries

Failed deliveries land in your notifications list, ready to retry through the API whenever you choose.

Fast Performance

Our webhooks are designed for speed and reliability.

Secure Signing

All webhooks are securely signed to verify authenticity.

Responsive Support

Every plan includes email and chat support to help with your webhook integration.

User-Friendly

Our intuitive API makes managing your webhooks a breeze.

What can you build with event notifications?

Four patterns cover most uses: payout monitoring, incoming settlements, NFT ownership updates and cross-chain alerts.

High-value payout tracking

Use Case

Monitor outgoing transfers by filtering on your hot wallet via from + type (ETH/ERC20) so finance gets alerted before funds land.

Incoming settlements

Use Case

Watch your receiving address using to plus optional contractaddress to confirm deposits in seconds instead of waiting for polling.

NFT activity monitoring

Use Case

Subscribe to token_id + contractaddress (optionally filtered by from) to update ownership tables immediately after mints or transfers.

Cross-chain risk alerts

Use Case

Combine type + chain-specific webhooks to forward results from Bitcoin, Tron, Arbitrum, or Polygon to your compliance stack.

FAQ

Common Questions & Answers

Find out all the essential details about our platform and how it can serve your needs.

Chaingateway Webhooks is a service that allows you to receive real-time notifications for blockchain events, such as incoming and outgoing transactions, by sending POST requests to your specified endpoint whenever relevant events occur.

An Instant Payment Notification (IPN) is a message sent by Chaingateway to your specified endpoint whenever a relevant blockchain event occurs, such as an incoming or outgoing transaction. This allows you to receive real-time updates and take immediate action based on the event data.

To set up a webhook, you need to create a secure endpoint on your server that can receive POST requests. Then, you can use the Chaingateway dashboard or API to create a webhook and specify the URL of your endpoint along with any desired filters for the events you want to receive notifications for.

You must supply url (public endpoint) and at least one of from or to. Additional optional filter arguments are contractaddress, token_id, and type (ETH/ERC20/ERC721 for Ethereum, and similarly for other chains).

Each POST includes id, webhook_id, from, to, blocknumber, datetime, tokenid, type, contractaddress, txid, amount, and other bookkeeping fields so you have everything to reconcile payments.

Every delivery is signed with X-Signature (HMAC SHA-256 over txid + your secret, Base64). A notification your server does not accept is not sent again automatically: the API lists failed notifications (GET /webhooks/notifications/failed), and you trigger a new delivery for each one with POST /webhooks/notifications/{id}/retry.

No. The webhook service calls your public endpoint over the open internet—just ensure your firewall allows incoming traffic without IP whitelisting.

Use the Chaingateway dashboard to send test events to your endpoint, allowing you to verify that your handler processes the payload correctly before going live.

Use the X-Signature header to verify that incoming requests are genuinely from Chaingateway. This signature is generated using HMAC SHA-256 with your secret key, ensuring that only authorized events are processed by your endpoint.

Our support team is here to assist you with any questions or issues you may have. Please contact us through the support page on our website, and we will be happy to help you.

Still have questions?

We're here to provide clarity and assist with any queries you may have.

Enhance your Data Pipeline

Ready for real-time event notifications?

Stop polling and start receiving instant updates with Chaingateway Webhooks. Get notified of blockchain events in real-time, so you can react faster and build more responsive applications.