Checklist of use cases / functionality for a subscription based software as a service app [closed]

Question

I want to offer a subscription using stripe on my rails site. What are some basic things that I'd want users to be able to do. (stupid question, I know, I just want to make sure I don't miss anything critical when handling people's money)

So far I have thought of:

• Secure connection (SSL)
• User accounts
• Sign up for service
• Cancel service
• Modify subscription tier
• Dispute charge? (Should I handle this, or does stripe do it?)
• View historical charges (Same here, does stripe do something for this or should I handle it?)
• Modify Payment Details (eg: CC expired, need to update to new one)

tl;dr: what's considered feature complete for basic Software as a Service subscription via Stripe?

Answer 1

It looks like Stripe does not automatically do dunning for failed payments. In subscription billing scenarios, a payment may fail for a number of reasons. It looks like Stripe will retry but what if the person's card has expired mid-way through their subscription period? What if their credit card is now maxed out?

You will need to communicate to the customer and in some cases collect new payment instrument from them.

Stripe does payment and has a simple subscription service, but there are services (contact me if you want a list) that specialize in subscription billing and automation of the failed payment conditions.

As far as reporting etc., this is another area where you might consider going with a third party that is oriented to subscription billing, they will already have these reports and generally you will be live in market much faster using them than something not specially created for subscription management.