#subin_error
gilded shaleBOT
👋 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/1362047680724992113
📝 Have more to share? Add more details, code, screenshots, videos, etc. below.
tough field
Hi 👋 I'm not sure what you're trying to ask, but that error is thrown when the authorization code you're trying to use has already been consumed.
midnight remnant
can you able to check it uif i provide the account id?
acct_1Pza6dGv07M9Hyxh
tough field
Check what? This sounds like an integration within your OAuth flow. What debugging have you done so far to ensure you aren't trying to reuse a previously consumed authorization code?
midnight remnant
we only use once the authorization code.
on connection stripe redirected to our server with the auth token and we send it for refrsh token,
the end point handling the this part is only accessed by the redirection url in the instalation link.
so there is no athor way autorization code while sent to this end point where authorization code is passed to get the access token, refresh token, etc
'grant_type' => 'authorization_code',
tough field
Are you caching codes at all? Are you sure when you receive a new code you're using the new one? (Sorry if these questions sound silly, but I don't have visibility into what you're doing so I only have the context that you share with me)
midnight remnant
yes
i get the authorization code from the response from stripe.
so only i use same code if the same code is sent by stripe
can you able to check fir the account if the same authorization code is passed twice for refresh token?
iam not sure you have the authorization for that.
tough field
Not really. Do you have logs from your side showing you received the same code twice?
midnight remnant
we dont log this kind of the datas.
tough field
Gotcha, next steps here are probably to add some code to your flow for debugging purposes then. Track what codes you're receiving, and ensuring they're the ones you're using.
midnight remnant
on i click the connect button
the link is https://marketplace.stripe.com/oauth/v2/authorize?client_id=ca_Pl5sdRX9ZIbMhFni2PDjsnkMEERxD3Ye&redirect_uri=https://verify-stripe.webtoffee.com/wp-json/wt-stripe/v1/oauth&state=aHR0cHM6Ly9yaWRnZWJpb21lZC5jb20ubXkvP3djLWFwaT13dF9zdHJpcGVfb2F1dGhfdXBkYXRlJm1vZGU9dGVzdCZuYW1lPWVoX3N0cmlwZV9wYXltZW50X2dhdGV3YXk
and the stripe redirect to our server.
so there is no direct connection with the end point which handle the authorization code,
only stripe redirect to the endpoint
