#Kapuetze
narrow jetty
Hi 👋 there is an older OAuth flow that allows people with an existing Stripe account to connect that to your platform, but it isn't typically recommended anymore.
https://stripe.com/docs/connect/oauth-standard-accounts
We don't recommend it because of change that was made, where now some Connected Accounts are locked to being associated with a single Platform. If one of these accounts tried to connect to your Platform with OAuth, they would have a new account automatically created for them rather than connecting the existing one. It is typically easier to always create new accounts for this reason rather than trying to connect existing ones.
lime quest
The reason I am asking is that we are migrating from charges to stripe connect. Our customers already have stripe accounts. Would they have to set up all of their settings again if they create a new account?
narrow jetty
I'm not sure I'm following, migrating from Charges to Connect isn't something I've heard of someone doing before. Are you moving from Charges to Payment Intents, and also implementing Connect at the same time?
lime quest
Exactly, sorry for the confusoin
So yeah, technically we are just moving from direct integration to connect
So the question is: Will these existing customers be able to use their account that they've been using for years or will it be a new account they have to set up?
narrow jetty
By direct, do you mean your users used to created Stripe accounts, provided you with the API keys for those accounts, which gave you the necessary access to those accounts?
lime quest
Yes
narrow jetty
Gotcha, okay, then maybe. Do you know what type of Connect integration you're going to be setting up, what type of Connected Accounts and what charge structure you're going to use?
lime quest
We're looking to use standard accounts. And I am not exactly sure what you mean when refering to "charge structure"
We don't want to payout the customer if thats waht you are asking. We want them to take care of their money just like when they directly used their own credentials
narrow jetty
With Connect there are three different types of Charge Structures:
https://stripe.com/docs/connect/charges
Direct charges, happen direclty on the Connected Accounts, typically the best option when working with Standard Connected Accounts, and the Platform's application fee is sent from the Connected Account to the Platform.
Destination charges, payment happens on the Platform, and then proceeds are sent to the Connected Account.
Separate Charges and Transfers is similar to Destination Charges, but with more steps.
If you're working with Standard Connected Accounts, then it is a possibility that your customers will be able to reuse their existing Connected Account. The guide I linked initially will walk through what that flow looks like. Again, it is possible that there will be cases when a new account is created rather than the existing one being created, there is no way to predict when this will happen so your process will need to be prepared for both possibilities.
lime quest
I understand. We are going to use direct charges. So to confirm: The only way to make this possible is by using the oauth described here: https://stripe.com/docs/connect/oauth-standard-accounts instead of using this https://stripe.com/docs/api/account_links
olive peakBOT
narrow jetty
Correct
lime quest
Ok, thank you for your time!
narrow jetty
Any time!