#martin-_create-accounts
sterile ospreyBOT
👋 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/1287754200352034861
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
golden forge
Hi there!
Can you share the ID (req_xxx) of the failing API request?
https://support.stripe.com/questions/finding-the-id-for-an-api-request
What guide are you following exactly ?
unborn vale
Hi, here is the ID of a failing request : req_x3cYyN7jkzKPTk
I was following the stripe documentation concerning stripe connect : https://docs.stripe.com/connect/onboarding/quickstart
here is a screenshot of my code :
golden forge
You need to remove tos_shown_and_accepted: "true", when creating the account token
You need to keep only individual under account
unborn vale
but then I have this error : This account token does not indicate that the TOS was accepted. Make sure to set tos_shown_and_accepted to true when creating the account token.
sterile ospreyBOT
golden forge
OK, let me do a quick test...
sly sparrow
Hi there 👋 jumping in as my teammate needs to step away soon. In the request that errors, does that error subside if you set business_type to individual when creating the Connected Account?
https://docs.stripe.com/api/accounts/create#create_account-business_type
sterile ospreyBOT
martin-_create-accounts
unborn vale
Hi! business_type isnt supposed to be set in the account creation since im using an account_token. it trigget this error :
Parameter 'business_type' cannot be used in conjunction with an account token. To set this field create a token with the desired changes. Pass the token with 'account_token' in a request without setting 'business_type'. See https://stripe.com/docs/connect/account-tokens#updating for more information.
oh did you ment creating an account with business_type individual without using a token ?
sly sparrow
Oh, no, I meant using them together exactly as that error says you can't, awkward 😅
Seems like we aren't throwing a great error message there. Let me take a closer look here
unborn vale
sure take your time 😄
sly sparrow
Okay, I think it's one of two things. First, can you try setting business_type when creating the Account Token?
https://docs.stripe.com/api/tokens/create_account#create_account_token-account-business_type
unborn vale
Sounds good, now i have : You cannot accept the Terms of Service on behalf of accounts where controller[requirement_collection]=stripe, which includes Standard and Express accounts.
sly sparrow
Gotcha, so that's indicating that you can't accept the tos for non-Custom Connected Account, which is what I thought might be run into next.
Do you need to use Express accounts as part of your flow, or does Custom work better for you if you're planning on collecting onboarding details within your flow?
unborn vale
Let me read exactly what does it change and i'll come back to you 🙂
I think Express would fit my needs better. If I understand well, I need to rework the way my users register ?
sly sparrow
Yes I believe so. It's been a while since I stepped through it personally so I don't recall the exact steps offhand, but you will need to use our hosted onboarding I'm pretty sure then.
The part I'm a little unclear on, is whether you can still use the Account Token -> Account process to start creating the Connected Account, then send your user to our hosted onboarding flow to complete any remaining pieces and acknowledge our tos.
I think this is the fastest path to test from where you are. Take the tos parameter out of the token creation request, then create an Account Link assuming the account creation request works.
If that approach still throws errors, you may need to let our hosted onboarding collect everything then. For that you'd create an empty Account, then create an Account Link to send your user to so they can complete onboarding.
unborn vale
Well that what is started doing by following the doc : https://docs.stripe.com/connect/onboarding/quickstart?connect-onboarding-surface=embedded&connect-dashboard-type=express&connect-economic-model=buy-rate&connect-loss-liability-owner=platform&connect-charge-type=destination
With the client-side part and all but it didnt worked since my account creation failed
Well, I'll keep trying on my own since this is another part of the flow. Thanks for your help and maybe I'll come back for more help (I hope not haha).
sly sparrow
I'm also testing this on my end too in between other threads. I'm pretty sure the error you most recently saw is because you can't accept the tos for Express accounts, they need to provide that consent directly to Stripe. Happy to help any lingering questions though or provide any more guidance I can if things are still unclear.
Alright, my testing is showing that you can't actually use Account Tokens with Express accounts here, Since that flow requires acknowledging the tos for your user, which you can't do for Express Connected Accounts.
So your options are:
- Keep using Express Accounts and switch to our hosted onboarding
- Keep using Tokens but switch to Custom Connected Accounts.
unborn vale
The reason why I'm using token is because my plateform is based in France. If I use the hosted onboarding will it work ?
(sensitive data needs to be encrypted)
sly sparrow
Yup. Tokens exist so you don't have to handle user data yourself, our hosted onboarding flow does the same thing by putting Stripe provided UIs directly in front of your users.
The Account Token restriction would come into play if you were using Custom Accounts. Typically those allow you to provide data direclty from your system to our API, but that's restricted for France.