#ygd-connect
1 messages · Page 1 of 1 (latest)
cloning payment methods work only for card type :Cloning supports PaymentMethods of card type only. we wanted to store sepa debit as well
unfortunately we don't support that
so, if I understand it correctly, we first need to clone the customer and afterwards the customers payment method separately to the connected account to create the payment intend. cloning only the customer is not sufficient, right?
you can't clone customers at all
sorry, the docs on this feature are quite bad
the only thing you can do is clone a payment method from a platform account to a connected account. That's a building block you can use to implement a concept of 'cloning a customer'
by creating two separate cus_xxx Customers, one on the platform and one on the connected account, and copying the PaymentMethod from the platform to the connected account to attach to the Customer on the connected account
got it
the gap of cloning sepa payment methods is letting me think if the feature makes it useful for us. we have the problem of not getting paypal integrated in our system like we do with stripe and connected accounts and wanted a counter for prospects and customers who are asking for it - saving sepa payment info is doing the same thing as paypal
maybe storing the payment information / customer only on the connected account would work with sepa
well it's one of the the only two options yes
either you collect and store the SEPA PaymentMethod on the connected account and do Direct Charges there with them, or you collect/store them on the platform and do Destination Charges (https://stripe.com/docs/connect/destination-charges) so you can route the funds to a particular connected account.
okay thank you a lot. I will discuss with my team and come back if we have still questions.