Plans, payment methods, invoicing, and PCI scope live in the billing provider — hosted fields keep card data off your servers, and rebuilding proration is a rite of passage nobody should complete.
Your product must ask 'what can this account do right now' — a clean entitlements service driven by subscription state, handling trials, grace periods, seat counts, and plan changes without scattering billing logic through features.
Dunning flows (retry schedules, update-card prompts), webhook processing with idempotency, and reconciliation between provider truth and your database — involuntary churn hides here.
Sales tax/VAT automation, upgrade/downgrade proration policy, refunds and credits, and revenue-recognition exports for finance — decided deliberately, before the auditor or the angry invoice arrives.
Skipping the discipline this article describes until an incident, audit, or stalled project forces it — every practice above is cheaper adopted early than retrofitted under pressure.
Let's discuss how we can help you with how to implement subscription billing.