#alexelba-subscription-paymentmethods
1 messages · Page 1 of 1 (latest)
Hello! We'll be with you shortly. Below are links to other discussions we've had with you in the past week in case you want to review that information. If your question is related to one of these previous discussions, please provide a comprehensive summary of the current state and what you need help with now. We help many users simultaneously, so a summary allows us to resolve your issue as soon as possible.
- alexelba-account-support, 6 days ago, 2 messages
Hi 👋
What do you mean by "update client"? What are you trying to update here?
customer
not client
lets say customer wants to change their card
and customer has multiple subscription
Okay first question, have you explicitly set the default payment method on these subscriptions?
In that case you would need to update each of the subscriptions.
One thing you should not do is use tokens. You should be using Payment Methods
I recommend using Setup Intents to create Payment Methods for your Customers
https://stripe.com/docs/payments/save-and-reuse
what are core differences 1 vs other (I am not disagreeing, just want to understand )
Tokens are a deprecated API that is more brittle and does not take advantage of optimizations we have made to ensure payment methods are properly configured for off-session payments.
Payment Methods are more likely to succeed when you charge them.
thanks
And when you create them using Setup Intents we configure them for off-session charging, including triggering 3DS if the issuing bank requires it.
So, once you use a Setup Intent to create & attach the payment method for the Customer I would recommend setting it as default in a few places
- As the default Payment Method for the Customer object: https://stripe.com/docs/api/customers/update#update_customer-invoice_settings-default_payment_method
- As the default for each Subscription for that Customer: https://stripe.com/docs/api/subscriptions/update#update_subscription-default_payment_method
Thanks