#hatvaccuum_sandboxes-account-session
1 messages ยท Page 1 of 1 (latest)
๐ 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/1326949977900978196
๐ Have more to share? Add more details, code, screenshots, videos, etc. below.
here's a stripe insiders forum post if relevant! https://insiders.stripe.dev/t/stripe-connect-embedded-components-not-working-with-sandbox/4035
Hey all! My team is adopting sandboxes for our app which uses stripe connect and the connect embedded react components (Get started with Connect embedded components | Stripe Documentation). Previously, we have the embedded components working with our stripe api keys for test mode. Recently, we tried switching these test mode api keys for sandbo...
Hi ๐
Can you describe exactly what it is you are doing here? Share the API requests you make (providing API request IDs would be amazing) and the responses you get in a step by step fashion
Hey! Sorry for the delay! The api request being made is
POST /v1/account_sessions
and the response we get is
400. Reason: No account session with that client secret was found. Was the account session created using a secret key for a different account?
I'm working on getting you some api reqeust id's now!
Are all the objects you are attempting to use ones that exist in the Sandbox?
I am just now discovering that I did not swap out my old stripe publishable key... which would make total sense why things are not working... Let me confirm this is the issue (sorry for the inconvinience!)
^ works now!!! Agh so embarassing, but thank you so much for everything!
Woohoo! ๐
I'm glad it was an easy fix. Sometimes it just takes reviewing your code with someone else asking questions to find the solution