Stripe's subscription, invoicing and recurring-revenue product — the default billing layer for global SaaS, now at a unified 0.7% of billing volume after the July 2024 plan consolidation
Stripe Billing is Stripe's purpose-built subscription, invoicing and recurring-revenue product line — the default choice for global SaaS, AI and B2B product teams that have already chosen Stripe as their payment processor and want subscription management on top of it without bringing in a separate vendor. It is part of the broader Stripe stack (founded 2010 in San Francisco by Patrick and John Collison; Stripe Billing launched as a dedicated product in 2018), and as of July 2024 Stripe consolidated the previous Starter (0.5%) and Scale (0.8%) tiers into a unified 0.7% of billing volume price. For Indian product teams, the practical positioning is clear: Stripe Billing is the right call when you're an Indian SaaS / AI company selling subscriptions to global customers (US, EU, APAC), where Stripe handles the international card acceptance and the billing layer sits naturally on top. It is not a great fit for India-domestic INR recurring payments — RBI's e-mandate regulations (in force since 2021) impose meaningful friction on card-based recurring transactions over ₹15,000, and the dominant Indian-buyer pattern for that use case is Chargebee (Indian-built), Razorpay's subscriptions product, or UPI Autopay via a domestic gateway.
Stripe Billing is a layer of products that sits on top of Stripe's core payment processing and gives you everything you need to run a subscription business — recurring billing schedules, plans and prices (with support for tiered, volume, package, graduated and usage-based pricing), invoicing, dunning (automatic retry of failed payments with email notifications), customer portals, proration and upgrades / downgrades, trials, coupons, taxes (via Stripe Tax), and revenue-recognition reporting.
It was launched as a dedicated product in 2018, and has steadily grown to be Stripe's most cross-sold add-on alongside Stripe Tax, Stripe Connect and Stripe Identity. Most modern SaaS companies that use Stripe for payments end up using Stripe Billing for subscriptions — partly because the integration is just an extension of the same Stripe SDK, partly because the Stripe-side-of-the-ledger reconciliation is automatic, and partly because Stripe has steadily added the features (Customer Portal, dunning intelligence, usage-based pricing, multi-currency invoicing) that earlier generations of SaaS teams had to bolt on with separate vendors.
Stripe itself was founded in 2010 in San Francisco by Patrick and John Collison, the Irish-born brothers who had previously built and sold Auctomatic. Stripe is privately held, headquartered in San Francisco with a major operational presence in Dublin, Ireland (Stripe's EU/EEA customers contract with Stripe Payments Europe Limited). India is supported as a Stripe market — Indian merchants can sign up for Stripe accounts and accept international payments, but the platform's India-domestic capabilities are constrained by RBI regulation in ways we cover below.
The most important fact for Indian product teams considering Stripe Billing for India-domestic recurring revenue: RBI's e-mandate regulations (in effect since October 2021) require that recurring debits from cards issued by Indian banks go through a one-time additional factor authentication (AFA), and that any recurring transaction over ₹15,000 requires AFA each time — not once, every time. This applies to both Indian merchants and foreign merchants charging Indian-issued cards.
Stripe supports the e-mandate flow for INR recurring debits, but the friction is real:
For a SaaS plan priced at ₹999/month, the constraint barely shows up. For a SaaS plan priced at ₹50,000/month or annual prepay of ₹3 Lakh, the AFA step becomes a real friction point. Many Indian SaaS sellers handle this by either (a) using Chargebee, which has built more sophisticated retry logic and customer-facing flows around the e-mandate constraint, (b) routing INR recurring through Razorpay's subscriptions product which has tighter Indian-card integration, or (c) charging upfront annual rather than monthly to minimise the recurring touch.
None of this affects Stripe Billing for international customers. If you're an Indian SaaS company selling to US / EU / APAC customers, Stripe Billing works exactly the same way it does for any global vendor.
Plans, prices, products, schedules. Supports per-seat, tiered, volume, package, graduated and usage-based pricing models. Multi-currency invoicing (170+ currencies). Trial periods, coupons, promotion codes, proration on plan changes, upgrade/downgrade flows.
Hosted invoice pages, sendable PDF invoices, customer self-serve portal for downloading and paying invoices, attached files, customisable branding. Auto-charge or send-for-payment options.
"Smart Retries" feature uses Stripe's machine learning on failed payments to choose the best retry time. Automated email notifications to customers about failed cards, plus customer-portal flow for them to update payment methods. Less configurable than Chargebee's dunning engine — see comparison below.
ASC 606 / IFRS 15-style revenue recognition reports built-in. Useful for finance teams that need GAAP-compliant subscription accounting without bolting on a separate revenue-recognition tool.
Native support for the Indian RBI e-mandate flow on Indian-issued cards in INR. Required for any India-domestic recurring use case but adds AFA friction at every >₹15K transaction. Documented in Stripe's India recurring-payments guide.
Same well-regarded Stripe SDK across Python, Ruby, Node, PHP, .NET, Go, Java; webhooks for every billing event; deep integrations with Salesforce, HubSpot, Xero, QuickBooks, NetSuite, Slack and dozens more. Developer experience is industry-leading.
Stripe Billing's pricing model was simplified in July 2024 — what used to be Starter (0.5%) and Scale (0.8%) tiers is now a single unified plan at 0.7% of billing volume. Specifically:
The page's previous "0.5–0.8% fee" is the old plan structure that no longer applies — corrected. For a SaaS company doing $100K MRR ($1.2M ARR) of subscription revenue, Stripe Billing fee alone runs roughly $700/month ($8.4K/year) — on top of which sit the actual payment-processing fees. For an Indian buyer pricing-comparing this against Chargebee, see the comparison section below.
This is the single most-asked question by Indian SaaS founders evaluating subscription-billing infrastructure. Honest framing:
Default rule of thumb: start with Stripe Billing if you're already a Stripe customer; migrate to Chargebee if and when you can articulate the specific feature gap (dunning, entitlements, multi-processor) that's actually costing you revenue.
Stripe Billing is the wrong call when: you specifically need India-domestic INR-recurring at scale (use Chargebee or Razorpay Subscriptions); you need richer dunning + entitlements at $100K+ MRR (use Chargebee); or you specifically want a payment-processor-agnostic billing engine (use Chargebee or Maxio / Recurly).