#rkrkrohitkkumar

1 messages · Page 1 of 1 (latest)

bronze talonBOT
charred niche
#

Hi there

#

What integration flow are you using here?

gleaming storm
#

we are using payment element

#

and using stripe.confirmPayment() to check if the card is 3ds or not

charred niche
#

Hmm are you trying to block any cards that require 3DS?

#

Or you want to show an error if 3DS fails?

gleaming storm
#

we want show error when saving 3ds payment method for backend user

charred niche
#

Can I ask why you want to do this exactly?

gleaming storm
#

during checkout we are able to show the error message for 3ds Pm message using error_on_requires_action but seems like for setup intent this parameter is not there

#

we dont want the user to save 3ds card from backend.

charred niche
#

Is there a reason you don't want to save cards that require 3DS? As long as 3DS is completed successfully initially it will be very rare for it to be required again in the future.

gleaming storm
#

not sure of the reason, but we want only the community member to save a 3ds card not the backend user.

charred niche
#

Hmmm I'm still not sure I understand. What is a "backend user"?

gleaming storm
#

okay, so bacically when saving a 3ds PM I have to display an error message

#

I checked the setup intent's doc but there is no parameter for any error to be thrown

charred niche
#

No there is no way to force an error with a SetupIntent if 3DS is required. That doesn't really make sense as the whole point is to set up the payment method for future use which means completing 3DS if necessary.

#

It sounds to me like you are trying to work around some other issue

#

Like, are you inserting card details for your customers here?

#

And that is why you want to prevent 3DS?