#softwareloop

1 messages · Page 1 of 1 (latest)

sudden templeBOT
spark coral
#

Hi there

#

That should only be the case if you are forcing 3DS via the API or via Radar rules

#

Do you have an example you can share?

#

A PaymentIntent ID I mean

shy copper
#

This happens now in any setup intent with this card. It never happened before.

#

Sure i have examples, do you need a setup intend id? or the request body?

spark coral
#

SetupIntent ID works

#

But yeah this is expected now if you are forcing 3DS as I stated above.

shy copper
#

seti_1OcrQND3QP1PpaABzKVXN6Zz

spark coral
#

There was a small change recently where we now support 3DS2 instead of 3DS1 (since 3DS1 is deprecated) on our test cards and we now do show 3DS for the 4242 test card among others if you are requesting it.

#

Looking at that SetupIntent, one sec.

#

Yeah so you force 3DS here via payment_method_options: { card: { request_three_d_secure: "any", }, },

#

So that is why this is happening

#

We used to just bypass 3DS for you here with 3DS1

#

But now with 3DS2 the challenge is actually shown

#

So yes this is expected.

shy copper
#

I see, that explains it. I'll run some more tests. Thanks for now.