Multiple SaaS products via Stripe (best practices?)
When using Stripe for running multiple SaaS products, how do you separate the different product offerings? Do you create multiple accounts, or do you just separate the different product offerings and hardcode the product/plans in your application?
Trending on Indie Hackers
Question related to this: let's say I have a couple small products. They're separate websites, so I'd need seperate stripe accounts. However, I only want to incorporate a single LLC for them.
If I setup an LLC with stripe atlas, can I then make multiple stripe accounts with that LLC? Or is it "bound" to the single stripe account that's created when you setup atlas?
I create multiple accounts and it works pretty well.
One email to enter but multiple accounts inside.
Another "hack" is to connect the stripe's plans to the code, I do it using metadata and then parse in the code.
Yeah, this has been my instinct, but was curious to hear other experiences. Thanks!
I've been noodling over this exact question this past weekend and I'm glad I stumbled on this discussion in the IH space.
Just to get started (because I have a habit of obsessing over details like this) I'm going to create a separate account for my SaaS project. I think @hschutte's comments make a lot of sense as far as tracking metrics separately. I also like that I can reserve Products for service add-ons.
We are actually working on this solution on servicebot.io .. check out this guide for how we think you should set up products and plans in your Stripe account: https://docs.servicebot.io/subscription-portal/setup-your-stripe-account
Looks awesome, though ended up rolling my own implementation for Knowsi.com
I'm surprised there aren't better solutions like yours direct through stripe.
Nice! Did you also build the portal for your customers to manage their Stripe subscriptions themselves? If so, would you mind telling me how long that process took?
Yeah, it wasn’t that hard. I wrote a small library to interface with stripe, and then a handful of react components handle almost everything. Took about a day total.
I'm using Paddle for my SaaS products, but I guess the answer would still apply.
I've gone with different accounts for each product. Since I have a separate domain for each product, creating unique accounts was not really a problem. I chose this route for a few reasons:
Another thing, for different products you might have different dispute rates, and I'm not sure how this could affect your account if you bundle everything into 1 account.
Hey @hschutte.
Noticed you're a fellow South African, and since I'm in a similar boat to you, thought I'd ask you a specific question: I'm in the process of building a consumer saas product and inevitably I'm evaluating potential payment gateway's. What's been your experience with Paddle so far?
At this point it's looking likely that I go with Paddle or pony up a bit of cash for Stripe Atlas. I'm open to any suggestions from you. Thanks!
Hi @ragtagyusuf!
I've been using Paddle since March 2017. I also had to find a payment provider that catered to South Africa. Unfortunately, the local payment gateways are a million miles behind what's being offered by Stripe and Paddle in my opinion.
I also tried 2Checkout, but in the end, went with Paddle because of:
In the past 2+ years, there have been a few minor issues, but they are pretty quick to respond via email/chat and get it resolved.
So overall I'm pretty happy with Paddle.
Let me know if you have any questions about the integration or anything else related.
Thanks for the info, very informative!
It seems there's no downside to trying out Paddle for me then. And if need be I can go the Atlas route. Will post a follow up update at some point to let you know how it goes.
Thanks.
Ah, seems cool. I should look into Paddle. Thanks!