#pradeep_gururani - two 3DS modals

1 messages · Page 1 of 1 (latest)

idle sparrow
#

Are those both for the same payment?

#

And if so, are you using both a SetupIntent and a PaymentIntent here?

tiny latch
#

yes, these both are for the same payment, and we're using setupIntent when creating customer and then using PaymentIntent to charge the customer

idle sparrow
#

In that case, you can skip the SetupIntent entirely and just set the parameters on the PaymentIntent so that it saves the card to your customer

#

Looking for the docs on that...

tiny latch
#

will it show the proper 3d secure modal ?

#

as of now we're also using the confirmCard method before sending the details to the backend apis

idle sparrow
#

Yes, the second 3DS modal that you are seeing now is the one from the payment intent. Without the setup intent it will just be that one that shows

tiny latch
#

okay, can we call the confirmCardSetup method without setup intent ?

#

we also need to save the card info to charge the customer again after their credits end

idle sparrow
#

No, you can only call confirmCardSetup with SetupIntents, luckily you don't need one here so you will only need to call confirmCardPayment

#

The doc I send you details how to save that info while charging the user

#

If you use the setup_future_usage parameter, you will save the card for future payments while taking the first payment

tiny latch
#

yes, we are using the paymentIntent method and the flag is true, it seems the first modal is from the setupIntent card validation ?

idle sparrow
#

Correct. And you do not need in this case, the payment intent will do everything that you need here

#

SetupIntents are for when you don't have a payment that you want to set up.