Billing overview

Switera Billing helps Builders prepare customer plans, map organizations to billing customers, assign subscriptions, review usage and invoice state, and track payment collection readiness from the same app console used for Auth, Email, Webhooks, and API keys.

Billing is app-scoped. Plans, customer mappings, subscriptions, usage, and invoices in one app do not apply to another app.

What Billing manages​

Area	Use it for	Current launch state
Customer mappings	Turn app organizations into billing customers.	Available from Sync tenants and the Billing API.
Plan catalog	Create, edit, activate, and archive customer-facing plans.	Available for fixed-price and usage-ready launch plans.
Subscriptions	Assign a billing customer to an active plan and track lifecycle hints.	Available for active, trialing, incomplete, past-due, and canceled assignments.
Usage meters	Review retained billable usage events from Switera services.	Storage, Managed Data, Email, Webhooks, and API requests have initial metering paths.
Invoices	Review invoice and collection status when invoices exist.	Read-only visibility is available for synced billing customers.
Payment collection	Check whether the app is ready to test paid customer flows.	A provider-neutral readiness checklist is visible in the Billing page and API.
Launch gaps	See the remaining Billing work before treating the app as fully launch-ready.	Visible directly on the Billing page.

Recommended setup order​

1. Create at least one organization for the app.
2. Open Services > Billing.
3. Select Sync tenants to create billing customer mappings from organizations.
4. Create the first active plan.
5. Assign the billing customer to that plan.
6. Review usage meters, invoice readiness, and payment collection setup.
7. Run a test invoice/payment flow before inviting real paying customers.
8. Use webhooks to notify your backend about plan and subscription lifecycle changes.

Do not invite real customers into paid flows until payment collection, invoice handling, dunning, and your support process are approved for the app.

Permissions​

Billing routes are app-scoped management routes. Backend integrations need a trusted secret app key with manage_settings scope.

Browser access requires the signed-in Builder to have permission to manage app settings.

What Billing does not do yet​

• It does not expose internal billing engine configuration to Builders.
• It does not provide a full customer payment portal yet.
• It does not implement dunning workflows yet.
• It does not author advanced tiers, seat pricing, custom charges, taxes, or entitlements from the UI yet.
• It does not replace your customer-facing pricing page or checkout UX.

Related pages:

• Plans and subscriptions
• Payment collection readiness
• Usage, invoices, and API
• Services overview
• Webhooks overview