Payments
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.
Loads this recipe straight into the wizard — every setting stays editable before you generate anything.
The stack
Install
# pulls this exact recipe straight from the Vault $ npx stacktora install subscription-dunning-pause-resume --remote $ stacktora sync # generate the files
What you get
More from the Vault
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.
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.
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.
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.