←BACK TO TRIP LOG [2]
DISPATCH LOG: WB 03
FEATURED SPECIFICATION · 01/03
SYSTEM INTERFACE GALLERY [3 SCREENS]
OFFICIAL EVENT & PLATFORM CERTIFICATE
VERIFIED
Technical Associate & Engineering Team at InnovateX Connect
What needed to be engineered
Event ticketing requires resilient payment webhook handling to prevent double billing, handle network dropping, and issue tickets instantly.
Boundaries & non-negotiables
- [01]Zero double-charges: strict idempotency keys on every transaction.
- [02]Fast query lookups under simultaneous checkout rushes.
- [03]Separation of concerns between registration state and payment ledger.
System flow & boundary isolation
Next.js full-stack platform integrated with Razorpay signature verification, MongoDB atomic updates, and automated email confirmation pipelines.
Why this choice over alternatives
Idempotency Key Middleware
Persisted incoming webhook IDs before firing business logic, preventing replay attacks and race condition duplicate tickets.
Strict Payload Validation
Removed client-provided role fields entirely, locking all authorization decisions strictly behind server-side verified sessions.
05 — RETROSPECTIVE & WHAT I GOT WRONG
TODO(Srayash): document caching trade-offs during initial ticket release bursts.
Verified delivery & outcomes
Processed 750+ registrations, 170 captured payments, and 10 refunds with zero payment reconciliation failures.