Jordeen

[rain tartan]

Hi there! Taking a look

The fact that the Checkout Session isn't prefilled with this customer's payment details appears to be expected. There are no recent card payments on this account with the saved PaymentMethod for this customer.

If you complete the Checkout Session with one of our test cards, then create another Session for the same customer, the card details should be prefilled

[true bough]

So is there no way for me to migrate a Checkout Session to a Connect account and have their payment info pre-populated?

[rain tartan]

No, this isn't possible with Checkout

[true bough]

Even though they technically made a payment before on my platform account

I see

Is that something that might change in the future? Or is that purposely designed that way?

Because I can copy over a payment method on a Connect account and create a payment intent and charge that customer all in that Connect account, so I thought this would be similar, in that I don't have to force the user to re-add their credit card.

[rain tartan]

Right, so even though they technically made a payment before on the platform account, the connected account is separate. Currently, the prefill logic for Checkout will pull in a card that was recently used by that customer but this customer as it exists on the connected account is technically a brand-new customer

[true bough]

I see, how come it can't see the payment methods that are already attached on the customer in the Connect account?

[rain tartan]

That's a good point, I'm not sure why it was designed this way exactly. That said, since you already have the customer's payment details, is there a particular reason why you're creating a Checkout Session instead of creating and confirming a PaymentIntent server side?

[true bough]

It's just what we had originally used, so we were hoping we could keep that logic, but I think we will have to use PaymentIntents.

Thanks for your help!