#joe_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/1227029852100759603
đ 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_standard-oauth-state, 5 hours ago, 35 messages
- joe-s_api, 7 hours ago, 19 messages
Hey @thin helm it looks like you were here earlier today asking about this and redirected to our support team and I think that's the best approach to get actionable support on this issue: https://support.stripe.com/contact
The last agent asked for the account numbers we were experiencing issues with.
Sure but now for follow ups I recommend working directly 1:1 with our support team. We can't really debug this further here unfortunately. So you can contact support https://support.stripe.com/contact and they will be able to investigate this further
joe_oauth-state