#Wasabi - Mobile Crashes
1 messages · Page 1 of 1 (latest)
Hello! We generally recommend you write code to account for and gracefully handled unexpected input, but do you have a more specific question?
Thanks for confirming. No, the payment intent id and client secret use cases were the only two has been brought to my attention.
I do have a separate question for mobile sdk
Is there any documentation on how to update a payment method for mobile SDK?
What specific SDK(s) are you asking about?
iOS and Android
By update do you mean update an existing Payment Method's info, like the expiration date, or do you mean replace a Payment Method on a Customer with a new one?
By update as if a customer wants to change a card number of payment method
You should follow this guide to set the card up for future payments and save it to the Customer: https://stripe.com/docs/payments/save-and-reuse?platform=ios&ui=payment-sheet
That link is for iOS, but there's also an Android tab on that page.
You can then set the resulting Payment Method as the Customer's invoice_settings.default_payment_method or remove the previous Payment Method or whatever makes sense for your use case.
Is this the only option, where user needs to do auth & capture using SetupIntent? They are planning to go with PaymentIntent
Not sure I understand. If a Customer wants to update their card without making a payment you would use the guide linked above which involves a Setup Intent and no funds, so there's nothing to capture.
Are you asking how to save a card while also taking a payment?
If so this would be the guide for that: https://stripe.com/docs/payments/save-during-payment?platform=ios&ui=payment-sheet
🤔
No. I'm trying to better understand an effective way to update a PaymentMethod for an existing customer. So let's say when create a new customer, user call PaymentIntent to create a subscription and save default card by setting inovice.settings.default_payment. Then this customer before renewal date decide to update his paymentmethod via the UI. What api and param should the user call?
for Mobile SDK for iOS and Android^^
You should implement the steps from the first link I shared above and use a Setup Intent to set up the new Payment Method for future use, then set it as the Customer's invoice_settings.default_payment_method.
This one specifically: https://stripe.com/docs/payments/save-and-reuse?platform=ios&ui=payment-sheet
Thank you! To confirm, the trade-off here is that the user will be charge for both auth and capture when an existing customer update their payment method?
What do you mean? A Setup Intent does not charge anything. Who is the "user" you're referring to?
Maybe I am misunderstanding the docs I've read. Are there any financial impact or tradeoffs when using PaymentIntent vs. SetupIntent?