subin_error | Stripe Developers | Page 1

feral bladeBOT Apr 22, 2025, 9:07 AM

#

👋 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/1364165827435298917

📝 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.

subin_error, 48 minutes ago, 8 messages
subin_error, 4 days ago, 32 messages
subin_error, 5 days ago, 14 messages

#

tranquil tulip Apr 22, 2025, 9:08 AM

#

We're implementing the OAuth flow for our Stripe Connect integration. We're observing a duplicate redirect from Stripe after a successful authorization.

Here’s what’s happening:

The first redirect comes in with the authorization code (as expected).
We then exchange the code for access/refresh tokens.
Afterwards, we make a request to our client’s site to store the tokens.
If this request takes longer than 60 seconds, we see a second identical redirect from Stripe to our server.

The second request has the same parameters and a Referer header of https://marketplace.stripe.com/.

Can you please confirm:

Is this retry behavior expected when the initial redirect doesn’t respond quickly?
Is there an officially recommended timeout for this redirect handler?
Is there a way to prevent Stripe from retrying or a webhook-based alternative?

Here’s our handler setup for your reference:

We’re using a custom PHP backend (not WordPress).
We respond only after completing a cURL request to the client site.

#

the installation link is only clicks once.

#

if the response stripe sent with in 60 sec i dont get the second response.

vernal basin Apr 22, 2025, 9:14 AM

#

If this request takes longer than 60 seconds, we see a second identical redirect from Stripe to our server.
Can you share more details about this ? do you have a screenvideo recording ?

tranquil tulip Apr 22, 2025, 9:20 AM

#

i can share the response

115.245.222.92 - - [21/Apr/2025:11:43:32 +0000] "GET /wp-json/wt-stripe/v1/oauth?code=ac_SAe21H7Bc53fsmYLq5rppu7AYO5JyHjY&user_id=usr_MTMsOxAahaiTvo&account_id=acct_1MgkSrCxZV7Ws7XN&stripe_user_id=acct_1MgkSrCxZV7Ws7XN&state=aHR0cHM6Ly93b3JkcHJlc3MtMTA0NjE5OC01MzY1ODYxLmNsb3Vkd2F5c2FwcHMuY29tLz93Yy1hcGk9d3Rfc3RyaXBlX29hdXRoX3VwZGF0ZSZtb2RlPXRlc3QmbmFtZT1laF9zdHJpcGVfcGF5bWVudF9nYXRld2F5 HTTP/1.0" 302 492 "https://marketplace.stripe.com/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36"
115.245.222.92 - - [21/Apr/2025:11:42:32 +0000] "GET /wp-json/wt-stripe/v1/oauth?code=ac_SAe21H7Bc53fsmYLq5rppu7AYO5JyHjY&user_id=usr_MTMsOxAahaiTvo&account_id=acct_1MgkSrCxZV7Ws7XN&stripe_user_id=acct_1MgkSrCxZV7Ws7XN&state=aHR0cHM6Ly93b3JkcHJlc3MtMTA0NjE5OC01MzY1ODYxLmNsb3Vkd2F5c2FwcHMuY29tLz93Yy1hcGk9d3Rfc3RyaXBlX29hdXRoX3VwZGF0ZSZtb2RlPXRlc3QmbmFtZT1laF9zdHJpcGVfcGF5bWVudF9nYXRld2F5 HTTP/1.0" 302 376 "https://marketplace.stripe.com/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/134.0.0.0 Safari/537.36"

Stripe App Marketplace

Stripe Apps integrate all the tools you use to run your business

vernal basin Apr 22, 2025, 9:23 AM

#

If this request takes longer than 60 seconds, we see a second identical redirect from Stripe to our server.
Ok so if you don't send a response to Stripe in 60sec, stripe will call your reditec endpoint again ?

tranquil tulip Apr 22, 2025, 9:28 AM

#

we think so.
if the process take more than 60 seconds i get the error.

#

because of the second response.

i checked the reference i the header and it says "https://marketplace.stripe.com/".

so the two identical responses from stripe?

#

i dont find anything regarding in articles.
So i dont find what go wrong?

vernal basin Apr 22, 2025, 9:31 AM

#

Yes, it's like a retry mechanism

#

Is there a particular reason why your integration don't answer in 60sec? it seems like a hudge amount of time to response

tranquil tulip Apr 22, 2025, 9:31 AM

#

ok so is there is any article

tranquil tulip Apr 22, 2025, 9:32 AM

#

vernal basin Is there a particular reason why your integration don't answer in 60sec? it seem...

in some client site are with lower server performance so they may need bit more time to connect with our seerver.

#

currently we keep the time out for connection as 45 sec but for some customers, they unable to connect server within this time .
so we neeed to incease the time out .
which introduce the error.

#

So first i need to conform that there is any retry mechanism in stripe which may cause the duplicate response.
Also can i able to change this from stripe dashboard ?

feral bladeBOT Apr 22, 2025, 9:56 AM

#

high urchin Apr 22, 2025, 10:00 AM

#

No, there's no way to configure/disable the retry mechanism. Why are you integrating with OAuth anyway? It's not recommended for new platforms

tranquil tulip Apr 22, 2025, 10:03 AM

#

what you mean by this?
It's not recommended for new platforms

high urchin Apr 22, 2025, 10:05 AM

#

It's deprecated, as it says right there on docs:

OAuth is not recommended for new Connect platforms. We recommend using Connect Onboarding for Standard accounts instead.

#

You should be using the API directly to create accounts and onboard them: https://docs.stripe.com/connect/standard-accounts

Using Connect with Standard connected accounts

Use Standard connected accounts to get started using Connect right away, and let Stripe handle the majority of the connected account experience.

tranquil tulip Apr 22, 2025, 10:06 AM

#

please explain it bit more?

#

OAuth was suggested by stripe team

#

we are using it in a wordpress plugin

high urchin Apr 22, 2025, 10:09 AM

#

Who is 'Stripe team'? Not sure why that would be recommended. If you're building a plugin, you should be using a Stripe App: https://docs.stripe.com/stripe-apps/plugins/oauth

Migrate a plugin to an OAuth 2.0 app

Migrate your existing plugin to an OAuth 2.0 authentication path using Stripe Apps.

tranquil tulip Apr 22, 2025, 10:13 AM

#

this is what we are using

#

https://marketplace.stripe.com/apps/webtoffee

WebToffee | Stripe App Marketplace

Learn about the WebToffee app for the Stripe payments platform

high urchin Apr 22, 2025, 10:16 AM

#

So it's this part of the OAuth connection: https://docs.stripe.com/stripe-apps/api-authentication/oauth#obtain-access-token

OAuth 2.0

Use the industry standard OAuth 2.0 to authenticate requests to the Stripe API on behalf of your users.

#

In future I'd recommend be really crisp about that docs/guides you're following, what it is you're building. We can't really help you very well if we're unclear about what exactly you're doing

tranquil tulip Apr 22, 2025, 10:19 AM

#

ok what about the isuue we encounter?
is there is any data you need?

high urchin Apr 22, 2025, 10:26 AM

#

I think we've explained that problem, right? You need to ack the callback within a minute, or handle the duplicate calls

tranquil tulip Apr 22, 2025, 10:30 AM

#

ok
i have some confusion because in earlier response not in this thread i got a replay like stripe only sent response once.
so just need to conform it.

is there is any article regarding this?

high urchin Apr 22, 2025, 10:31 AM

#

No

#

I think given the long-running back and forth here I'd recommend you write in to our team directly about this issue and we can work 1:1 there to get a resolution. There's too much context lost here in Discord so it makese keeping up with previous conversations dificult

#subin_error