#joe_standard-oauth-state
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/1226926186672947222
๐ 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.
- joe-s_api, 24 minutes ago, 19 messages
A working test account number is acct_1O81DDLAy35cMRlM
Hi ๐
When you say Auth 2.0, is there a Stripe doc you are following?
Oh, you mean OAuth with Standard Accounts
I'm continuing a support chat from here: #1226926186672947222 message
Yes we close idle threads, we provide real time chat support here so we don't leave threads open for long if we don't get a response
This was something that was broken but we have addressed the breakage. Did you need more details?
I know, it's pretty annoying though. Sometimes it takes a while to get required info and I'm also trying to do a million other things ๐ญ
We were experiencing the issue just last week, has it been addressed since then?
On 4/4/2024
My colleagues attempted to reproduce the error and, when they completed the OAuth with redirect, we all saw the state value retained in the URL
I just completed a test using a colleague's OAuth URL and I can see the state value present.
This has occurred for two of our users, others seem to working correctly. Can you share when the issue was fixed?
Hmmm... it looks like the fix was merged and deployed in March. So you're still having issues?
Yes, but only for these two accounts so far.
When you say "these two accounts" do you have account IDs I could reference?
Yes, I'll get them.
It looks like I only have the response url, can you use the token from that? ac_Prx9jchiOXeTuUg3n3FpT4xPSnIgauED, ac_PsKE50Y774FC9EaymZubIUtXZYzXkGTh
If not I'll need to reach out to the users as their account numbers were never recorded.
Hmmm.. I don't think so but I can share these with the team that handles this flow. And what happens when you attempt to onboard the test account you shared using Oauth?
When you onboarded acct_1O81DDLAy35cMRlM? Did you get the state variable returned properly?
I'm reaching out to the users to obtain their account numbers. When using the test ID the state was returned properly
Got it. Okay then those account numbers will likely be important to troubleshooting this issue since it seems like the state of those accounts are a factor
Ok. How can I reference these chats later so I'm not starting from square 1 every time I have an update?
Honestly, troubleshooting this on Discord is just not a good fit for this kind of problem
I recommend writing in to Support here: https://support.stripe.com/contact
Reference that you were already chatting with us on Discord and provide as much detail as possible.
This will allow us to keep all of the context together.
Discord is really only well suited, and intended for, helping developers coding Stripe integrations with specific API/code issues. This appears to be related to account configuration and I don't have the permissions or expertise to handle it
Ok, I was try the discord channel because the Stripe support site mentioned it and the standard support channel chat has been incredibly unhelpful; I'm still waiting for them to reply to a query I had over two weeks ago.
Yeah, I would keep pushing on Support by using the form to send in a new email and be as detailed as possible about what you are experiencing.
I'm sorry for the poor experience but unfortunately I don't have the tools, permissions, or experience to assist with account related problems. By pushing and providing as clear details as you can, you will help the first level support team route your request to the people who can actually help.
Ok thanks