#paulo-lacerda_code
sacred pantherBOT
đ 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/1354513763344056351
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
vital sluice
Hi, what does 'This means that stripe will retry to fetchClientSecret to refresh it and no errors will be shown to the user?' mean exactly? You can't claim claim an expired account session, https://docs.stripe.com/connect/get-started-connect-embedded-components?platform=web#configuring-connect
undone cairn
well, we are not the ones that is calling the account_sessions/claim, so I believe that's the stripe library doing it, our question is, when stripe tries to claim it using an expired client secret for some reason, it will then fetch the client secret again, that should return a refreshed one and do what it needs to do again without ever showing any errors to the user?
based on this doc: https://docs.stripe.com/connect/get-started-connect-embedded-components?platform=web#refresh-the-client-secret
we just want to make sure that having some 400 errors for the /v1/account_sessions/claim endpoint it's something we shouldn't worry about
vital sluice
In these cases, you would not need to do anything additional, https://docs.stripe.com/connect/get-started-connect-embedded-components?platform=web#refresh-the-client-secret no. The code you write is fetching the client secret here, fetchClientSecret and on long running sessions we automatically use fetchClientSecret to retrieve a new client secret and refresh the session.
undone cairn
ok, thanks for confirming