#nikoschns_best-practices
distant minnowBOT
đ 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/1361299597959364771
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
rapid raptor
The recommendation is to create a new Account object via the API and onboard them via an Account Link
real plinth
Okay, so essentially, they will have two accounts. The 'normal' Stripe account that they are the only ones to have access, and the Connected Account, that I can also manage. Is that right?
rapid raptor
Yes
real plinth
And a final (maybe silly) question; is it okay, if I do the process you suggested via the Dashboard? E.g. create a Connected Account in the Dashboard, get the link and send it to my potential customer? or the API offers a significant advantage?
rapid raptor
No real difference, no. The only thing worth mentioning is that depending on how you send the link to your users may invalidate it. They're one-time use only and some email clients, etc will mark them as used
real plinth
Oh I didn't know that. Thank you for sharing it. So what's the best practise for sharing Stripe links?
rapid raptor
Well generally most people create them via the API in their application and redirect the user straight to the URL
distant minnowBOT