← knowledge.oriz.in

Hookdeck

service serviceswebhookspaymentreliabilitytooling

Hookdeck

Role

Webhook reliability + queueing + replay layer between Razorpay and the Hono API Worker at api.oriz.in. Razorpay POSTs the webhook to Hookdeck; Hookdeck persists it, retries on failure, and forwards to the Worker.

Without Hookdeck, a Worker outage during a payment webhook drops the event — the user paid but the subscription never activates. With Hookdeck, the event sits in the queue until the Worker is back, then delivers cleanly.

Free tier

Card / subscription required?

NO. Hookdeck's free tier requires only an email-verified account. No payment method on file. (Paid plans exist but the free tier is generous enough for the family's expected webhook volume.)

Alternatives

Swap cost

Low. Razorpay webhook destination URL is just a string in the dashboard. Today it points at api.oriz.in/webhooks/razorpay; with Hookdeck it points at https://hkdk.events/<connection-id>, and Hookdeck forwards to api.oriz.in/webhooks/razorpay. To swap providers, change the Razorpay URL back (or to a Cloudflare Queues-fronted Worker). Code changes inside the Worker: zero.

Why this is our pick

The family is a single-developer, eventually-consistent project. A Worker can be down for legitimate reasons (deploy, edge incident, mistake). Without a queue layer, those minutes cost real revenue — Razorpay's retry policy is short and capped. Hookdeck's 100K/mo free covers the family's expected payment volume by orders of magnitude, and the dashboard's replay UI is worth the integration alone for debugging.

Cross-refs