#mecha-chocobo_error
vocal bearBOT
đź‘‹ 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/1405542914045771857
đź“ť Have more to share? Add more details, code, screenshots, videos, etc. below.
inland urchin
Hi, Express oauth has not been a recommended pattern for some time, several years now. Is this an existing integration that is encountering issues? Or, are you trying it out new? When was the last time it worked?
snow ermine
It is an existing integration. We just noticed the error in our test environment yesterday, but I don't have a solid time for when it started failing.
inland urchin
What is your account id?
We're in the process of deprecating it as it no longer recommended: https://docs.stripe.com/connect/oauth-express-accounts
Caution
OAuth isn’t available for new Connect platforms. For new accounts, use Accounts API with Express instead. Extensions shouldn’t use Express OAuth, as extensions can’t connect to existing Express accounts. If you need access to OAuth for Express accounts, please contact support.
You would have likely recieved an eamil from Stripe about this
snow ermine
I have not received any emails, but I'll check with some coworkers to see if they did.
snow ermine
ok, thanks
inland urchin
Sure