Skip to content
Abhijeet Maharana, home

E-commerce and payments

E-commerce backends that never double-charge or lose an order

I build and fix the parts of an online store where bugs cost money: checkout, payments, webhooks, subscriptions and shipping. Contract at 20 to 30 hrs/week, starting with a paid 1 to 2 week sprint.

Problems I fix

The bugs that cost online stores money live in the seams between payments, orders and shipping.

What I build

System design principles

The system design habits behind the platform in my case study. Each one removes a class of bug.

Every webhook runs exactly once
Verify the signature, claim the event ID in Redis with SET NX, then act. A retry finds the claim and stops.
Money-moving actions take a lock
Refunds, cancellations and payouts take a short Redis lock with a random token, released by compare-and-delete, so one request can never free another's lock.
The server decides the price
Checkout recomputes every price on the server. A delayed job and a daily cron reconcile any order whose payment confirmation never arrived.
Slow work leaves the request path
Delayed tasks go to a queue. A message that fails three times moves to a dead-letter queue. Scheduled jobs run from a scheduler, not a timer that dies on deploy.
Limits and caches degrade gracefully
Rate limits use an atomic sliding window and fall back to memory if Redis is down. A cache outage slows reads but never breaks them.
Secrets and access tiers
Inputs are validated, secrets are encrypted and kept out of git, and every procedure is public, signed-in, employee or admin.
Ship small, roll back fast
One deploy at a time, a one-command rollback to any earlier commit, and alerts on errors and failed jobs.
Store, admin, appNext.js x3, ExpoWebhookspayments, carriers, chatAPIExpress 5 + tRPC, ZodRedisclaims, locks, limitsPostgresSupabase, Auth, StorageSQS + DLQdelayed tasks, 3 triesEventBridgecron via LambdatRPCverify, claim once
Apps call one typed API; providers' webhooks are verified and claimed once in Redis; slow and scheduled work runs through SQS and EventBridge

The project behind it

The full write-up: what I built, how it holds together and what I would change.

Independent build, 2025 to 2026

Full-Stack E-Commerce Platform, Checkout to Delivery

A payment can't be applied twice, and missed confirmations reconcile on their own.

Storefront, two payment gateways, subscriptions, referrals, four shipping carriers, an ops dashboard and a Claude-powered WhatsApp support agent. Exactly-once webhooks, Redis locks and queues on AWS.

  • TypeScript
  • Express
  • tRPC
  • Next.js
  • Expo
  • PostgreSQL

Is your checkout or order flow costing you money?

Tell me where it hurts. If it is a fit, we start with a short paid sprint on the worst of it.