Software EngineeringEngineeringPlatinum

Designing subscription billing systems for SaaS with complex pricing tiers.

Subscription Billing Architect

Stripe, Chargebee, SaaS Billing

expertv5.0

Best for

▸Design subscription billing architecture for SaaS platforms with complex pricing tiers
▸Implement Stripe/Chargebee webhook processing with idempotent payment state management
▸Build dunning workflows to recover 50-70% of failed recurring payments
▸Design proration logic for mid-cycle plan upgrades and downgrades

What you'll get

▸Complete subscription state machine with 15+ states (trial, active, past_due, canceled) including transition triggers and business logic
▸Webhook processing architecture with idempotency patterns, event deduplication, and reconciliation job specifications
▸Multi-stage dunning strategy with specific retry timing (days 1, 3, 5, 7), customer communication templates, and success rate benchmarks

Expects

Clear business model details (pricing tiers, usage-based components, trial periods) and technical constraints (existing payment stack, compliance requirements, scale expectations).

Returns

Technical architecture diagrams, state machine definitions, webhook handling code patterns, and revenue recognition data schemas with specific implementation guidance for subscription lifecycle management.

What's inside

“You are a Senior Subscription Billing Architect. You design recurring revenue systems that recover 60-75% of failed payments, handle multi-currency at scale, and never lose money to rounding errors or state divergence. - **Money-first infrastructure**: Treat every amount as integers (cents, never fl...”

Covers

What You Do DifferentlyMethodologyWatch For

Not designed for ↓

×One-time payment processing or e-commerce checkout flows
×Accounting software implementation or financial reporting systems
×Payment gateway selection without subscription-specific requirements
×Simple membership sites with fixed monthly fees and no plan changes

SupaScore

88.83▼

Research Quality (15%)

8.85

Prompt Engineering (25%)

9.2

Practical Utility (15%)

8.65

Completeness (10%)

8.85

User Satisfaction (20%)

8.8

Decision Usefulness (15%)

8.75

Evidence Policy

Standard: no explicit evidence policy.

subscription-billingpayment-processingstripedunningprorationrevenue-recognitionsaas-billingrecurring-paymentspci-compliancewebhooksmonetization

Research Foundation: 7 sources (3 official docs, 1 industry frameworks, 2 web, 1 books)

This skill was developed through independent research and synthesis. SupaSkills is not affiliated with or endorsed by any cited author or organisation.