Block · Payments and billing

Stripe subscriptions

Adds plans (each linked to a Stripe price) and subscriptions. A Plans and billing page lets people pick a plan and pay on Stripe's secure checkout. Stripe then tells the app what happened through a signed webhook (checkout completed, invoice paid or failed, subscription changed or cancelled), and only the server marks a subscription active. Manage billing opens Stripe's customer portal to change card, switch plan or cancel. Rules stop anyone marking their own subscription paid. Staff manage plans and see every subscriber.

View the files

use_template { slug: "stripe-subscriptions" } adds

Tables: plan, subscription
Components: BillingPanel
Pages: /billing, /subscriptions-admin
Workflows: subscription-checkout, stripe-subscription-events, subscription-sync, subscription-apply-sync, billing-portal, subscription-active-notify
Rules: 2 on subscription

What it adds to your app

Tables plan and subscription (two starter plans). BillingPanel component on a Plans and billing page. A Stripe-signed webhook that applies checkout, invoice and subscription events. Server functions: checkout, billing settings and a manual check with Stripe. A staff page for plans and subscribers.

Tables

plan name, description, price, currency, interval, stripe_price_id, features, active, …
subscription subscriber_id, plan_id, status, sync, stripe_session_id, stripe_subscription_id, stripe_customer_id, current_period_end

Workflows

subscription-checkout Start a Stripe Checkout for a plan. On server function (‹subscriber_role›)
stripe-subscription-events Apply Stripe's subscription events. On webhook stripe-subscription-events
subscription-sync Check a subscription with Stripe (fallback). On server function (‹subscriber_role›, @staff)
subscription-apply-sync Apply what Stripe said about a subscription. On subscription updated
billing-portal Open Stripe's billing settings for a subscriber. On server function (‹subscriber_role›)
subscription-active-notify Tell the subscriber their plan is active. On subscription updated

Components

BillingPanel Plans to choose from, the current subscription and Stripe billing settings

Rules on every write

subscription A new subscription starts as pending until Stripe confirms it.
subscription Only Stripe can change a subscription.

Where it attaches

Params point the template at your own tables and roles. Leave out the ones with defaults; a wrong one is refused with the options your app has.

Param	What it is	Example
`subscriber_role`	The role whose people buy a plan (their own table is the subscriber). Optional.	`member`

Use with your coding agent

Connect the Appbricx MCP server to Claude Code, Cursor or any MCP client (quickstart).
Paste the prompt. The agent reads the template, previews the merge with dry_run and shows you the diff.
It applies to dev. Check it, then deploy when you are happy.

Needs the STRIPE_SECRET_KEY secret, the STRIPE_WEBHOOK_SECRET secret. A Stripe account with a recurring price for each plan (paste each price id into the plan).

Prompt

Add the Stripe subscriptions template (slug "stripe-subscriptions") to my Appbricx project. Read it with get_template, run use_template with dry_run first and show me the diff, then apply it. Ask me where it attaches if you can't tell from my contract (subscriber_role: who subscribes).

MCP call

{
  "tool": "use_template",
  "arguments": {
    "slug": "stripe-subscriptions",
    "project_id": "<your project id>",
    "params": {
      "subscriber_role": "member"
    },
    "dry_run": true
  }
}

CLI

appbricx templates use stripe-subscriptions --param subscriber_role=member --dry-run

Your agent adds it. Appbricx runs it.

Start free All templates

Block · Payments and billing

Stripe subscriptions

View the files

use_template { slug: "stripe-subscriptions" } adds

Tables: plan, subscription
Components: BillingPanel
Pages: /billing, /subscriptions-admin
Workflows: subscription-checkout, stripe-subscription-events, subscription-sync, subscription-apply-sync, billing-portal, subscription-active-notify
Rules: 2 on subscription

What it adds to your app

Tables

plan name, description, price, currency, interval, stripe_price_id, features, active, …
subscription subscriber_id, plan_id, status, sync, stripe_session_id, stripe_subscription_id, stripe_customer_id, current_period_end

Workflows

subscription-checkout Start a Stripe Checkout for a plan. On server function (‹subscriber_role›)
stripe-subscription-events Apply Stripe's subscription events. On webhook stripe-subscription-events
subscription-sync Check a subscription with Stripe (fallback). On server function (‹subscriber_role›, @staff)
subscription-apply-sync Apply what Stripe said about a subscription. On subscription updated
billing-portal Open Stripe's billing settings for a subscriber. On server function (‹subscriber_role›)
subscription-active-notify Tell the subscriber their plan is active. On subscription updated

Components

BillingPanel Plans to choose from, the current subscription and Stripe billing settings

Rules on every write

subscription A new subscription starts as pending until Stripe confirms it.
subscription Only Stripe can change a subscription.

Where it attaches

Params point the template at your own tables and roles. Leave out the ones with defaults; a wrong one is refused with the options your app has.

Param	What it is	Example
`subscriber_role`	The role whose people buy a plan (their own table is the subscriber). Optional.	`member`

Use with your coding agent

Connect the Appbricx MCP server to Claude Code, Cursor or any MCP client (quickstart).
Paste the prompt. The agent reads the template, previews the merge with dry_run and shows you the diff.
It applies to dev. Check it, then deploy when you are happy.

Needs the STRIPE_SECRET_KEY secret, the STRIPE_WEBHOOK_SECRET secret. A Stripe account with a recurring price for each plan (paste each price id into the plan).

Prompt

Add the Stripe subscriptions template (slug "stripe-subscriptions") to my Appbricx project. Read it with get_template, run use_template with dry_run first and show me the diff, then apply it. Ask me where it attaches if you can't tell from my contract (subscriber_role: who subscribes).

MCP call

{
  "tool": "use_template",
  "arguments": {
    "slug": "stripe-subscriptions",
    "project_id": "<your project id>",
    "params": {
      "subscriber_role": "member"
    },
    "dry_run": true
  }
}

CLI

appbricx templates use stripe-subscriptions --param subscriber_role=member --dry-run

Your agent adds it. Appbricx runs it.

Start free All templates

Stripe subscriptions

What it adds to your app

Tables

Pages

Workflows

Components

Rules on every write

Where it attaches

Use with your coding agent

One-off payments

Stripe payment received

Organisations and teams

Your agent adds it. Appbricx runs it.

Stripe subscriptions

What it adds to your app

Tables

Pages

Workflows

Components

Rules on every write

Where it attaches

Use with your coding agent

One-off payments

Stripe payment received

Organisations and teams

Your agent adds it. Appbricx runs it.

Stripe subscriptions

What it adds to your app

Tables

Pages

Workflows

Components

Rules on every write

Where it attaches

Use with your coding agent

Goes well with

One-off payments

Stripe payment received

Organisations and teams

Your agent adds it. Appbricx runs it.

Stripe subscriptions

What it adds to your app

Tables

Pages

Workflows

Components

Rules on every write

Where it attaches

Use with your coding agent

Goes well with

One-off payments

Stripe payment received

Organisations and teams

Your agent adds it. Appbricx runs it.