#mattiaferrari_docs

1 messages · Page 1 of 1 (latest)

austere creekBOT
#

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

📝 Have more to share? Add more details, code, screenshots, videos, etc. below.

polar galleon
#

Maybe i am a little confused, was there an even older version of stripe connect that i am basing my integration on?

#

Is "Stripe connect standard" a terminology referred to stripe connect v1?

brazen pecan
#

Hi there! It depends on your use case, but I would say many platforms are fine using Accounts v1. Accounts v2 solves a somewhat specific problem where the account can be treated as both an account and a customer. This is described at the beginning of the doc you linked:

As a Connect platform, you enable your connected accounts to accept payments. You can also accept payments from your connected accounts when they purchase products or subscribe to your services. In the Accounts v1 API, associating these purchases and subscriptions with your connected account requires a separate Customer object that you manually associate with the connected account’s Account object.

The Accounts v2 API allows you to create one Account object that supports all interactions with your connected account, so you don’t need to create and track separate Customer objects.

Again, many platforms are using Accounts v1 without issue. I would say in my experience that Accounts v2 are more complex to setup and understand, so it depends on what you want to prioritize

polar galleon
#

If i plan to use buy-rate do i need connected accounts v2?

#

Another question, is connect v2 publicly available from this end of February

#

?

#

Hi there! It depends on your use case, but I would say many platforms are fine using Accounts v1
Ok but from the docs i see that the page about stripe connect v1 says that it is now considered legacy

brazen pecan
#

Is "Stripe connect standard" a terminology referred to stripe connect v1?
There isn't a Connect v1, in this case you are referencing Accounts v1 and v2, which changes the behavior of the account objects themselves. You can read more in this guide:
https://docs.stripe.com/connect/accounts-v2/saas-platform-payments-billing

If i plan to use buy-rate do i need connected accounts v2?
This guide shows the fee structure, both Accounts v1 and v2 are supported
https://docs.stripe.com/connect/direct-charges-fee-payer-behavior

#

Ok but from the docs i see that the page about stripe connect v1 says that it is now considered legacy
Can you tell me the specific docs and section you are seeing this?

polar galleon
#

Even the sidebar says legacy

brazen pecan
#

Got it. We have no plans of deprecating Accounts v1, but as you say our docs recommend Accounts v2 for new platforms.

Another question, is connect v2 publicly available from this end of February?
Accounts v2 is available now, but there may be certain features that are still in development, as it is relatively new

polar galleon
#

Ok so it is new features indeed

#

Another question not strictly related, before accounts v1, was there an even older legacy way to create connected accounts from your knowledge?

brazen pecan
#

Yeah, from my understanding the first version of Connect (it wasn't called Connect then) was using OAuth to link one Stripe account to another

#

That flow is now deprecated

polar galleon
#

Ok thanks for clarifications, now are there some way to migrate from account v1 to account v2?

brazen pecan
polar galleon
#

Ok thanks, for now i don't have any more questions.