Skip to main content

Checkout & provisioning lifecycle

Starfire Billing 4.0 treats checkout as the beginning of a state transition, not the entire billing process.

Lifecycle

1. Choose billing context

Confirm whether the subscription belongs to your personal account or an organization before starting checkout.

2. Customer linkage

Starfire links the BillingAccount to a Stripe Customer before the subscription is treated as owned by the account context.

3. Price mapping

The selected Starfire plan maps to configured Stripe price identifiers. Production configuration—not documentation text—is the source of truth for active prices.

4. Payment completion

Completing Stripe checkout means the payment/subscription flow reached Stripe successfully. Starfire still needs to process and reconcile the resulting subscription state.

5. Provisioning

Entitlements, plan state, credits, and seat behavior are derived from reconciled billing state.

If the page returns before access updates

Allow normal webhook/reconciliation processing to complete and refresh the billing view. Do not immediately create another checkout.

Duplicate prevention

Billing 4.0 is designed around deterministic ownership and idempotent event handling so network retries or duplicate webhook delivery do not create duplicate entitlement grants.
If payment succeeded but Starfire still shows the old plan, troubleshoot the existing billing chain. A second purchase can create a more complicated duplicate-subscription problem.