#birdy247
velvet loom
karmic flame
Hi, what specific questions do you have?
gilded talon
We have a specific use case where we use direct charges to pay 2 or more connected accounts in one go
For this, we use a setupIntent on our platform and then clone things to create paymentIntents on the connected accounts
Finnaly we use stripe.js to confirm them
In this use case, its always paymentIntents
We now have another use case, whereby we want to follow the same model, but on one account, we want to setup a subscription
karmic flame
The same flow should work here too. You're cloning the Payment Method, https://stripe.com/docs/payments/payment-methods/connect#cloning-payment-methods and then use that cloned Payment Method to create the Subscription.
gilded talon
Would we need a customer to clone as well?
karmic flame
To be specific, the steps are
1/Create the customer on the Platform Account
2/ Create the Payment Method on the Platform Account
3/ Attach the Payment Method to the Customer on the Platform Account
4/ Create a Payment Method using the Stripe Account Header and by passing the above object ids. It creates a Payment Method on the Connected Account
5/ Create a Customer on the Connected Account also by using the Stripe Account Header
6/ Attach the Payment Method from step 4 to this customer id from step 5 by using the Stripe Account Header
7/ Create the Subscription and use the Payment Method.
gilded talon
Or can we just create the customer and attach the clone payment method
item 4 - is the cloning the payment method?
karmic flame
The 'cloning customer' is a bit confusing on this document, https://stripe.com/docs/connect/cloning-customers-across-accounts. But it's essentially saying to clone the customer's payment information.
For some business models, it’s helpful to reuse your customers’ payment information across connected accounts. For example, a customer who makes a purchase from one of your connected sellers shouldn’t need to re-enter their credit card or bank account details to purchase from another seller.
Yeap!
gilded talon
So we must be doing upto point 4 already
But at this point, we currently diverge and instead create the payment intents
So we would instead need to follow points 5,6 and 7 for any subscriptions
karmic flame
I recommend that you try it out in test mode.
karmic flame
Yeap!
gilded talon
Awesome
From that point on, we can step back from managing the subscription presumably and leave it to the other account
Or would all webhooks etc.. only come to our account because we handled the setup process?
karmic flame
If you're handling direct charges and if you are listening to your Connect Accounts webhooks, you would get the events.
gilded talon
But presumably so would the connected account
karmic flame
Yeap