#ale_api
mellow eagleBOT
👋 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/1415183937990426655
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
⛔️ Stripe developers have stepped away for a short while
Please leave your questions here, and we’ll respond as soon as we're back! If you need help urgently, you can contact Stripe support for help.
calm gorge
Hi @tropic isle Can you tell me exactly what didn't work? Do you have the detailed error message and request ID?
tropic isle
I don't see any logs on my end related to OAuth calls though, that's why I couldn't add one, sorry. I am not ruling out a bug on my end, but we have new orgs connecting to our Stripe platform account, even as far as 2 days ago, but this customer that we met them today, I saw them do what we always instruct them to do, which ends up in me calling Stripe via the dotnet OAuthTokenService and even then, I can't see their account from mine. I am sorry if I am raising a case here without much info, but I don't have much to go on, I can give you the two account Ids assuming that's not confidential information
calm gorge
Yes, account ID isn't a sensitive data. Can you share with me your account ID as well as the connected account's ID?
tropic isle
My account id: acct_1D2T4wAbHJNhsv2V
Won't connect account Id: acct_1R1IyEDxXhGd1s78
calm gorge
Ok, I found both account.application.deauthorized and account.application.authorized events occured at a very shot interval (a few seconds). And this incidate that the platform sent /oauth/token requests multiple times with the same auth code, which resulted in account disconnection.
https://docs.stripe.com/connect/oauth-reference#post-token-request
Per OAuth v2, this endpoint isn’t idempotent. Consuming an authorization code more than once revokes the account connection.
tropic isle
I see, so it would seem that we have a bug that is spamming Stripe when connecting an account, and this can cause Stripe to disconnect us as soon as connecting?
calm gorge
Yes. that's possible
tropic isle
I see, that's probably enough for me to look into it, I am guessing this is more a race condition, since it's working in some situations?
calm gorge
Yes. it's a common problem that I heard from many users.
tropic isle
Thank you, this gives me something to look at! Thank you very much!