#skammerens-datter_api
oblique questBOT
đ 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/1288448016944205824
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
fast hull
Hi, let me help you with this.
Do you have a screenshot of the error?
It should still allow you to onboard though.
azure acorn
I'll get a screenshot from the customer in a couple of minutes. I'll be right back
looking at the error, it might be due to the fact that the onboarding he began was for patrick@halmtorvet9.dk, not info@halmtorvet9.dk - is that the cause?
in which case, shouldn't the onboarding then just accept the email and use that for the account, like all the other details he'll submit for this connected account onboarding? It seems counterintuitive that a field that can be edited cannot deviate from what was inputted a short while ago
fast hull
Yeah, probably makes sense. Feel free to report it to Stripe Support: https://support.stripe.com/?contact=true
azure acorn
Okay, got ya. It seems that might have been the issue. What would be the API call to update the connected account's email?
Seems like that would be the fastest resolve, if they believe they used that other email adress
oblique questBOT
azure acorn
thank you