Skip to main content

​
Payments with Stripe

Stripe is optional. When configured, users can start a Stripe Checkout flow from the app.

​
Required variables

For premium activation after payment, also configure Supabase:
Prefer SUPABASE_URL, SUPABASE_PUBLISHABLE_KEY, and SUPABASE_SECRET_KEY for server configuration. Legacy names remain supported during migration.

​
Functions

create-checkout-session.ts creates a one-time Stripe Checkout session. When Supabase is enabled, it requires a valid access token; user identity, email, and Price ID are derived by the server. stripe-webhook.ts verifies the signature, payment state, and purchased Price ID before invoking an idempotent database transaction that records payment and activates Premium. Guest support payments remain available for self-hosted deployments without Supabase, but do not grant Premium.

​
Stripe dashboard setup

  1. Create a Stripe product (for example SteadyRenew Premium).
  2. Create a one-time Price of **9.00USD∗∗(lifetime).Donotreuseanold9.00 USD** (lifetime). Do not reuse an old 6 Price — create a new Price and keep the product if you want.
  3. Copy the new Price ID (price_...) into the trusted server variable STRIPE_PRICE_ID. Optionally keep VITE_STRIPE_PRICE_ID only as a legacy server fallback; the browser does not trust it for checkout.
  4. Add your publishable key and secret key to the correct environments.
  5. Create a webhook endpoint for:
  1. Subscribe the endpoint to checkout.session.completed.
  2. Store the webhook signing secret in STRIPE_WEBHOOK_SECRET.

​
Local webhook testing

Use the Stripe CLI if you want to test webhooks locally:
Run the app through Netlify Dev while testing functions: