#evan_unexpected
glad sundialBOT
👋 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/1326652022556065843
📝 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.
- evan_webhooks, 5 days ago, 8 messages
cosmic steeple
Hello, were are you seeing the "something went wrong" message?
grim wadi
after clicking use test phone number and completing the captcha
I did it like 5 times I swear I know what cake is 🙈
I tried with a phone number too
cosmic steeple
Interesting, has this ever worked for you or is this the first time you are testing with it?
grim wadi
This is the first time I'm testing
cosmic steeple
Will see if I am getting this in test mode as well
grim wadi
I have set up accounts (in test mode and prod) using the dashboard and sharing the account onboarding link - this does the email auth flow
this is the first time I'm attempting setup with the account_links api
logger.info('creating stripe connect account');
const account = await stripe.stripe.accounts.create({
type: 'express',
email: identity.userEmail
});
logger.info('created stripe connect account', { accountId: account.id });
await supabase.updateCustomer(identity.customer.id, {
stripe_account_id: account.id
});
const referer = args.headers.referer as string;
const accountLink = await stripe.stripe.accountLinks.create({
account: account.id,
type: 'account_onboarding',
refresh_url: referer || 'https://app.asdfasdf.com/settings',
return_url: referer || 'https://app.asdfasdf.com/settings'
});
logger.info('Account link created', { accountLink });
return {
status: 200 as const,
body: { session_url: accountLink.url }
};
my code fwiw
cosmic steeple
Gotcha, thank you. Testing this on my side now. One quick question, if you look at your browser's dev tools can you see if we log an error in the dev console when this happens?
grim wadi
[connect-flows.vendors~accept_invite~cancel_recovery~default_redirect_uri~durable_connect_onboarding~durable_custom~03f88ee9.f0e483d129.min.js:5
POST https://connect.stripe.com/ajax/connect/sessions/register_user/auth_attempt?include_only%5B%5D=attempt_id%2Cexpress_2fa_sms_outage 400 (Bad Request)](https://connect.stripe.com/ajax/connect/sessions/register_user/auth_attempt?include_only%5B%5D=attempt_id%2Cexpress_2fa_sms_outage%20400%20(Bad%20Request))
2fa_sms_outage is in there somewhere? just a service down temporarily?
cosmic steeple
This works for me on my acount. Can you create a new account link and then send me the account ID of your platform account? (acct_1234)
I can try reproducing on a link that you created to see if that also produces this error for me. The links are used up if Discord tries to preview them, so I can just pull the latest test one from your account logs and try that if you create a new one in test mode
grim wadi
whats the easiest way to find my platform account id lol
cosmic steeple
If you run the retrieve account call with no parameters that will retrieve your own account https://docs.stripe.com/api/accounts/retrieve
there is also a dashboard page, can link in a sec
cosmic steeple
Thank you checking in to that
Hmm that link worked for me. Have you tried in multiple browsers or on multiple devices?
cosmic steeple
Another window of the same browser?!
grim wadi
Im running on localhost with a chrome debugger through VS code
running a normal chrome profile works!
cosmic steeple
Nice! If this keeps up, you may have to pass things off to the normal browser and then when things complete go back to the final redirect page in your debugger one. You can also report this to our support team and we may be able to look in to and fix this, though I can't guaruntee if/when we would https://support.stripe.com/?contact=true
grim wadi
thanks for the help!
cosmic steeple
Of course! Glad we could narrow down the cause
cosmic steeple
Hmm, and that was on the browser window where you could get past the phone number piece? It may be worth trying in incognito/private mode to make sure it isn't a browser addon
