What to do next
This checklist reflects the records and Stripe config this server can see.
How the pieces fit
Read left to right. This is the mental model for every app you bolt onto this billing service.
The product, like RealtyOS or ReelTours.
A Stripe price plus the features and limits that price unlocks.
One client, company, or copied app instance.
Calls this server before paid actions and records usage after.
Projects
Rotate the token when a client copy should lose API access.
| Project | Origin | Token | Action |
|---|
Tenants
A tenant is the billing identity for one client app copy.
| Tenant | Plan | Subscription |
|---|
Plans
Plans are where Stripe price IDs become RealtyOS permissions.
| Plan | Price | Stripe | Features | Status |
|---|
API call builder
Use these snippets when wiring a Base44 copy or another app.
Generated snippets
These are the calls your app makes to this billing server.
Check entitlement before an action
Record metered usage after an action
Start Stripe Checkout
Stripe webhook
This is what turns completed payments into active tenant subscriptions.
After adding `STRIPE_WEBHOOK_SECRET`, restart the billing container.
customer.subscription.created
customer.subscription.updated
customer.subscription.deleted
invoice.created, invoice.finalized, invoice.paid, invoice.payment_failed