50an6xy06r6n

[fierce ridge]

hi! that's impossible, no.

[clear oxide]

is there a way to manually copy the info over?

[fierce ridge]

what's the context on why you need to do this? For you yourself to self-serve it, no. As a one-off migration we do for you if you write to support, maybe.

[clear oxide]

we originally set up payment methods to be on the connect accounts, with the platform taking an application fee, but we now have a use case where those customers pay us directly. We'd like to enable that without forcing them to all re-enter their payment information

we'd also be cloning those payment methods back onto the connect accounts so we can still support the original use case

[fierce ridge]

well the options are

• re-collect information from the customers and save it to your platform account.
• ask us to copy the details from a connected account to your platform, as a one off(https://stripe.com/docs/account/data-migrations/pan-copy). Will heavily depend on the type of Connect account you have(for example if it's Standard Connect, the account holders all have to agree I believe) and note it's a one-off so you likely want to already have a working integration for your 'future state' built first

[clear oxide]

yeah they're standard accounts. Who would we have to get consent from? The account holders or the customers?

why is cloning allowed to connect accounts but not to the platform account?

[fierce ridge]

the account holders

[fierce ridge]

because we built one of those and not the other I suppose. There's no deep reason but it's just not how the API works, Connect is very hierarchical

[clear oxide]

so there's also no way for a customer on a connect account to directly pay the platform right? There's a line in the documentation that seems to suggest that, but I'm not sure

https://stripe.com/docs/connect/cloning-customers-across-accounts

Cloning saved payment methods is only relevant when creating direct charges on connected accounts. It’s not necessary when making charges on your platform account.

[clear oxide]

it seems like a weird design decision to not allow that, especially since there are support pages describing the transition from having customers on the connect account to having them on the platform. Like clearly it's a known use case lol

[fierce ridge]

right

[fierce ridge]

what support page?