#deathpote - connect

1 messages · Page 1 of 1 (latest)

random shard
#

Hi there!

broken nacelle
#

Hi Soma, thanks for your time !

random shard
#

What do you mean by "I've tried to link the new Stripe Connect to itself"?

broken nacelle
#

I didn't found any other way to link an existing account to a Connect account.
(I want to link the old account to itself via connect to facilitate the migration from standalone account with legacy subscriptions to a Connect account)

random shard
#

Connect is useful when you have a main account (a platform) that wants to connected to a different Stripe account. Here you are trying to use Connect with a single account?

broken nacelle
#

we plan to upgrade to multiple currencies with a sub company in another country

#

the plan is in a first step to handle our EUR subscriptions via connect instead of standalone account, and adding in a second step an USD account

random shard
#

OK, but you can't connect an account to itself. If you want to use Connect, you need at least 2 accounts.
If you already have an account for EUR subscriptions, you could create a new Stripe account that will be the platform, and then connect the existing account to it. And later you also connect the account fur USD subscriptions.

broken nacelle
#

Oh, strange I remember a line for the stripe documentation stating that I "shouldn't" connect an account to itself, but only to avoid confusion while using and debugging connect.

If I create a third account with Connect on it, how can I handle legacy subscriptions ? Those were created on our first old Stripe account, and Stripe Connect can't manage subscriptions not created by itself. Should I have two separate flows, one connect for new subscriptions and one legacy standalone for old subscriptions ?

#

(I've found the line :
Don’t connect the platform account to itself—that fails to reflect the real world use of Connect, and makes debugging difficult.
https://stripe.com/docs/connect/testing
Since it's on the testing documentation, it's maybe only possible to link to itself in a sandbox environment)

random shard
#

OK, so it might be possible to do. But like mentioned in the documentation, we don't recommend doing it. The approach I mentioned above should be better.

broken nacelle
#

Ok so I'll make a third account for Connect, thanks !
And for legacy subscriptions, how can I handle them ?

solar crane
#

👋 I'm stepping in for my colleague

broken nacelle
#

Hi Tarzan, thanks for your time !

solar crane
#

what do you mean by legacy subscriptions?

broken nacelle
#

We have a running Stripe integration since multiple years, with customers, payment methods, subscription, etc already up and running
those subscriptions where created by our current EUR Stripe account
If we create a new Connect account and connect our current account to it, those old subscriptions still running can't be managed by the new Connect account

solar crane
#

you'd have to do this in multiple steps

#

2- go through your Platform Account's subscriptions and recreate those on the new account

broken nacelle
#

Ok thanks, a migration was what I feared.
I see I have a call to create payment intent in the process, with the SCA regulation will the migration be possible for 100% of my customers ?
Will all subscriptions be migrated without any drop ?

The more I look into it, the less likely I think I'll use Stripe Connect. With a legacy account, migrating to it is not a lightweight solution.

#

If only I could enable connect on my old account and connect it to itself, it could handle it's own subscriptions via connect without any migration.
If I may suggest, a complete guide to migrate from standalone to stripe connect could be a nice addition to the documentation. I think it's a step many companies will go through when going international

Anyway, thanks for your time and answers !

solar crane
#

I think you can get support for migrations if you contact https://support.stripe.com/?contact=true

#

this would be your best chance