#bensif88
1 messages · Page 1 of 1 (latest)
Hello bensif88, we'll be with you shortly! 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.
• ben-connect-oauth, 1 days ago, 13 messages
• ben-checkout-pricingmodels, 6 days ago, 49 messages
• bensif88, 7 days ago, 29 messages
• ben-checkout-variousproducts, 7 days ago, 47 messages
Hi there 👋 trying to make sure I'm understanding correctly, you have a Connect Platform, and you're trying to disconnect a Connected Account from it?
If so, are these Connected Accounts that you created, or did you allow your users to bring their own account and connect to your Platform via OAuth?
Hi, so we are letting users bring their own account if they have one, otherwise create one
( i am still not sure letting them bring their own is wise but hey ho)
Gotcha, if a user brought their own account and authenticated with OAuth, then you should be able to revoke that access using the approach shown here:
https://stripe.com/docs/connect/oauth-reference#post-deauthorize
For accounts that you created, are you working with Standard accounts? or are they Custom/Express accounts instead?
standard only
Hm, alright, I need to double check with a teammate what you can do about those. I know you can't delete them, but I also don't think rejecting them is the right action either. I'll double check that and get back to you.
ok cool, thanks Toby. We are doing all the connection with oauth, so i dont know if the user doesnt already have an account, if that counts as us crearting it or not
Ah, if everything is happening over OAuth, then that process should be all you need for deauthorizing. But let us know if that seems to not be the case at any point.