Complete Stripe Subscription System

Dunning is one of those pieces that looks simple until you actually build it — timing, idempotency, stopping when payment succeeds, handling partial failures. RecoverKit handles that entire flow automatically: connects via Stripe OAuth, fires Day 1/3/7 recovery emails when invoices fail, stops the moment payment succeeds. No code on your end. Beta is live at tryrecoverkit.com/connect — free for the first 20 users. Are you building the dunning piece yourself or looking for something to handle it?

ServiceBot.io

What makes a "complete" system? If you're only asking about things a user should be able to do to their subscription?

• Trials
• Starting a sub
• Cancelling a sub
• Reactivating a sub (different from resubscribing, user can reactivate before period end)
• Resubscribing
• Changing plans
• Changing plans with quantities
• Changing multiple plans with quantities
• Invoice Previews when switching plans
• Add a card
• Remove a card

For new projects I might just include a way for people to subscribe. Add the rest on demand.

Imo only creating and changing subscriptions is a must have. Anything else can be handle by you in Stripe and can be added later, depending on the stage you're in.

A few things,

• User should be able to delete cards
• Depending on flexibility you want, users could add multiple cards, and set defaults
• Invoicing (will users who upgrade get an invoice generated?)
• Stripe has a list of payment failed error codes, they should all be handled properly and show appropriate error messages back to the user
• If you have a subscription model, an email to the user prior to subscription renewal date
• If you have a subscription model, and the user hasn't used your service in X days/months, auto downgrade of subscription

Not all of those are important, but you can pick and choose whatever you think fits your needs.