Buildspace
Billing

Overview

Add paid plans to a Buildspace app without embedding Stripe directly in app code.

Buildspace billing uses Stripe Connect.

  • Creators connect their own Stripe account in Creator Studio.
  • Customers pay the creator's connected Stripe account directly.
  • Buildspace creates products, prices, Checkout Sessions, customer portal sessions, and processes Stripe webhooks.
  • Creator apps integrate through the Buildspace SDK and Buildspace runtime API, not through raw Stripe secrets or webhook handlers.

Use this model when you want paid subscriptions or one-time purchases inside a Buildspace app while keeping subscription state, webhook processing, and application fee handling in the platform layer.

What your app owns

  • Pricing UI
  • Upgrade buttons
  • Success and cancel pages
  • Feature gating based on entitlements

What Buildspace owns

  • Connected-account onboarding
  • Checkout and portal orchestration
  • Stripe webhook verification
  • Subscription state sync
  • Application fee reconciliation

What not to do

  • Do not add STRIPE_SECRET_KEY to your app just to launch Checkout.
  • Do not configure raw Stripe webhooks for subscription truth.
  • Do not treat the Checkout success redirect as proof of payment.
  • Do not send explicit userId or appUserId from browser billing calls.

On this page