Subscription Management App Development

Subscription management is a harder engineering problem than it appears. The challenge is not generating recurring invoices: it is correctly modelling plan changes mid-cycle (upgrade, downgrade, pause, add-on), propagating those changes to the billing engine, entitlement system, and analytics layer consistently, and recovering revenue from failed payments without churning customers who would otherwise stay.

Scrums.com builds subscription billing engines, dunning systems, entitlement platforms, and analytics layers for SaaS companies that have outgrown Stripe Billing's native capabilities and for companies building subscription management as their core product. Our teams have worked on subscription platforms handling flat, per-seat, tiered, volume, metered, and hybrid pricing models across B2B SaaS, D2C subscription commerce, and embedded subscription billing within vertical SaaS platforms.

Subscription Platform Architecture

The components that most subscription builds get wrong are mid-cycle change proration, dunning sequence calibration, and entitlement consistency across billing and product layers.

Subscription Lifecycle State Machine

Subscriptions are modelled as a state machine with defined valid transitions: Trial, Active, Past Due, Paused, Cancelled, Reactivated. Invalid transitions (e.g. reactivating a subscription that requires payment method re-entry without triggering SCA) are rejected at the API layer. Every state change is recorded with timestamp, actor, trigger event, and previous state, creating an immutable audit trail that supports revenue recognition calculations and customer support review.

Pricing Model Engine

Pricing models are stored as configuration data, not code: flat monthly/annual, per-seat (licensed user count), tiered (first N units at rate A, next M units at rate B), volume (all units priced at the tier rate for the total quantity), metered (rate applied to usage aggregated from the metering layer), and hybrid combinations. Plan changes are evaluated against the pricing engine at the time of the change, not at renewal, so proration calculations are deterministic and auditable. The engine supports promotional pricing, coupons (percentage, fixed, duration-limited), and free trial periods with configurable trial-to-paid conversion logic.

Dunning and Payment Recovery

Dunning sequences are calibrated by payment method type (card vs direct debit have different retry windows), failure code (hard decline vs insufficient funds vs expired card require different responses), and customer segment (enterprise customers on manual outreach paths, SME/consumer on automated sequences). Card expiry is handled proactively via Account Updater (Visa, Mastercard) and Stripe Card Updates before the renewal date, not reactively after a failed charge. Permanent failure codes trigger immediate cancellation; soft failures trigger the retry sequence with adjustable cadence.

Entitlement Management

Entitlements define what features and usage limits apply to a subscription at a given point in time. The entitlement service evaluates the current subscription state, plan configuration, and any active add-ons to produce a feature access decision. Plan changes take effect immediately or at next renewal period depending on the change type (upgrades are typically immediate, downgrades at period end), and the entitlement service reflects this without a polling delay. Entitlement decisions are cached per session with a short TTL and invalidated on subscription state change events published to Kafka.

Types of Subscription Platforms We Build

• SaaS subscription billing engine. Custom pricing model engine replacing Stripe Billing for complex pricing (hybrid metered + per-seat + committed spend), with full control over proration logic, dunning sequences, and revenue recognition data feeds.
• Usage-based subscription metering platform. Event ingestion at scale (Kafka idempotent consumers), aggregation by billing period (ClickHouse/BigQuery), rate application engine, and usage-to-invoice translation for API, compute, or seat-based SaaS products.
• Subscription box commerce platform. SKU allocation per subscriber box, subscription preference management, fulfilment schedule orchestration, skip/pause/swap workflows, and churn prediction signals fed from engagement data.
• Multi-tier plan and feature entitlement system. Plan configuration management, entitlement rule engine, feature flag integration (LaunchDarkly, Unleash), and usage limit enforcement at API gateway level without hardcoding limits in application logic.
• Embedded subscription billing for vertical SaaS. Multi-tenant subscription management where the SaaS platform's customers each have their own subscriber base; per-tenant plan configuration, billing, and revenue reporting with platform-level revenue share calculation.

Scrums.com's mobile app development teams build across the full range of subscription management platform types. Start a conversation about your subscription management platform build.

Technology Stack for Subscription Management Platforms

• Billing engine. Java Spring Boot or Node.js (TypeScript) API; pricing model and proration logic as config data evaluated at runtime; all billing events immutably logged to PostgreSQL ledger
• Metering layer. Kafka idempotent event ingestion; ClickHouse or BigQuery for aggregation with configurable billing period windows; Redis for real-time usage counters against soft limits
• Payment orchestration. Stripe (card, ACH, SEPA Direct Debit) + GoCardless (BACS, SEPA Core); Stripe Radar for fraud scoring on new card additions; Account Updater (Visa/Mastercard card-on-file update) for proactive expiry handling
• SCA/3DS handling. Stripe Payment Intents with off-session charge flow; MIT (Merchant Initiated Transaction) exemption for recurring charges after SCA-authenticated initial payment; SCA re-authentication trigger for plan upgrade charges above thresholds
• Entitlement service. Redis-cached entitlement decisions with Kafka invalidation on subscription state change; LaunchDarkly or Unleash for feature flag evaluation per entitlement tier; usage limit enforcement at API gateway (Kong/AWS API Gateway) level
• Revenue recognition. Deferred revenue schedule per subscription period; MRR/ARR waterfall (new, expansion, contraction, churn, reactivation) calculated from subscription event log; feed to accounting system (Xero, NetSuite, QuickBooks) via nightly export
• Analytics. Churn cohort analysis, LTV calculation, trial conversion funnel in BigQuery/Redshift; Metabase or Looker dashboards for finance and product teams

Regulatory Compliance for Subscription Management Platforms

PCI-DSS: Payment Data Isolation

Payment card data is never stored in the subscription management system. Card details are captured via Stripe Elements or Adyen Drop-in and stored as payment method tokens only. The subscription engine stores the token reference and payment method metadata (last four digits, expiry, brand), not raw card data. This token-only architecture scopes PCI-DSS compliance to SAQ A or SAQ A-EP depending on implementation, rather than requiring full SAQ D assessment.

PSD2/SCA: Strong Customer Authentication for EU Recurring Charges

EU and UK regulations require Strong Customer Authentication for the initial payment and for recurring charges that do not qualify for an exemption. The subscription engine handles this by: collecting SCA-compliant 3DS authentication on the first charge, storing the resulting network transaction ID, and presenting MIT (Merchant Initiated Transaction) exemption claims on subsequent recurring charges. Charges above €30 (or £30 post-UK PSD2) that do not qualify for MIT exemption trigger a re-authentication request to the subscriber rather than failing silently.

ASC 606 / IFRS 15: Subscription Revenue Recognition

Subscription revenue is recognised ratably over the service period, not at payment date. Annual prepayments are deferred and recognised monthly. Mid-cycle plan changes create a modification event that must be evaluated against ASC 606 modification accounting, prospective or cumulative catch-up depending on whether the change represents a new distinct performance obligation. The subscription engine maintains a deferred revenue schedule per subscription that feeds the period-end revenue recognition close process.

GDPR: Renewal Consent and Cancellation Rights

EU and UK consumer protection law (reinforced by the Digital Markets, Competition and Consumers Act in the UK) requires clear disclosure of auto-renewal terms and a straightforward cancellation mechanism. For B2C subscription products, the platform enforces a cancellation flow that does not require contacting customer support; self-service cancellation is mandatory. Renewal reminder emails are sent within the required window before annual renewals. Consent records for marketing communications are stored separately from the subscription record and respect withdrawal at any time.