Add subscriptions to your app
Sell a Pro plan with Stripe Checkout, lock a paid feature to subscribers, and watch Strent follow a cancellation. Every step ends with a checkpoint.
Add Stripe subscriptions to your SaaS.
No webhook code.
Stripe charges your customers. Strent keeps track of which plan each one has. Your app decides what they can use.
Charges your customers
Stripe
Your plans and prices, its payment page (Checkout), and its plan management page (Customer Portal) stay in your Stripe account.
Keeps track of what is active
Strent
Receives Stripe's messages about every change (webhooks) and answers your app's access checks. You write no webhook code.
Decides what they can use
Your application
Your code maps each user to a Stripe customer and each plan to what it unlocks.
Your plans stay in Stripe. Works with any login and any database. You create your plans and prices in your own Stripe account, and Strent reads them from there, so you never keep two lists in sync. Strent needs only the ID Stripe gives each customer, not your users’ accounts, so it works with whatever signs your users in: Supabase Auth, Auth.js, Better Auth, or your own. Strent keeps track of each customer’s subscriptions, so your app stores only that ID, in whatever database it already uses.
Where to go next
Section titled “Where to go next”Understand how Strent works
How Strent hears about each change in Stripe and answers your app’s access checks, and where Strent stops and your app begins.
Look up the SDK and API
Every Node.js SDK method and HTTP endpoint, with its errors and what happens when Strent cannot answer.
Operate and recover
See what needs your attention in Strent Admin, fix its cause, and have Strent read a customer from Stripe again when an answer looks wrong.