#nicolas

1 messages · Page 1 of 1 (latest)

thick bluffBOT
tawny knot
#

Hello! There are many reasons this might be the case. Have you confirmed your integration supports 3D Secure by using test cards in test mode which require it?

proper bear
#

We didn't make it support 3DS, that's why we are surprised that there are even a few 3DS transactions

tawny knot
#

Card issuers can require 3D Secure at any time.

#

If your integration doesn't support 3D Secure the transaction will fail, which is what you're seeing.

proper bear
#

We’re using Stripe.js. Does it make any difference ?

tawny knot
#

Wait, sorry, I got my threads mixed up!

#

What does "using Stripe.js" mean exactly? Do you know what version (v2 or v3)? Are you using Stripe Elements? If so, which ones?

proper bear
#

we're using stripe/stripe-js 1.11, with no API version specified

#

and yes, we use Stripe Elements

tawny knot
#

1.11? There is no such version, and Stripe Elements requires v3.

#

Which Stripe Elements are you using?

proper bear
#

Yes, we are using the ES module

tawny knot
#

I just need to know which Stripe Elements you're using and how you're using them to determine if you have support for 3D Secure or not.

proper bear
#

It’s loaded with the Stripe API and no version defined

tawny knot
#

The ES module is only going to load Stripe.js v3, so that doesn't matter. The main question now is what Stripe Elements you're using?