How to bill multiple apps from one Stripe account

The short answer is yes, and nothing in Stripe stops you. The reason the question keeps getting asked is that Stripe has no concept of an “app” at all. Products, prices, customers and subscriptions are flat lists belonging to the account, so every per-app boundary you want has to be invented and enforced by you.

If a search for this sent you to Stripe’s multi-entity business guide, that is a different question: several legal entities with several accounts. One company with several products is the case below.

What one Stripe account does and does not give you

One Stripe account can sell several different products

Products and prices are flat lists on the account. Nothing stops you creating a set per app, and no Stripe limit is involved.

Stripe has a concept of an "app" that owns its own plans

There is no such object. The grouping has to live in metadata you set and read yourself, or in your own database.

One webhook endpoint can serve all of them

But it has to work out which app each event belongs to, from metadata or from the price id, before it can grant anything.

Stripe Connect is the feature for this

Connect is for paying other people: marketplaces and platforms moving money to third-party sellers. Your own second app is not a third party, and Connect adds onboarding and payout complexity you do not need.

Stripe’s "multi-entity business" guide answers this question

That guide is about several legal entities, each with its own Stripe account, usually for tax or regulatory reasons. If you are one company with several products, it is the wrong document.

Customers stay separate per app

A Customer belongs to the account, not to an app. The same email buying two of your products is one Stripe Customer with two subscriptions, and your own tables decide what that means.

The three routes

1. One account, metadata, and your own routing

Correct for two or three apps you do not expect to grow.

Stamp every price and every subscription with an app identifier in metadata. Your single webhook reads it and writes to a subscriptions table with an app column. Each app queries its own rows.

What it costs you: You write the routing, the state machine and a pricing page per app, once per app. The work does not shrink with the fourth app, it repeats.

2. A separate Stripe account per app

Correct when the apps belong to different companies.

Clean separation of payouts, tax settings and reporting. If two products sit in two legal entities, this is not a preference, it is the requirement.

What it costs you: Separate keys, separate dashboards, separate webhooks and separate reconciliation, multiplied by the number of apps. Nothing is shared, including your view of total revenue.

3. A billing layer that treats an app as a first-class row

What SparkPay does, and the rest of this page describes it.

One deployment, one Stripe account, and an apps table where each row carries its own plans, trial, webhook target, sender address and pricing page. Adding the fourth app is a dashboard form, not a deploy.

What it costs you: A service in the path, and the pricing page lives on SparkPay rather than on your own domain. Stripe still processes every card at its ordinary fees: this replaces engineering, not payment costs.

Route three, concretely: what an app row holds

“Multi-tenant” is a word that hides the detail, so here are the columns. Each registered app is one row, and these are the fields that stop one product’s plans, emails and webhooks reaching another. This deployment runs 17 apps on one Stripe account today.

The per-app columns a SparkPay app row carries, and what each one isolates
Per-app fieldWhat it isolates
pricing_plansIts own tiers and Stripe price ids. No app sees another’s.
owner_slug + app_slugIts hosted pricing page URL, unique on the pair.
trial_daysIts own trial length, or none.
webhook_url + webhook_secretEvents pushed to that app alone, HMAC signed.
from_emailReceipts and reminders sent from that product’s own address.
referral_configIts own referral programme, or disabled.
tagline, faq, customizationThe copy and look of its pricing page.
app_typeweb, chrome_extension, npm or cli, so a CLI bills the same way a site does.

Columns read from this project’s own schema in November 2026. The app count is read from the live catalogue and moves as apps are registered.

When you do not need any of this

If you have one app, stop here. The number of apps is exactly what SparkPay charges for: the free tier and Essentials each cover one, Founder covers three, Growth is unlimited. One app means the free tier is the whole product, so there is nothing on the pricing page worth buying yet. Come back at the second one.

Questions

Can I use one Stripe account for multiple apps?

Yes, and there is no Stripe limit on it. What you do not get is any notion of which app a product, customer or subscription belongs to. That grouping lives in metadata you set and read, or in your own database, and building it is the actual work.

Do I need Stripe Connect for this?

Almost certainly not. Connect exists to pay third parties, as a marketplace pays its sellers. Your own second app is not a third party, so Connect adds seller onboarding and payout handling for no benefit.

Should I open a second Stripe account instead?

Only if the apps belong to different legal entities, or their tax treatment genuinely differs. Otherwise you are multiplying keys, dashboards, webhooks and reconciliation, and giving up any single view of revenue.

How does one webhook endpoint know which app an event is for?

It has to look. Either you stamped an app identifier into the metadata of the price or the Checkout Session and read it back, or you map the price id to an app yourself. An endpoint that grants entitlements without resolving the app first will eventually grant the wrong one.

Does SparkPay replace Stripe?

No. It runs on your own Stripe account, your customers and payouts stay yours, and Stripe charges its usual processing fees either way. What it replaces is the layer above: the plans, the pricing page, the webhook and the entitlement read.

What if I only have one app?

Then you probably do not need any of this. SparkPay’s free tier covers one app with a hosted pricing page, Stripe checkout and the gating kit, and the only reason to leave it is processing more than its cap or wanting invoices and webhooks. Multi-app is what the paid tiers are for, and with one app there is nothing here worth buying.