#Cpark14
north forge
No problem
normal trailBOT
daring oasis
So I figured out it doesn't necessarily have to do with tokens but what we are doing is for recurring payments, we're setting the initial payment intent for future use, and attaching the payment method to the customer object. We then retrieve that payment method and use it to create future payment intents for the recurring payment. Since the payment intent is bound to a customer object, and that customer object is a part of the account, I'm going to assume there's no way to move customers with their associated payment methods from the customer's "main" account into a newly created Connected account. So really the question is, is there a way to move customers with their associated payment methods from their main account into a newly created Connected account?
abstract pulsar
Hi there 👋 taking over, as my colleague needs to step away
So let's use the terms "platform" and "connected account" where the term "platform" refers to the Stripe account that is creating and managing the connected accounts.
If you create Customers on the platform, you can clone them from the platform to any number of connected accounts (see here: ~~https://stripe.com/docs/connect/cloning-customers-across-accounts~~). This functionality is not possible when the Customers are created on the connected account. Once they're created on the connected account, they cannot be cloned or "moved"
daring oasis
Definitely answers my question thank you so much!
abstract pulsar
Real quick: I accidentally sent you the legacy docs @daring oasis. Here are the up-to-date ones: https://stripe.com/docs/payments/payment-methods/connect#cloning-payment-methods
daring oasis
no worries thanks again
daring oasis
Just to clarify, the previous statement said that customers on a connected account cannot be cloned, only customers on the platform account. Does the same apply to cloning payment methods?
abstract pulsar
Correct