Subscription Fullstack

Covers the non-obvious parts of subscription billing: why your DB — not Stripe — is the access gate, the exact webhook events that matter and which to ignore, idempotency in webhook handlers, and the trial-to-paid transition edge cases most teams discover in production. Skips Stripe account setup — assumes keys exist and a product/price catalog is configured.

Discovery

Before writing anything, answer:

1. Billing provider: Stripe (assumed below), Paddle, Lemon Squeezy?
2. Plan structure: Single plan with tiers, or multiple distinct products?
3. Trial period: Free trial before payment, or paid from day one?
4. Cancellation behavior: Cancel immediately, or access until period end?
5. Seat-based or flat-rate: Per-user pricing changes metering logic significantly.
6. Customer portal: Use Stripe's hosted portal, or build custom upgrade/cancel UI?