Entry subscription for teams validating the product shell before full production rollout.
Commercial pricing template with six explicit billing lanes.
This page keeps subscriptions, buyout, fixed packages, and flexible top-ups clearly separated. Exact money amounts should come from your actual Stripe catalog and business policy, not from fake hardcoded template prices.
Pricing contract
Plans
Use this structure as the public-facing commercial model: three recurring tiers, one buyout tier, one fixed package lane, and one flexible top-up lane.
Primary production subscription for teams turning the shared stack into a revenue product.
Top recurring plan for larger customers who need the highest-value subscription without a buyout.
Permanent access purchase for founder deals, internal tools, launch campaigns, or demo buyout offers.
Preset credits bundles backed by a Stripe Price ID and hosted Checkout.
自由充值数额: the customer enters the amount, then the backend creates a one-off PaymentIntent.
Pricing notes
These notes explain how to keep the page commercially correct instead of visually polished but operationally false.
Do not hardcode prices you cannot guarantee
This page now reflects the current commercial amounts you provided, but the operational source of truth still remains your Stripe catalog and backend checkout configuration.
Subscriptions and credits should be named separately
Starter, Pro, Premium, Lifetime, Package, and Custom Amount each represent a different commercial path. Do not collapse package credits and flexible recharge into one generic credits card.
Fixed package and free amount are different Stripe flows
Package credits still use hosted Checkout plus a fixed Price ID. Custom amount top-up uses PaymentIntent plus Payment Element, because the amount is created dynamically at runtime.
Marketing copy lives here, payment truth lives there
If a referral code was captured before signup, the billing page can still forward it as metadata when checkout is created for subscriptions, lifetime, package credits, or custom amount top-up. Checkout creation and webhook truth still stay backend-owned.