Reliable Crypto Payment Webhook Development

You integrate crypto payments, but the blockchain cannot notify your backend on its own. You have to poll the node every 12 seconds — that's 7200 RPC requests per hour per address. For 1000 active users, the load grows to 7.2 million requests per hour, costing tens of thousands of dollars monthly and causing delays of up to 30 seconds. During network congestion, like a popular mint, you are guaranteed to lose transactions.

Webhook solves the problem: blockchain monitoring itself sends an HTTP request to your server when an event occurs. Latency drops to 2–5 seconds, backend load falls by 95%. We have built dozens of such systems and know how to make them reliable.

Why webhook is better than polling for crypto payments?

Polling means constant RPC requests to the node. Each request costs money and creates load. Webhook is a push model: you get a notification as soon as the transaction is included in a block. Latency is minimal, server load drops significantly. For high-load projects, this is the only viable option. For example, one of our client exchanges reduced infrastructure costs by 40% and decreased average payment confirmation time from 15 to 3 seconds after switching from polling to webhook.

How we build a webhook notification system

We use a proven architecture: blockchain monitoring → webhook dispatcher → your task queue. Monitoring can be implemented through third-party services (Alchemy Notify, Moralis Streams, QuickNode Streams) or your own node listener. We usually choose Alchemy for simplicity and reliability. Here's an example of creating a webhook:

// Creating a webhook via Alchemy API const response = await fetch('https://dashboard.alchemy.com/api/create-webhook', { method: 'POST', headers: { 'X-Alchemy-Token': process.env.ALCHEMY_AUTH_TOKEN!, 'Content-Type': 'application/json', }, body: JSON.stringify({ network: 'ETH_MAINNET', webhook_type: 'ADDRESS_ACTIVITY', webhook_url: 'https://yourapp.com/webhooks/crypto', addresses: ['0xYourAddress'], }), }) 

How to ensure idempotent webhook processing?

Webhook providers guarantee at-least-once delivery. Your handler must be idempotent — repeated notifications must not duplicate payments. We use INSERT ... ON CONFLICT DO NOTHING:

async function processPaymentWebhook(txHash: string, address: string, amountWei: bigint) { const result = await db.query(` INSERT INTO processed_webhooks (tx_hash, processed_at) VALUES ($1, NOW()) ON CONFLICT (tx_hash) DO NOTHING RETURNING id `, [txHash]) if (result.rowCount === 0) { return // already processed } await updatePaymentStatus(address, amountWei, txHash) } 

Retry mechanism for outgoing webhooks

If your service itself notifies clients via webhook, you need a reliable retry mechanism. We use exponential backoff with 10 attempts and persistence in a dead letter queue. Example handler:

interface WebhookDelivery { id: string url: string payload: object attempt: number nextRetryAt: Date } async function deliverWebhook(delivery: WebhookDelivery): Promise<void> { try { const res = await fetch(delivery.url, { method: 'POST', headers: { 'Content-Type': 'application/json', 'X-Webhook-Signature': signPayload(delivery.payload), 'X-Webhook-ID': delivery.id, 'X-Webhook-Attempt': String(delivery.attempt), }, body: JSON.stringify(delivery.payload), signal: AbortSignal.timeout(10_000), }) if (!res.ok) { throw new Error(`HTTP ${res.status}`) } await db.markDelivered(delivery.id) } catch (err) { const nextAttempt = delivery.attempt + 1 if (nextAttempt > 10) { await db.markFailed(delivery.id, String(err)) return } const delayMs = Math.min(30_000 * Math.pow(2, nextAttempt - 1), 3_600_000) await db.scheduleRetry(delivery.id, nextAttempt, new Date(Date.now() + delayMs)) } } 

Retry scheme: 10 attempts with exponential backoff are sufficient for 99.7% deliveries. Final failure — notify developers via PagerDuty or Telegram, save to dead letter queue.

Comparison of blockchain monitoring providers

We recommend Alchemy for starting — it is better documented and stable. We use it in about 70% of projects.

Typical webhook events and their handling

This table helps developers quickly understand what data arrives and what to do with it.

What to do if the webhook handler goes down?

Blockchain providers do not store events indefinitely. If your endpoint goes down, you risk losing notifications. Therefore, we design the system with a task queue (RabbitMQ, Redis, or Kafka) right after the endpoint. If processing fails, the queue retains the message and retries. Additionally, we set up monitoring: if the queue grows beyond 1000 unprocessed tasks, an alert is sent. This ensures no payment is lost even in case of a database or network failure.

Development process

1. Requirements analysis: event types, number of addresses, SLA.
2. Architecture design: provider selection, data schema, retry policy.
3. Implementation of webhook endpoint with signature verification and queue.
4. Development of idempotent handler and retry mechanism.
5. Integration with your payment system.
6. Testing on testnet (Goerli, Sepolia).
7. Deployment and monitoring (Grafana + Prometheus).

What is included

• Webhook API documentation
• Source code with comments
• Deployment guide
• Test environment
• One month of post-launch support

Timeline and pricing

A basic webhook endpoint with verification and queue can be done in 1 day. A full system with retry, dead letter queue, and dashboard takes 2–3 days. Pricing is tailored individually after analysis. We will evaluate your case within 24 hours — just reach out. Get a consultation from an engineer with 10 years of experience in blockchain development.

Typical mistakes

• Not verifying the signature — anyone can send a fake webhook.
• Responding with 200 after queuing — blocks the queue, reduces throughput.
• Not using idempotency — double charging a payment.
• Ignoring retry for outgoing webhooks — data loss.

Our team guarantees reliability and security for every solution. We have implemented over 50 payment system integrations using webhooks. If you need a reliable webhook notification system — contact us.