I will integrate stripe subscription billing and webhooks into your app

M
muhammadanas093
M
muhammadanas093
Muhammad Anas

About this gig

Most teams do not lose money on pricing. They lose it on billing edge cases.


Failed payments nobody retries. Proration that overcharges annual customers. Webhooks that fail silently for weeks before anyone notices. Checkout is the easy part. What breaks is everything after it.


WHAT I BUILD


Stripe Checkout and subscription plans. Trials and trial to paid conversion. Upgrades and downgrades with correct proration. Customer portal for self serve plan changes and invoices. Usage based metering. Failed payment retry and dunning. Pricing and plan change screens too.


WHY IDEMPOTENCY MATTERS


Stripe retries delivery and can send events out of order. A handler that is not idempotent will eventually charge someone twice. I use an event log with a uniqueness constraint on event ID, so a repeated delivery cannot create a duplicate charge or subscription record.


STACK


Node.js, NestJS, Express, Next.js, TypeScript, PostgreSQL, MySQL, Redis, Prisma, TypeORM. I work in your existing codebase or build the billing layer from scratch.


Message me with your pricing model and stack before ordering and I will tell you which package fits.

Get to know Muhammad Anas

Muhammad Anas

Backend Developer, Stripe and AI Integration Specialist

  • FromPakistan
  • Member sinceSep 2026
  • Avg. response time1 hour
  • Languages

    Urdu, English
I build the parts of web applications where mistakes are expensive: subscription billing, APIs that hold up under load, real-time features, and AI capabilities added to products that already work. 2 years building production SaaS in TypeScript — Next.js, NestJS, PostgreSQL, Redis, Stripe. I've shipped multi-tenant platforms with role-based permissions, idempotent payment webhooks, and concurrency-safe transactions. I ask questions before writing code, and I tell you when an approach won't work instead of building it and letting you find out later.