Billing

Two separate billing relationships. Yours with Authoric, and your customers' with you.

Billing appears at two levels, and keeping them apart prevents most of the confusion:

	Your plan	Selling from your app
Who pays whom	Your organization pays Authoric	Your app's users pay you
Whose Stripe account	Authoric's	Yours, connected in the console
What it decides	How many apps, members, storage, requests and so on you may use	What each of your users has bought, and the limits and features that come with it
Where you manage it	Settings › Billing and Settings › Usage	Integrations › Providers (connect Stripe) and your app's Commerce › Products
Records live in	The platform	Your app's own database

Plans, changing plan, limits and what happens when you reach one.

Products, checkout with your own Stripe account, subscriptions and entitlements.

The short version

Limits are enforced where the action happens, not by a nightly job. Reaching one returns 402 SUBSCRIPTION_LIMIT_REACHED, and a feature your plan lacks returns 402 FEATURE_NOT_INCLUDED. Both say which limit or feature in error.details.
Going over a limit on your app's traffic never locks you out of the console, where you would upgrade.
A limit can trip inside your users' requests. A storage or bandwidth limit reached while one of your users uploads or browses refuses that request, so handle 402 in your app. At the monthly-active-user ceiling the message to the user asks them to contact the app's owner.
Money from your customers never passes through Authoric. Your app sells through your own Stripe account, and the purchase records are rows in your app's database.

Limits, usage and plan changes.

Products and purchases on your Stripe account.

Billing and limit failures in full.