#ben_api
fallen ridgeBOT
👋 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/1313495438128844821
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
vernal jungle
hi there!
dense cypress
Well hello there
vernal jungle
based on the error message, it doesn't seem supported for this type of connected account.
dense cypress
yeah i think i can see this in th docs, it looks like this is only possible when creating the account but not after, unless its a custom account which i assume is if we were on a diff contract.
On the notion of creating, currently we redirect to stripe, account is configured then redirects back with a oauth code etc.
Is it possible to do the creation completely programmatically via the api? Is it recommended?
fallen ridgeBOT
vernal jungle
Is it possible to do the creation completely programmatically via the api? Is it recommended?
that's the recommended approach: create the account with the API and redirect them to the onboarding.
dense cypress
oh? OK we certainly arent doing that! So first create an account via the api, then redirect to onboard with said account?
I think at the moment we just redirect them and they either log in or createn account.
If we do as you suggest, how would deal with situations where someone already has a stripe account?
rocky shard
someone already has a stripe account
What do you want to happen in such situation?
dense cypress
well theres what i want to happen and what will have to happen 🤣 i guess we will need to let them connect . Although now i am saying this, we wont be letting them import anything i dont think as we have no idea what type of products they have may have created.
I think if we forced them to use a new account, we may run into problems with adoption as they would have to set up an entirely new stripe account and go through validation etc.
rocky shard
Generally we recommend creating new accounts specifically for your application, to not mix up the data.
I am not familiar with all aspects of the onboarding process, but you might be able to reuse the account, or at least registration documents.
I suggest you to try it in Test mode and see what happens: https://docs.stripe.com/connect/standard-accounts
dense cypress
so you are saying there is a way to attach an already existing, normal stripe account (standard) to our platform by first creating a connect account and then linking them?