Provider self-serve

Self-serve flows use the payment provider as purchase source of truth. Vluna exposes hosted checkout/portal entry points plus billing state APIs.

Prereqs

• You can issue bearer tokens for your frontend.
• You have defined product catalog and pricing baseline:
  • Operate the product catalog
  • Pricing model blueprint (plan-centric)

Workflow

1. Frontend lists products and prices.
2. Frontend creates a checkout session for the selected price.
3. Provider completes checkout and sends webhooks.
4. Vluna updates account state based on provider events.
5. Frontend uses the portal for management.

Provider self-serve rules

• Checkout conflict handling: if the requested purchase conflicts with an existing non-stackable active subscription, checkout creation returns a portal destination instead of a new checkout flow.
• Recurring subscription state is modeled by subscription groups and synchronized from provider subscription events.
• Plan-centric mapping is driven by catalog price metadata (for example billing-plan mapping keys), not by client-only state.

What your app should rely on

• Use webhook-finalized state from Vluna billing APIs for entitlement-sensitive UX.
• Treat redirect success as provisional until provider event processing completes.
• Keep a fallback path to portal for customer-managed subscription changes.

Verify

• Checkout session creation returns a session URL.
• Subscriptions endpoint reflects the active subscription after provider finalization.

Next

• End-to-end flow design: Self-serve orchestration
• Subscription packaging: Subscription group modeling