Payments

Documentation Index

Fetch the complete documentation index at: https://docs.insforge.dev/llms.txt

Use this file to discover all available pages before exploring further.

Use InsForge Payments to charge customers, run subscriptions, and host the customer portal through Stripe without holding the secret key in your application code. Project-level Stripe keys handle billing, webhook routing, and customer/subscription mirroring into your Postgres database.

​

Features

​

Checkout sessions

Create a Stripe Checkout session with one API call and redirect the user. The session is bound to an InsForge user, so subscription state lands on the right account when the webhook fires.

​

Subscriptions

Manage recurring plans, upgrades, downgrades, trials, and proration. Subscription rows are mirrored into Postgres so feature gating and entitlements are a SELECT, not a Stripe API round-trip.

​

Customer portal

Hosted Stripe customer portal links scoped to an authenticated user. Customers update payment methods, change plans, and download invoices without you building any UI.

​

Webhook routing

Inbound Stripe webhooks land at one URL, signature-verified, idempotency-keyed, and routed to the right handler. No raw webhook plumbing in your app.

​

Declarative provisioning

Define products, prices, and webhook subscriptions in insforge.toml and apply them with the CLI. Stripe state stays in version control.

​

Concepts

​

Build with it

​

Next steps

• Set up the CLI to link your project (the recommended path).
• Browse the TypeScript SDK reference for checkout patterns.