#maurice-lafeve_error

1 messages ¡ Page 1 of 1 (latest)

scenic flintBOT
#

👋 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/1384102013796749354

📝 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.

solar agate
#

If I set the business_type when creating the token, the account creation works. However, when I return to the onboarding (embedded component), I see that the business_type is a company. If I try to modify it, it does not offer me the individual type. In a previous ticket, an administrator told me that I had to indicate the business_type when creating the account. But when I do this, I get the error that appears

#

you can show the result with this account : acct_1RaZ12PdmfQ1Cdhm

humble thicket
solar agate
#

request for account create : req_PUVVuJ3CY706tZ
request for token create before account create : req_yINENWsbZZiiwN

scenic flintBOT
vapid ore
#

hello! fyi i'm taking over for my colleague here - fyi the server is a little busy atm so my response might be a little slow

vapid ore
#

ok sorry about that delay - looking at this now

#

it looks like you're already setting the business_type in the account token here - have you tried just removing it from the second request?