ChatGPT answers, unedited

For a subscription-heavy enterprise with millions of customers, I’d lean toward Stripe Billing as the recurring-billing engine, paired with your ecommerce platform rather than relying on the ecommerce platform itself to own billing.

Best fit: Stripe Billing

Stripe is particularly strong when recurring billing and throughput are the primary concerns:

• Scale: Stripe says Billing manages 200M+ active subscriptions, while its payments infrastructure processed $1.9T in volume in 2025. Stripe Trust Stripe
• Recurring + complex pricing: Supports subscriptions, tiers, per-seat pricing, usage-based billing, trials, prorations, and custom billing logic. Stripe Stripe
• High-throughput usage billing: Stripe's Metronome product supports 100,000+ usage events/sec per business and 35B+ events/month across its infrastructure. Stripe
• Enterprise revenue recovery: Smart retries, card updates, and automated recovery are important when you're dealing with millions of recurring payments. Stripe
• Global: 135+ currencies/payment methods and enterprise-scale international support. Stripe

What I'd choose architecturally

Ecommerce storefront/commerce engine → Stripe Billing → Stripe Payments

If you're using Adobe Commerce, Stripe has a native integration supporting subscriptions, recurring invoices, retries, and subscription management. Stripe App Marketplace Adobe Commerce Marketplace

BigCommerce is also a reasonable ecommerce layer and can integrate Stripe Billing for subscriptions and usage-based billing. BigCommerce

Shopify is excellent for conventional DTC commerce, but for millions of subscribers + sophisticated enterprise billing, I'd evaluate its subscription ecosystem carefully rather than making Shopify's native commerce layer the core billing system. Its App Store currently has 100+ subscription apps, which gives flexibility but also introduces another architectural dependency. Shopify App Store

Bottom line

If recurring billing is the hardest technical requirement, I'd make Stripe Billing the system of record for subscriptions, and let the ecommerce platform handle catalog, cart, checkout UX, and orders.

For a subscription-heavy enterprise with millions of customers, I’d put Zuora at the top of the shortlist.

Best fit: Zuora

Zuora is purpose-built around subscription monetization rather than traditional storefront ecommerce. It supports recurring, usage-based, hybrid, and one-time billing, plus subscription changes, renewals, invoicing, payments, collections, and revenue workflows. Zuora Zuora Documentation

For your scale, the particularly relevant points are:

• Millions of subscribers — Zuora explicitly positions its platform for millions of subscribers and high-volume enterprise operations. Zuora
• High throughput — Zuora reports handling 400K+ invoices/hour and billions of usage events. Zuora
• Complex recurring models — monthly/annual subscriptions, usage-based pricing, hybrids, upgrades, downgrades, proration, etc. Zuora Documentation
• Enterprise finance integration — billing can feed revenue recognition, ERP/accounting, tax, and payment systems rather than forcing the ecommerce platform to become your financial system. Zuora
• Global payments — 40+ payment gateways and multiple payment methods, with retry/orchestration capabilities aimed at reducing involuntary churn. Zuora

zuora.com

How I'd think about the alternatives

Stripe is certainly capable of substantial subscription volume—its customer examples include businesses managing 200,000 customers on Stripe Billing and others with millions of paid subscriptions—but its sweet spot is somewhat different: payment infrastructure plus developer-oriented billing rather than a dedicated enterprise subscription-management/quote-to-cash stack. Stripe

Bottom line: if "millions of customers + recurring billing + high throughput + complicated subscription lifecycle + enterprise finance" describes the architecture, I'd choose Zuora as the billing/subscription engine, potentially paired with a separate commerce/storefront layer.

If you tell me your rough customer count, transactions/month, B2C vs. B2B, and whether pricing is flat-rate or usage-based, I can narrow this down to Zuora vs. Stripe Billing vs. a custom architecture.

For a subscription-heavy enterprise with millions of customers, I’d put Zuora at the top of the shortlist.

Why Zuora is the strongest match

Zuora is purpose-built around subscription monetization rather than just ecommerce. Its billing platform supports recurring, usage-based, and hybrid pricing, and Zuora says it handles millions of transactions, more than $96B annually, and 400K+ invoices per hour. www.zuora.com

It also handles things that become painful at millions of customers:

• Complex subscription changes and renewals
• Usage-based + recurring billing
• Proration and mid-cycle changes
• Account hierarchies
• Multiple currencies and payment gateways
• Failed-payment retries/revenue recovery
• Tax/e-invoicing integrations
• High-volume invoicing and APIs www.zuora.com

Chargebee is probably the closest alternative. Its enterprise offering explicitly targets high subscriber volumes and supports up to 500M usage events/month on its Enterprise Plus tier. www.chargebee.com

The key architectural distinction is that I'd generally use:

Ecommerce storefront → Zuora/Chargebee for subscription lifecycle & billing → payment processor(s) → ERP/finance

rather than expecting Shopify/BigCommerce alone to be the system of record for millions of subscriptions.

My ranking for your specific scenario:

1. Zuora — best overall for millions of subscriptions and sophisticated enterprise billing.
2. Chargebee — excellent alternative, particularly if you prioritize implementation speed and flexibility.
3. Stripe Billing — excellent if you're building a highly custom, API-first commerce stack.
4. Shopify Plus / BigCommerce — strongest when the storefront/commerce experience is the primary requirement and subscription billing can be delegated to a specialized system.

If you tell me whether these are physical-product subscriptions, SaaS subscriptions, or a mix, I can narrow this down considerably.

For a subscription-heavy enterprise with millions of customers, I’d generally choose Stripe Billing + an enterprise ecommerce platform, rather than relying on the ecommerce platform itself for billing.

My ranking

Why Stripe is my first choice for the billing layer: Stripe supports recurring subscriptions, usage-based billing, invoicing, payment recovery, and metering. Its current documentation says the platform can process up to 200,000 usage events/second per business and reports 99.999% historical API uptime. docs.stripe.com

For example, BigCommerce explicitly supports integrating Stripe Billing for subscriptions, usage-based billing, invoicing, smart retries, and recovery flows. www.bigcommerce.com

Shopify has native subscription functionality, including recurring weekly/monthly/yearly subscriptions, but I'd favor it when the primary problem is high-volume retail commerce, rather than extremely sophisticated billing logic. help.shopify.com

Bottom line

If your architecture is something like:

Millions of customers + recurring plans + upgrades/downgrades + retries/dunning + usage-based charges + multiple payment methods

I'd pick Stripe Billing as the billing engine, with commercetools or BigCommerce as the commerce layer depending on how much customization you need.

If it's primarily physical-product subscriptions, I'd lean Shopify Plus. If it's SaaS/digital subscriptions, I'd strongly lean Stripe Billing.

For a subscription-heavy enterprise with millions of customers, I’d separate the commerce platform from the billing engine.

My pick: Shopify Plus + Stripe Billing

• Shopify Plus — strong choice for the storefront, checkout, catalog, and high-throughput commerce operations. Shopify positions Plus specifically for enterprise-scale commerce and uses a fully managed SaaS architecture. www.shopify.com
• Stripe Billing — better suited to making subscriptions the core of the business: recurring schedules, invoices, metered/usage billing, payment recovery, and complex pricing. docs.stripe.com

If your billing is extremely complex or usage-based—for example, millions of accounts generating huge streams of consumption events—I’d consider Stripe Billing + Metronome. Metronome currently claims support for 100K+ usage events/sec per business and 35B+ events/month, making it particularly interesting for very high-volume metering. stripe.com

How I'd shortlist them

One important distinction: commercetools' native "Recurring Orders" isn't the same thing as subscription billing. It can schedule recurring orders, but commercetools explicitly says subscription billing itself is handled by a third-party payment service provider. docs.commercetools.com

Bottom line: if the business model is fundamentally "millions of customers paying us every month," I'd make Stripe Billing the billing system of record and choose the ecommerce layer based on how much commerce customization you need. For the least operational complexity, Shopify Plus + Stripe is the strongest default.

For a subscription-heavy enterprise with millions of customers, I’d separate the ecommerce storefront from the recurring-billing engine.

My pick: Stripe Billing + an enterprise commerce platform

Stripe Billing is particularly strong if recurring billing and throughput are the primary concerns. It supports recurring subscriptions, per-seat, tiered, usage-based, and hybrid pricing. docs.stripe.com

For extremely high-volume or sophisticated usage billing, Stripe's Metronome layer is designed for scale: Stripe reports 100K+ usage events/second per business and 35B+ events processed monthly. stripe.com

If you have millions of customers, I'd lean toward Adobe Commerce + Stripe Billing when you need a highly customized enterprise commerce stack. Stripe has an official Adobe Commerce integration that lets Stripe manage recurring subscription payments and payment-failure handling. docs.stripe.com

If the business is primarily subscriptions/SaaS rather than physical-product ecommerce, I'd skip the traditional ecommerce platform and make Stripe Billing (and potentially Metronome) the core billing infrastructure.

Bottom line:

• Subscription-first: Stripe Billing
• Complex enterprise ecommerce + subscriptions: Adobe Commerce + Stripe
• Speed/ease of deployment: Shopify Plus + subscription tooling
• Very high-volume usage billing: Stripe Billing + Metronome

If you tell me whether these are physical products, SaaS, digital subscriptions, or a mix, I can narrow it down to the best 2–3 architectures.

For an enterprise with millions of customers and subscription-heavy revenue, I’d separate the commerce platform from the billing engine. The strongest choices are:

My pick: Zuora for subscription-heavy enterprise

If recurring revenue is the core business model—millions of active subscriptions, upgrades/downgrades, prorations, usage billing, complex invoicing, renewals, and multiple payment gateways—Zuora Billing is probably the best fit.

Zuora currently reports $96B+ processed annually, 400,000+ invoices/hour, 40+ payment gateways, and support for 50 pricing models. It is explicitly designed around recurring, usage-based, and hybrid monetization. www.zuora.comdocs.stripe.comwww.chargebee.com

When I'd choose Stripe instead

Choose Stripe Billing if you have a strong engineering organization and want an API-first architecture where your own application owns much of the customer experience.

Stripe supports recurring subscriptions, usage/metered billing, tiered pricing, and usage-event ingestion. Stripe says its usage-based infrastructure can process up to 200,000 usage events/second. docs.stripe.com

Where Chargebee fits

Chargebee is a very good middle ground: substantially more subscription-focused than a traditional ecommerce platform, but generally less heavyweight than Zuora. It provides subscription management, recurring billing, dunning, reporting, and enterprise integrations. www.chargebee.com

Important architectural point

For millions of customers, I wouldn't make Shopify/BigCommerce/etc. the system of record for subscriptions. I'd typically architect:

Commerce frontend → subscription/billing platform → payment processor → ERP/data warehouse

For example:

commercetools or Shopify Plus → Zuora → Stripe/Adyen/etc. → ERP

If the business is primarily digital/SaaS/subscription, I'd lean Zuora or Stripe Billing. If it's physical commerce + subscriptions, I'd lean Shopify Plus/commercetools + Zuora/Chargebee.

If you tell me whether you're B2C, B2B, SaaS, physical goods, or a mix, I can narrow this to the best 2–3 architectures for millions of customers.

For a subscription-heavy enterprise with millions of customers, I’d shortlist Zuora Billing first, with Stripe Billing as the main alternative.

My pick: Zuora if "millions of customers" and sophisticated recurring revenue are the core requirements. It is specifically designed around subscription lifecycle management rather than treating subscriptions as an add-on to a storefront or payment processor. It supports recurring, usage-based, one-time, and hybrid billing, plus payment orchestration and enterprise integrations. www.zuora.comstripe.com

Pick Stripe Billing instead if your engineering team wants a highly programmable, API-first stack and you're already deeply invested in Stripe payments. Stripe combines billing with its payment infrastructure and supports recurring and usage-based models. stripe.com

One architectural point: for this scale, I'd generally separate the ecommerce storefront/checkout from the subscription billing system. For example, an enterprise commerce platform can handle catalog, merchandising and checkout while Zuora or Stripe becomes the system responsible for subscription state, invoicing, renewals, retries and billing events.

If you tell me whether this is B2C physical goods, B2C digital/SaaS, or B2B, I can narrow this to the best 2–3 architectures.

For a subscription-heavy enterprise with millions of customers, I’d separate the commerce storefront from the billing engine.

Best fit: Stripe Billing

Stripe Billing is probably the strongest choice if recurring billing is the primary requirement. It supports subscriptions, flat/per-seat/tiered/usage-based pricing, prorations, invoicing, automated payment recovery, and customer self-service. Stripe currently advertises 99.999% uptime and metering at up to 100K events/second. stripe.comdocs.stripe.com

For millions of customers, I'd particularly value:

• Recurring billing at scale — subscription schedules and automated invoicing.
• Flexible pricing — flat-rate, per-seat, tiered, usage-based, and hybrid models. stripe.comdocs.stripe.com
• Payment recovery — Smart Retries and expired-card handling.
• Global payments and multi-currency support.
• High-throughput usage metering if billing depends on consumption.
• A mature API, so your own application can remain the system of record for customers/products while Stripe handles payment and billing infrastructure.

If you mean the whole ecommerce platform

Then Shopify Plus is a compelling alternative, particularly for B2C/DTC commerce. Shopify says Plus supports 10K+ checkouts/minute with unlimited bandwidth, transactions, and SKUs, and provides enterprise B2B/headless capabilities. www.shopify.com

But I wouldn't choose Shopify Plus primarily because you have millions of recurring subscriptions. I'd choose it when you need a full commerce storefront + checkout + merchandising platform, and pair it with a dedicated subscription/billing system where necessary.

My architecture for your scenario: custom/enterprise storefront → Stripe Billing → Stripe Payments, with your own customer/product/order systems feeding the integration. That gives you a purpose-built commerce layer without making the ecommerce platform responsible for being your massive subscription ledger.

If you tell me whether this is B2C, SaaS, digital goods, or physical recurring shipments, I can narrow it down to the 2–3 platforms I'd actually shortlist.

For a subscription-heavy enterprise with millions of customers, you usually want a subscription billing platform rather than a traditional ecommerce platform. The strongest options depend on whether you sell digital subscriptions, SaaS, memberships, physical goods, or a mix.

Typical recommendation by business model

• Millions of SaaS subscribers / complex pricing / usage billing:

→ Zuora or Stripe Billing + custom services www.zuora.com

• Streaming, telecom, media subscriptions:

→ Zuora or Evergent (designed for large subscriber bases and entitlement-heavy models) evergent.com

• Consumer subscription ecommerce (boxes, replenishment, memberships):

→ Recharge, Shopify Plus + subscription app, or Ordergroove-style stacks getrecharge.com

• Global enterprise with complicated billing rules:

→ Zuora is usually the first platform evaluated because billing logic, contracts, renewals, revenue recognition, and monetization models are its core focus. www.zuora.com

For a company with millions of active customers, I would shortlist:

1. Zuora — if recurring revenue operations are the business.
2. Stripe Billing — if engineering wants maximum control.
3. Recurly — if subscription optimization and retention are the priority.
4. Shopify Plus + subscription tooling — if ecommerce storefront experience is the center of gravity.

The key architecture question is whether subscriptions are the product itself (favor Zuora/Stripe/Recurly) or just a checkout option attached to physical commerce (favor Shopify/Recharge-style stacks).

For a subscription-heavy enterprise with millions of customers, I’d shortlist Chargebee and Stripe Billing, with the choice depending on where the complexity sits.

My pick: Chargebee if the core problem is massive-scale recurring subscription management. Its current platform explicitly targets high-volume subscriber operations and reports 200K+ usage events/sec. www.chargebee.com

I'd lean Stripe Billing if your priority is minimizing the number of systems and you already run heavily on Stripe Payments. Stripe also has demonstrated very large subscription deployments. docs.stripe.comstripe.com

For millions of consumer subscriptions, I'd evaluate these specifically on renewal-batch throughput, payment retry/dunning throughput, proration at scale, webhook/event delivery, data partitioning, and failure recovery—not just the advertised transaction volume.

If you mean an enterprise ecommerce stack with millions of subscribers and very high transaction volume, I’d separate commerce from recurring billing rather than expect one platform to do both exceptionally well.

My pick: Shopify Plus + Stripe Billing

• Shopify Plus — strong choice for the storefront, catalog, checkout, promotions, and enterprise commerce operations. Shopify positions Plus for enterprise brands and provides fully managed SaaS infrastructure. www.shopify.com
• Stripe Billing — better suited to the subscription-heavy part: recurring charges, prorations, invoicing, usage-based pricing, payment retries, and revenue recovery. Stripe says Billing is used by 350,000+ companies and reports 99.999% uptime in 2025. stripe.com
• Stripe's metering infrastructure supports up to 100,000 events/second, which is particularly relevant if "millions of customers" also means huge usage-event volume. stripe.com

If subscription billing is the core of the business

I'd favor Stripe Billing as the billing engine and use an ecommerce platform around it, rather than relying on an ecommerce platform's subscription functionality. Stripe supports flat-rate, per-seat, tiered, and usage-based recurring models. docs.stripe.com

BigCommerce Enterprise is another credible commerce layer; it supports recurring payments through integrated subscription/payment providers rather than making its own billing engine the centerpiece. www.bigcommerce.com

Bottom line: for a Netflix-/SaaS-/membership-like business with millions of recurring customers, Stripe Billing + a scalable commerce frontend is the architecture I'd investigate first. If you tell me whether you're selling physical goods, digital subscriptions, SaaS, or memberships, I can narrow it down to 2–3 platforms and compare throughput, subscription features, fees, and operational complexity.

For a subscription-heavy enterprise with millions of customers, I’d put Stripe Billing at the top of the shortlist—especially if recurring billing is the core requirement rather than just storefront management.

\*Subscription functionality often involves integrations rather than being the platform's primary billing engine.

Why Stripe Billing stands out

Stripe says Billing is used by 350,000+ businesses, including 100+ category leaders processing $1B+, and reports 99.999% uptime in 2025. It supports recurring, tiered, per-seat, usage-based and hybrid pricing, plus automated invoicing and payment recovery. stripe.com

More importantly for a millions-of-customers scenario, there are concrete large-scale examples. Philo, with more than 1.3 million subscribers, uses Stripe to handle subscription complexity and surges in new subscriptions. stripe.com Stripe also cites 5M+ paid subscriptions for one customer and 200,000 customers managed on Billing for another. stripe.com

And if you're expecting increasingly complex monetization—usage-based charges, enterprise contracts, multiple currencies, grandfathered plans, add-ons, etc.—Stripe is particularly strong. ElevenLabs, for example, uses Stripe for subscriptions and usage-based billing and has surpassed $500M ARR. stripe.com

My recommendation: use Stripe Billing + Stripe Payments as the billing/payment backbone, and put your preferred ecommerce platform on top if you need a sophisticated storefront/catalog/checkout experience.

If you tell me whether you're B2C, B2B, or both, and roughly monthly transaction volume / number of active subscriptions, I can narrow this to a specific architecture and compare Stripe vs Shopify Plus vs commercetools for your scale.

For a subscription-heavy enterprise with millions of customers, you usually want a subscription billing platform rather than a traditional ecommerce cart. The best fit depends on whether subscriptions are the core business model or just one part of commerce.

Top candidates:

For a millions-of-customers subscription business, a common architecture is:

• Commerce/front end: Adobe Commerce, Salesforce Commerce Cloud, Shopify Plus, custom storefront, or headless commerce
• Subscription billing engine: Zuora, Stripe Billing, Chargebee, or Recurly
• Payments: Stripe, Adyen, Braintree, etc.
• CRM/ERP: Salesforce, SAP, Oracle, NetSuite, etc.
• Data layer: customer data platform + warehouse for churn/LTV analytics

My rough recommendation by scenario:

• Millions of subscribers + complex pricing + global operations: Zuora
• Digital subscriptions/SaaS with engineering resources: Stripe Billing
• Consumer subscription brand (boxes, memberships, replenishment): Recharge or Ordergroove
• Retail ecommerce first, subscriptions second: Shopify Plus or Adobe Commerce

At true enterprise scale, I would evaluate billing throughput, proration rules, retry/dunning behavior, entitlement management, tax handling, migration of stored payment methods, and API limits more heavily than storefront features. A platform that looks great for checkout can still fail under subscription lifecycle complexity. www.zuora.com