#ibgoldbergs
cedar flame
fallow igloo
Can you share more about your use case for this? I ask since it's common to clone payment methods from a platform to a connected account: https://stripe.com/docs/payments/payment-methods/connect#cloning-payment-methods
slow sinew
we have been running subscription management for our partners on our platform account and we are considering if it makes sense to move subscriptions to the connected account instead, to give our connected account partners more control over their subscriptions and customers
but are you saying they could live in both places?
fallow igloo
No, that's not what I'm saying exactly. If a connected account needs to charge a customer directly (instead of through your platform using a destination charge), that's where the payment method cloning comes in
slow sinew
Because one of the befits of having the customer and payment method on the connected account is they can use the customer to charge for other services.
fallow igloo
Yep, exactly.
slow sinew
But the drawback is that the connected account could manually modify data that may be important for our dev efforts (such as metadata)
So wondering if there is a hybrid model where a customer could be on both platform and the connected account to have flexibility but also protection
fallow igloo
Just taking a step back: cloning the payment method from the platform to the connected account will allow the connected account to directly charge them without having to prompt the customer for their payment details again. The cloned payment method could be attached to a brand-new customer on the connected account but, at that point, that's two completely separate/unrelated customers
slow sinew
Yeah makes sense. However, it’s not possible to have a customer shared between a platform and connected account. Would be really cool if that was a able to be set somehow programmatically
fallow igloo
Noted! Yeah, having these objects "live in" one account or the other doesn't afford much flexibility
slow sinew
Cool. Thanks for indulging me with the conversation. I think we will probably keep things on the platform account for now because it’s not safe to have data on a connected account when it could be manipulated by the connected account owner (metadata or products as examples)