#kyleruban
boreal jacinth
Hi 👋 can you elaborate, what are you expecting to see happen that isn't?
hushed lintelBOT
boreal jacinth
@fair fulcrum I wanted to check in to see if you're still around and could provide more details about your scenario?
fair fulcrum
I am expecting to see a payment method saved with my Customer
So I can go back in and use the Customer ID to recharge the payment method for a specific order if that order requires an extra charge that was not handled with my application
As you can see there is no default payment method saved with each Customer
@boreal jacinth @clever hazel - do you know what i mean
Or is it being saved elsewhere?
boreal jacinth
Using setup_future_usage does not automatically set the Payment Method as the Customer's default, you need to explicitly do that by updating the Customer object.
https://stripe.com/docs/api/customers/update#update_customer-invoice_settings-default_payment_method
The setup_future_usage parameter prepares the payment method for future usage, but it doesn't assume that the new Payment Method should be configured as the default.
fair fulcrum
How can i reuse a Customers payment method after saving? Do i just have to specify the CustomerID in the request?
Do i have to make the default method to reuse the customers payment method?
Is this where it saves when using setup_future_usage?
clever hazel
👋 stepping in
Yep so to re-use the PaymentMethod in the future you would create a new PaymentIntent and pass the Customer ID and PaymentMethod ID
fair fulcrum
Does that mean I have to save the paymentmethod ID in my database?
So i can access it to pass in the request?
I am saving my customers stripe customerID in my database right now
Or like how could i access that paymentmethod ID?
clever hazel
Up to you if you save directly in your database or if you retrieve the PaymentMethod via listing based on Customer ID (https://stripe.com/docs/api/payment_methods/customer_list)
hushed lintelBOT
fair fulcrum
Do i have to do this when saving a customers payment method also? Or just use the setup_future_usage?
clever hazel
Sorry for the delay