john-jones_api

[red socket]

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

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

[solid dust]

Hi there! This is hard to debug without any specific requests, can you check the logs in both accounts to see if you can find a request ID?

[vivid bronze]

Hello! I'll check again, stand by.

[vivid bronze]

I'm not sure where I would find a request ID for this as it's done through the UI. There aren't any log entries for this in the connected account log

[cold valley]

So in the browser console, do you see a req_123 id in either the Request section or Headers section anywhere?

[vivid bronze]

Oh ok, found it: req_5jEiSScbf3Efoo

[cold valley]

Yeah I'm not really sure what's going on unfortunately

I don't know a ton about account onboarding

So this is happening in the initial account onboarding flow?

Like you're prompted to add an authorizer when running through it for the first time?

[vivid bronze]

If I'm prompted to add an authorizer the first time, the email is sent, but clicking the email link doesn't seem to do anything. The authorizer request remains pending

Following the email link gives this

[cold valley]

Hm yeah not sure. We have a support team that's better suited to answer account onboarding issues

I'll have to recommend you reach out to support and provide them this info

https://support.stripe.com/contact