avatar_hzh

[wheat bluff]

we don't actually support an exact copy in most cases.

Using subscriptions as an example, what you would need to do is to create a new subscription and reimplement the subscription logic - https://support.stripe.com/questions/recreate-subscriptions-and-plans-after-moving-customer-data-to-a-new-stripe-account

For PaymentMethods that cannot be migrated, you're going to need to bring the customer back on-session to collect their payment details again.

You cannot copy Events and Logs to a different account.

With regards to connected accounts - what type of connected account are you using (Standard/Express/Custom)?

[lime bloom]

Hi, thanks for that. The sticking point I had was on PaymentMethods specifically and it's nice that you cleared this up for me.

[wheat bluff]

I need to step away so I’m going to archive this thread. If you need help with anything else please ask in #dev-help or contact Stripe Support: https://support.stripe.com/contact

[terse talon]

👋 hello lets continue here @lime bloom

[lime bloom]

sure

[terse talon]

from main:

is it possible to copy over SEPA sources from one account to another account via the API?

[lime bloom]

yea I was wondering if it's possible

[terse talon]

No, this is not supported

[lime bloom]

so with direct debit cards just like the payment methods we'll have to get the details from the customers again right?

[terse talon]

There is some support for cloning/sharing card-based payment method within a Connect platform to connected account, but for other payment method you'll need to create it on the account where you intend to use it

[lime bloom]

ok

What about coupons, charges and invoices?

[subtle summit]

catching up here avatar

only PaymentMethods can be cloned

nothing else

[lime bloom]

ok thanks for the clarification