#scastrect-connect-oauth
1 messages · Page 1 of 1 (latest)
We recommend not using OAuth at all since we deprecated it a while ago and you should create the account straight in the API instead.
@stark mist ^ does that make sense? Do you have a follow up question?
I get the StripeUserId along the OAuth token with Stripe API Connect.
My Objective is to let Stripe users to consult stripe information from my website. So OAuth seems the way.
So after OAuth you get the id acct_123 and that's all you need
This acct_XXXX will work indefinitly/forever?
for as long as the account stays connected
Ok. So no need to use the refresh_token?
correct, you could store it but it's only needed it you were to "leak the access token" which you won't need if you don't use/store the access token either
+The way to disconnect the account is through the stripe webapp?
you, as the platform, can also do https://stripe.com/docs/connect/oauth-reference#post-deauthorize