Billing is product strategy frozen in code
Pick the wrong subscription model and you chase refunds, fight churn with discount hacks, or block enterprise deals lacking invoices. LMS and developer education SaaS blend B2C learners, B2B team upskilling, and occasional lifetime deals—each with different cash flow and support load. This guide compares models we see on Toolliyo-class platforms and implementation notes for Stripe-heavy .NET and Node stacks.
Common models and when they fit
Monthly and annual recurring
Default for individual learners. Annual plan at fifteen to twenty percent discount improves retention and cash upfront. Show effective monthly price to reduce sticker shock. Auto-renew with clear email seven days before charge—required in several jurisdictions.
Tiered feature plans
Example: Free community access, Pro with courses and labs, Team with admin dashboard. Gate features in middleware checking subscription claims, not scattered if-statements. Document entitlements table product and engineering share.
Per-seat B2B
Corporate buys twenty seats; admin invites emails. Bill true-up quarterly if seats exceed purchase. Minimum seat commits secure revenue; self-serve seat add without sales call helps mid-market.
Cohort and one-time cohort passes
Live bootcamp cohort: single payment, access expires after twelve weeks plus archive read-only. Good for intensive schedules; bad for predictable MRR unless you run cohorts continuously.
Usage-based add-ons
AI interview minutes, cloud sandbox hours, certificate physical mail. Meter with idempotent usage events; cap overage to prevent bill shock surprises trending on social media.
Trials and freemium pitfalls
Seven-day trial with card upfront converts higher but attracts support complaints. Cardless trial needs strong onboarding emails day one, three, six. Freemium works when free tier showcases quality—first module complete, not teaser trailers only. Set trial webhook handlers before marketing launches ads.
Payment stack patterns (Stripe)
// Webhook idempotency — always
const event = stripe.webhooks.constructEvent(body, sig, secret);
if (await ProcessedEvent.exists({ id: event.id })) return;
switch (event.type) {
case 'invoice.payment_failed': await dunningService.start(subscriptionId); break;
case 'customer.subscription.deleted': await accessService.revoke(userId); break;
}Store Stripe customer id on user, subscription id on enrollment record. Never trust client-side payment success alone.
Tax, currency, and India specifics
Display GST-inclusive pricing for Indian consumers when required. Stripe Tax or manual tax rates per country. Support UPI and local methods via Stripe payment method configuration where conversion data shows drop-off. Invoice PDFs with legal entity name, GSTIN, SAC codes for B2B Indian invoices—finance will block launch without them.
Proration and plan changes
Upgrade mid-cycle: immediate access, prorated charge. Downgrade: often end of period to avoid partial refund arguments. Document policy on marketing site identically to Stripe billing portal behavior.
Dunning and failed payments
Grace period three to seven days with in-app banner before hard revoke. Retry smart timing (Stripe Billing retries). Email sequence: day zero fail, day three reminder, day seven last chance. Preserve progress data after revoke—learners return when card fixed.
Refunds and chargebacks
Pro-rata refund policy for annual within fourteen days reduces disputes. Chargebacks: submit activity logs showing course access. Pause certificate issuance until payment settled for high-risk regions if fraud pattern detected.
Enterprise contracts vs self-serve
PO-based annual invoices for universities bypass Stripe subscription—track in CRM with manual entitlement flag. Do not fork codebase; same access layer, different payment source field.
LMS-specific entitlements
- Course bundle SKUs mapping to many courseIds.
- Learning path subscription unlocking ordered modules.
- Affiliate and coupon stacking rules defined in one service.
Metrics finance and product share
MRR, churn, expansion revenue, LTV:CAC, trial conversion, failed payment recovery rate. Segment B2C vs B2B—blended averages mislead roadmap.
AI feature monetization
Bundle AI mock interviews in Pro tier or sell credit packs. Transparent limits ("50 sessions/month") beat opaque throttling. Log token costs internally even if priced flat to learners.
Compliance checklist
- PCI: use Stripe Elements, no raw card storage.
- Terms, privacy, refund policy linked at checkout.
- SCA for EU cards.
- Accessible checkout flows.
Launch order recommendation
Month one: single currency monthly/annual Stripe Checkout. Month two: webhooks hardened, admin refund tool. Month three: coupons and teams. Month four: tax and invoicing. Fancy usage billing waits until SKU complexity proves need.
Subscription billing for LMS SaaS rewards clarity over cleverness. Learners buy outcomes; companies buy seats and reporting. Model pricing around those truths, implement entitlements once, and let Stripe handle card networks while you focus on teaching—Toolliyo growth follows trustworthy checkout more than promotional spin wheels on pricing pages.