#negative10xprogrammer
1 messages · Page 1 of 1 (latest)
Yes, if you believe a future purchase may happen then you'll need a Customer object (because you need to attach a Payment Method to a Customer in order for it to be used repeatedly in the future)
Yes, alright. And all i really need here is the paymentmethodid? for the creation of a customer object
and then I save that customerId to the user in my db and whenever i want to fetch and display his payment methods i just make another stripe call
to get payment methods
There aren't any required params to create a Customer, but generally it'll be in your best interest to at least provide some things (like email, name, etc) or at least tie it to some other representation of a Customer in your own databases so you know which CUstomer to retrieve later on