#alexelba-subscription-paymentmethods

1 messages · Page 1 of 1 (latest)

exotic perchBOT
#

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.

modest patio
#

Hi 👋

What do you mean by "update client"? What are you trying to update here?

shell flume
#

customer

#

not client

#

lets say customer wants to change their card

#

and customer has multiple subscription

modest patio
#

Okay first question, have you explicitly set the default payment method on these subscriptions?

shell flume
#

'payment_settings' => [
'save_default_payment_method' => 'on_subscription',
],

#

yup

modest patio
#

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

shell flume
#

what are core differences 1 vs other (I am not disagreeing, just want to understand )

modest patio
#

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.

shell flume
#

thanks

modest patio
#

And when you create them using Setup Intents we configure them for off-session charging, including triggering 3DS if the issuing bank requires it.

shell flume
#

Thanks