ranvir

[analog lion]

You're right, there's nothing stopping you from creating the SetupIntent first

Creating the customer second isn't frowned upon, just depends on what's easier for your team to keep track of or what a typical customer flow looks like on your end

Creating customers any time the user wants to change their payment method seems suboptimal if a customer wants to go back to using a previously-stored payment method

[raven sundial]

yes if the user wants to switch back to previous payment method, that use case is in future scope and then we shall be creating the customer first/or picking the existing customer. thanks for the inputs.

[analog lion]

Actually, taking a step back. Creating the customer and attaching the PM later is suboptimal in that you're just creating additional calls. Ideally, the SetupIntent creation call should include a customer ID so that confirming the SetupIntent automatically attaches the PM to the customer