#deepeshkhanal_api
teal daggerBOT
👋 Welcome to your new thread!
⏲️ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
⏱️ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
🔗 This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1298997770446962751
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
tough finchBOT
delicate nimbus
Additional Consideration
In addition to package subscription, clients can also charge each branch some amount for each active users in the branch. Similarly, platform can also charge clients some amount for all the active end users. Each package created by client/branch or platform can have weekly, monthly and annual plans.
Recurring payments and subscriptions should be handled on each level. There can also be trial periods and grace periods for each package.
One of the major consideration is that, the whole platform is white-labelled. So, each level of hierarchy only knows one level above them exists and no further.
Implementation Methods
I also thought to create hierarchical connected accounts. Platform -> Client -> Branch so that the platform has clients as connected account and branch can be connected accounts of client. This hierarchical consideration might be easier but I have not gone into details of this. How would this look like in terms of integration, webhooks, etc?
Third approach would be to not create connected accounts at all and handle all the products, subscriptions, payments by the platform to the client/branch. This might be too complex to implement as well.
tough gyro
Hi 👋 this isn't easily done in Stripe. We don't support nesting Connect integrations like this.
delicate nimbus
Hi toby. Thanks for your reply. What would you suggest for this integration
tough gyro
The only thing coming to mind is to onboard every party as a Connected Account to your Platform, and then try to add your layer abstractions to cover that up as best you can. It won't be easy and everyone will know about your Platform.
delicate nimbus
I have tried to use Stripe connect and create connected accounts for client and branch in the main platform account.
The package created by each of them will be created in their own connected account and subscription will go through the connected accounts itself.
But, hiding the platform details is a problem which I am not able to do. Also, the onboarding process is quite heavy.
One approach without connect maybe is this but everything should be managed by the platform account =>
Third approach would be to not create connected accounts at all and handle all the products, subscriptions, payments by the platform to the client/branch. This might be too complex to implement as well.
tough gyro
You're talking about a flow with 4 tiers of hierarchy, every solution is going to be complex. I don't think there is any avoiding that.
The problem with storing everything in your Platform account without Connect, is you have no way to pay funds out to your clients/branches/users within Stripe.
delicate nimbus
is there a possibility that client/branches can simply put their credit card details without connected accounts and the platform can calculate payments and process it to their card. we will only have platform stripe account to do that.
tough gyro
What do you mean by process it to their card? Like send funds to the credit card from your Stripe account? If so, no, that is not possible. It's not possible to send funds from your Stripe account to a third-party without using Connect.
(It's also not possible to send funds to a credit card with Connect, only bank accounts and debit cards)
delicate nimbus
sorry, i mean debit cards not credit cards 😄
so, there is no other option than to use connected accounts for each party involved
tough gyro
Correct
delicate nimbus
Thanks toby. I think I got the info I required. Thanks for the clarification.