kotireddy_code

[strange mica]

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

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

[severe elk]

hello! do you have a publicly accessible site which we can access to take a look?

If you don't can you share the request ID for which you saw that error? I'm assuming you saw that request in the network tab of developer tools - the request ID will be in the headers and it'll have the prefix req_

[tawny pier]

Hello Alex, thank you for the reply. Here is the request id req_zdJRbAIqTtkGMr.

Our demo website is https://songbriteweb.earbor.com. We just moved the onboarding related changes and they should be done in around 5 minutes. You can use the following username: [e-mail] and password Ajay@3339 to login to the website. Once you login, you can go to Referral/Payout tab and enter the button Complete Account setup to see the issue.

Here is the screenshot of the error message we are getting

[severe elk]

okay, gimme a minute to try!

I was able to get to this page though

^ is the hosted connect onboarding page (not the embedded flow), so maybe this isn't the right flow?

[tawny pier]

My apologies Alex for the wait. Unfortunately the changes did not reflect yet.

Can I get back to you after they build’

We used stripe-hosted onboarding before and tried to embed the iframe but stripe blocked us from doing so. We wish to use embedded onboarding instead as we wish to keep the users in the app.

[severe elk]

Sure, although we can workaround that too. The requests to /v1/account_sessions/claim are being made by acct_1BTUDGJAJfZb9HEB. But I don't see any recent requests to create the account session on that same account. The most likely reason is that you're creating the account sessions on an entirely different account, or you're not passing in the value you think you are.

A couple of things you can do here :

• Find the corresponding request ID for where you created the account session and we can take a look at which account you're creating it for Since the request to create the account session is from your server, you'll likely need to log the corresponding request id : https://docs.stripe.com/api/request_ids
• Also log the corresponding client_secret which you're using to validate that it's correct

[tawny pier]

Hello Alex, thanks for your patience. The changes have reflected on the demo website now. Would you be able to take a look?

[severe elk]

you're creating the account sessions on a different account i.e. acct_1SAr9DDSOElcPVh7 - this is your Sandbox account

you need to use the secret key and publishable keys from the same accounts

i.e. there's two options here, either use the secret key from acct_1BTUDGJAJfZb9HEB (to match the publishable key which is currently from acct_1BTUDGJAJfZb9HEB), or else use the publishable key from acct_1SAr9DDSOElcPVh7 (so that it matches the secret key from acct_1SAr9DDSOElcPVh7 which you're currently using to create the Account Session)