#manic-silly-billy_api
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/1268726082555609098
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
Hi there, the acount link can only be used once. It looks like the link already consumed when you try to access it, and that's why it takes you back to the return_url which I believe, is your home page.
Are you shareing the account link URL through an IM like discord or slack?
Hey hey
So I think I misunderstood, the OAuth link is what I should use if I need something that doesn't need to be dynamic and individual to the user right?
I was trying to create account links on the server and I think it was over complicating things
When I can just use the OAuth flow
No, Oauth flow is already deprecated, and you should use /v1/accounts API
Bruh what? You all literally push it in the docs
https://docs.stripe.com/connect/oauth-reference#get-authorize-response
Take this down if it's depreciated
People wouldn't waste time setting things up
Also wait you literally have a whole portion on the dashboard for it
Sign in to the Stripe Dashboard to manage business payments and operations in your account. Manage payments and refunds, respond to disputes and more.
That's for legacy integration. For new integration I'd highly recommend using the accounts API instead of OAuth.
Thanks for the feedback, and I'd ask the doc team to put a legacy warning on the OAuth integration page
Yeah I mean without telling me what the accounts API actually provides over legacy I'm going to ignore that advice because my needs are basic atm. I just need onboarding.
Extra feedback, you should include this in the docs^. Because people usually like OAuth for the simplicity and most people would opt for Oauth over anything that requires more legwork.
You should segment them less so by legacy vs. new, and more how you have Express and Standard.