Payments
Payments recipes
8 admin-reviewed Payments starting points in the Vault, each installable with one command. Browse every category →
Digital Wallet / Stored Balance Backend
A stored-value balance (gift cards, in-app currency, prepaid credit) with Postgres as the source of truth and Redis for fast balance checks — distinct from the Ledger recipe (double-entry accounting) and Usage Metering (consumption billing): this is money already collected, sitting in an account, waiting to be spent.
by @ops
Go + Postgres + Redis: Marketplace Escrow & Split Payment Backend
Holds funds in escrow until release conditions are met, then splits payouts via Stripe Connect, a worker processing the release logic — distinct from the general Marketplace recipe and from the Ledger: this is specifically the escrow/hold mechanism sitting between a buyer's payment and a seller's payout.
by @ops
Ledger & Double-Entry Accounting Starter
A Postgres-only backend built around double-entry bookkeeping — tracking balances and money movement correctly, not processing payments. Distinct from a Stripe/subscription starter: this is for internal ledgers, marketplaces splitting payouts, or anything that has to get "where did this dollar go" provably right.
by @ops
Membership & Tiered Access Backend
Membership tiers gating feature/content access, Stripe-connected for the billing side, Redis for fast access checks on every request. Distinct from Usage Metering: that bills for consumption, this is a fixed tier granting or denying access.
by @ops
Multi-currency & FX Conversion Service
Currency conversion with rate caching and a worker keeping exchange rates fresh — distinct from the Ledger recipe: that records transactions correctly, this is what makes cross-currency amounts comparable in the first place.
by @ops
Node + Stripe SaaS Starter
A subscription SaaS backend: Node API, Postgres for customers/subscriptions, Redis for webhook idempotency, and a background worker for async Stripe event processing.
by @ops
Subscription Dunning & Pause/Resume Management
Failed-payment retry logic (dunning), and pause/resume subscription state via Stripe and a worker — the specific, often-mishandled part of subscription billing: what happens when a card fails, not just what happens when it succeeds.
by @ops
Usage Metering & Billing
Track consumption — API calls, tokens, seats, whatever your unit is — in Postgres with Redis for fast real-time counters, and turn it into billable line items via Stripe. Distinct from a subscription-SaaS starter: this is for usage-based pricing, not flat monthly plans.
by @ops