Skip to documentation
ScrumPulseDocumentation
v2.0 docsSign in
Billing

Plans and billing

Understand the verified plan behavior and manage a Stripe subscription without relying on conflicting price copy.

Last updated August 8, 2026

ScrumPulse stores subscription state for free, pro, and team plans. Stripe Checkout starts paid subscriptions and the Stripe customer portal manages existing billing accounts.

Required permission: billing:manage. Only Clerk organization administrators receive this permission; it cannot be delegated through ScrumPulse.

Verified plan behavior#

CapabilityFreeProTeam
Project limit enforced by API plan payload1No numeric limitNo numeric limit
Dry-run modeYesYesYes
Live mode eligibilityNoYesYes
Stripe checkout supportNot neededYes, when price ID is configuredYes, when price ID is configured

The repository’s public pricing page and signed-in billing page currently disagree about paid prices and plan presentation. Prices are therefore intentionally not repeated here. Check the current Pricing page and obtain product-owner confirmation before quoting a price.

Start a paid subscription#

  1. Sign in and open Settings → Billing.
  2. Review the available upgrade option.
  3. Select the upgrade button.
  4. Complete the Stripe-hosted checkout.
  5. Return to Billing and verify the plan and status.

Checkout requires the matching Stripe price ID on the API. If it is missing, the API returns an error rather than guessing a price.

Manage payment methods and invoices#

  1. Open Settings → Billing.
  2. Select Manage billing & invoices.
  3. Use the Stripe customer portal to update a payment method, inspect invoices, or manage the subscription features enabled in Stripe.

The billing portal is available only after a Stripe customer record exists.

Status and cancellation#

ScrumPulse records active, past_due, canceled, incomplete, and trialing subscription states from signed Stripe webhook events.

The public site says cancellation remains active through the paid period, but the repository does not implement refund rules or a support process. Refund behavior, failed-payment communications, plan downgrade timing, taxes, and billing support contacts need verification.