I will build a reliable stripe or authorize net webhook integration


About this gig
Is your Stripe or Authorize.Net webhook firing twice, double-charging customers, sending duplicate emails, or processing the same order more than once? That is a missing idempotency layer.
I build webhook handlers that are exactly-once by EFFECT. Even if the same event arrives many times, out of order, or your server crashes mid-processing, the result happens once.
What you get:
- Event-id deduplication and an idempotency-key store
- Signature verification, so only genuine events are processed
- Retry-safe, out-of-order-safe handling
- Dead-letter and replay tooling (higher tiers)
- Automated tests, including a duplicate-replay test that proves the fix
Proof before you order: every technique is backed by a public, runnable demo on my GitHub. A chaos harness replays 1000 events and shows N events become 1 effect, with green CI.
Boundaries: I build the idempotency layer only. I never receive or store raw card data (that stays with your gateway), and I do not need live production keys. I use test-mode fixtures.
Tell me which gateway and which events are doubling up, and I will tell you how I would make them exactly-once.
Get to know Yihong Z.
Backend Reliability Engineer, Idempotent Webhooks, ETL and LLM Evals
- FromGermany
- Member sinceJun 2026
Languages
Chinese, English, German
FAQ
Will you touch my customers' card data?
No. I build only the idempotency and event-handling layer. Raw card data stays with Stripe or Authorize.Net, so PCI scope never reaches me.

