kaustuva-connect

[sly python]

you have to create a different Customer object on the account you're creating the PaymentIntent on, you can't reference objects from one account when making an API call on another

there is https://stripe.com/docs/connect/cloning-customers-across-accounts, which lets you create a Customer on the platform account and copy one of its payment methods to a connected account(and then you can attach it to a Customer you create on that connected account), which might be useful in this case.

[cyan chasm]

Thanks. Is cloning something I'll have to implement as part of my code flow for every new attempt to save a card? once the paymentIntent is cloned, it is there for me to use on both accounts? [ Yet to go through the doc fully ]

Also can we clone customers to payment accounts or paymentIntents to customer account ? Or we can do it both ways?

[bitter pollen]

You can't clone a Payment Intent, no

Not sure I understand what the 'payment accounts' is in this context

[bitter pollen]

That really depends on your business needs. From the doc linked above:

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.

If that fits your use case, then you'd need to create the Customer and Payment Method on the Platform account and then they can be cloned across multiple connected accounts. The doc outlines how to do that

[cyan chasm]

Thanks
Is there way I can do it without cloning by using this:

https://stripe.com/docs/payments/connected-accounts

Charge on behalf of connected account? Can I save my card using this method to the connected account?

[bitter pollen]

You can, but then you can't then clone that Payment Method across to other connected accounts

[cyan chasm]

Thanks. this actually won't work since I would have to create a new account in account_2 and then create payment intent on behalf of account_1. Cloning would automatically make these two accounts identical

Also, just confirming...we cannot use sources object with PaymentIntent api right?

I intend to implement 3DS

[bitter pollen]

You can yes: https://stripe.com/docs/payments/payment-methods/transitioning#compatibility

Generally we'd recommend to use Payment Methods though

[cyan chasm]

so I can create a source, pass the source id to the paymentMethod field of the paymentIntent and also attach the source to the customer object (this would save it to the customer)
And I can still implement 3DS using this method below?
i.e. PaymentIntent(with source) and separately saving the source to the customer

[bitter pollen]

No, Source objects don't support 3DS. That's why we build Payment Methods

As I said, you shouldn't use Source objects unless you're a legacy integration

[cyan chasm]

Thanks a lot.
Is there a single api available that lists all the paymentMethods+sources for a customer?

[bitter pollen]

There's not, no

[cyan chasm]

Thanks for your help

[bitter pollen]

Np!