Skip to main content

​
Billing & plans

Starfire AI Billing 4.0 connects product entitlements, usage, credits, organization context, and Stripe-backed subscription state into one billing model. The key principle is that payment state and application access must agree.

​
Billing-account model

Starfire uses a billing-account layer so subscription state belongs to a defined personal or organization context. Conceptually:
This prevents a Stripe subscription from existing as a detached payment record with no reliable connection to the Starfire account that should receive access.

​
Checkout

Before checkout, Starfire should resolve or create the correct billing account and Stripe customer for the active context. Checkout then uses the configured price mapping for the selected plan. After Stripe processes payment, webhook and reconciliation flows update the Starfire subscription and entitlement state.

​
Webhooks

Billing 4.0 treats Stripe webhooks as important state transitions. Webhook handling should be idempotent so receiving the same event more than once does not duplicate provisioning or credits.

​
Reconciliation

Webhooks are not the only source of recovery. Reconciliation and polling can compare Starfire’s billing records with Stripe so temporary delivery failures do not permanently leave the two systems out of sync.

​
Plan changes

Supported plan and seat changes should update the existing billing relationship rather than creating disconnected subscriptions whenever possible. The resulting entitlements are derived from the reconciled subscription and Starfire plan configuration.

​
Customer portal

Where enabled, Stripe’s customer portal provides a secure self-service surface for supported subscription and payment-method actions without exposing raw payment details to Starfire.

​
Credits and usage

A subscription can provide plan entitlements and a compute/credit allowance. Starfire’s metering layer can distinguish usage categories while still charging them against the appropriate personal or organization billing context.

​
Current plan families

Starfire’s product architecture supports plan families including Free, Plus, Pro, and Business. Exact pricing, allowances, feature access, and availability are controlled by the current production plan configuration rather than hardcoded into this documentation.
A successful Stripe charge by itself is not proof that Starfire provisioning completed correctly. If payment succeeded but access is wrong, troubleshoot the billing-account, subscription, webhook, reconciliation, and entitlement chain instead of purchasing the plan again.

Subscriptions & Stripe

See the subscription lifecycle and reconciliation model.

Credits & metering

Understand how usage is attributed and measured.

Organization billing

Learn how seats, shared credits, and organization ownership affect billing.

Billing troubleshooting

Resolve plan, provisioning, portal, and reconciliation problems.