#Diegus
1 messages ยท Page 1 of 1 (latest)
Hi ๐
Using Setup Intents to collect payment method details and attach the payment method to the customer is our canonical approach to saving payment method data. I recommend going with that approach.
Great, so it's the right path then ๐ . Thanks!
Happy to shed what ๐ก I can ๐
Regarding with saving a payment method for the future, if the card requires some kind of authentication ( 3D ) during saving request, might it be required in the future after making a few payments? I need to be sure about this to crafting the right UX
Setup intents are designed to optimize the payment method creation up front. They will handle additional authentication if needed. That being said, an issuing bank can request additional authentication at any time so you should make sure your integration can handle bringing the customer back on-session if needed.
gotcha, and I guess next_action property included within payment_intent response will be the same as the setup_intent response
๐ hopping in here since snufkin had to head out