One-off payments

What it adds to your app

Table payment linked to your table. PayableList and MyPayments components with their pages. A Stripe-signed webhook that marks payments paid or not completed. Server functions: checkout and a manual check with Stripe. A staff payments page.

How its workflows run

Each one is a server workflow in your project: it runs on its trigger, with retries, and its runs show in the builder's log.

1. Start a Stripe Checkout for one ‹attach_to›

   When the app calls it: server function (‹payer_role›). Then: Look up ‹attach_to›, then Call api.stripe.com, then Create payment.

2. Apply Stripe's checkout events to payments

   When a webhook arrives: webhook stripe-payment-events. Then: Look up payment, then Update payment.

3. Check a payment with Stripe (fallback)

   When the app calls it: server function (‹payer_role›, @staff). Then: Look up payment, then Call api.stripe.com, then Update payment.

4. Apply what Stripe said about a payment

   When a row changes: payment updated, when check is requested. Then: Update payment.

5. Thank the payer when a payment goes through

   When a row changes: payment updated, when status is paid. Then: Notify.

Set it up

It merges into the contract of an app you already have. Nothing is overwritten: a name you already use is refused until you pass a prefix.

1. Pick the project

   Use the button above, or ask your coding agent with the Appbricx MCP server connected (quickstart).

2. Point it at your 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
   attach_to	The table whose records people pay for (bookings, orders, invoices).	booking
   price_field	The number field on that table holding what to charge. Optional.	total
   payer_role	The role whose people pay (their own table is the payer). Optional.	customer
   payer_ref	Optional: the ref on that table naming the person who owes it, so people only see and pay their own. Optional.	customer_id
   currency	The three-letter currency code, lower case. Optional.	usd

3. Connect what it calls

   add the STRIPE_SECRET_KEY secret (project settings); add the STRIPE_WEBHOOK_SECRET secret (project settings). A table with a number price field. A Stripe webhook endpoint at the URL get_contract lists for stripe-payment-events (Backend, API in the builder), with its signing secret in STRIPE_WEBHOOK_SECRET.

4. Preview, then apply to dev

   A dry run shows the diff and the check report; applying it changes your dev environment only.

5. Deploy

   When dev looks right, deploy. Production gets a snapshot first, so you can roll back.

Use it with your coding agent

The agent reads the template, runs a dry run, shows you the diff and applies it.

Add the One-off payments template (slug "one-off-payments") 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 (attach_to: what is paid for; price_field: price field; payer_role: who pays; payer_ref: whose record it is; currency: currency).

{
  "tool": "use_template",
  "arguments": {
    "slug": "one-off-payments",
    "project_id": "<your project id>",
    "params": {
      "attach_to": "booking",
      "price_field": "total",
      "payer_role": "customer",
      "payer_ref": "customer_id",
      "currency": "usd"
    },
    "dry_run": true
  }
}

appbricx templates use one-off-payments --param attach_to=booking --param price_field=total --param payer_role=customer --param payer_ref=customer_id --param currency=usd --dry-run

Works with

The services this template calls. Each page lists every action and what connecting it takes.

• Stripe