From Zero to Production: Building Enterprise Billing in 6 Weeks

The existing codebase had no local testing environment for billing operations. There was no way to test webhook events, billing failures, edge cases, or subscription lifecycle events without affecting production data. This made development extremely risky and slow.

Rebuilt the entire testing infrastructure from the ground up. Created a comprehensive test environment supporting Stripe test mode, webhook event simulation, failure scenario testing, and edge case validation. Implemented automated testing workflows for subscription changes, location additions/removals, and trial conversions. This transformed development from risky production testing to safe, iterative local development.

Users frequently change their billing setup-adding locations, removing locations, upgrading tiers, downgrading tiers, or switching between monthly and annual billing. Each operation required different Stripe schedule logic: some needed schedule cancellation, others needed modification, and some required creating new schedules entirely. Handling all permutations correctly while avoiding billing gaps or double-charges was complex.

Implemented a sophisticated schedule management system that determines the correct operation based on current state and desired state. Created decision trees for upgrade/downgrade scenarios, location quantity changes, and billing frequency switches. Used Stripe Schedules API to handle future-dated changes seamlessly, ensuring prorated billing calculations and preventing edge cases like overlapping subscriptions or missed billing cycles.

The pricing model charges per location-one location on Free plan, unlimited locations on paid plans with each location billed separately. This required tracking location count as a Stripe subscription quantity, handling additions/removals mid-cycle with proper proration, and preventing billing errors when users rapidly add/remove locations.

Leveraged Stripe's quantity-based subscription model where each subscription item quantity represents the number of active locations. Built an internal API that syncs location count to Stripe in real-time, automatically updating subscription quantities and triggering prorated billing adjustments. Implemented atomic operations to prevent race conditions when multiple locations are added/removed simultaneously.

The application needed to instantly enable/disable features based on subscription tier (e.g., POS integrations only on Pro, unlimited reporting on Essential+). Feature access had to reflect Stripe subscription state in real-time, handling scenarios like payment failures, trial expirations, downgrades, and cancellations without manual intervention.

Built an internal feature gating API that queries Stripe subscription status as the source of truth. Webhook automation updates local database state when subscription events occur (payment success/failure, trial end, cancellation). Application checks subscription tier before rendering premium features, with graceful fallbacks and upgrade prompts for locked features. This ensures feature access always matches billing state with zero manual reconciliation.

The Professional tier offers a 30-day free trial to encourage adoption, but the platform also wanted to incentivize early trial upgrades with discounts. Managing trial states, preventing trial abuse, handling trial-to-paid conversions, and applying early upgrade discounts required careful coordination between Stripe and internal systems.

Implemented trial management using Stripe's native trial period functionality combined with an internal API tracking trial status. Created early upgrade discount logic that applies promotional pricing when users convert before trial expiration. Built webhook handlers for trial_will_end and trial_end events to notify users and handle automatic conversions. Used Stripe Customer metadata to prevent users from creating multiple trial accounts.