#jm - update PM
1 messages · Page 1 of 1 (latest)
Hey there, can you clarify what you are trying to do? You mentioned updating a payment method but also charges/intents.
This is a hypothetical case, because I am still investigating about it: suppose I have a subscribed user and they want to update their default payment method, I saw that you can do it with the stripe.customers.updateSource method, that means I need to create a new token in the frontend and then send it back to the server, including the customer id so I can update it, but then I saw that using the createToken method is part of the Charges API, and the documentation says that the Charges API is for the USA and Canada only, so I am confused if I am able to use the token for updating the card or if I need to create an intent
Depending on how you want to update the details, you may want to use a setup intent to authenticate, yes, but this is not strictly required.
You can update the card/source (eg for expiry) or create a new one, or a new payment method, as you see fit.
But if I use the token method, will it work for global users?
What do you mean by global users here? It depends on the support for the exact payment method you mean:
https://stripe.com/docs/payments/payment-methods/transitioning#transitioning
If you mean just for credit cards, token will work fine, but you should be aware of considerations such as SCA for Europe:
https://stripe.com/docs/strong-customer-authentication
And you will need to use Setup Intents (and payment methods) to collect cards in a way that supports SCA
Oh I see... With global I mean for users outside USA and Canada, but I will take a look to those links
Sounds good -- I'd suggest reviewing and testing out what you're actually trying to do in test mode, and let us know if/where you encounter issues with specific examples/errors
My colleague @rich bough can give you a hand with that
Hiya @true nova ! 👋 Just letting you know I'm here and listening/watching