martimcfly

[vast quail]

Hey there

Do you have more information that you can provide?

These are your tests so I don't know what you are testing exactly

[lament badger]

We are generating payment automatically for testing purpose and since 5 days ago all of them are failing. You can have more info here:
https://dashboard.stripe.com/test/payments/pi_3OJdtPKrRPyzMk3S1t5SSFnt

[vast quail]

Can you provide a specific failing request ID?

What error do you see?

[lament badger]

Can you recheck the link please?

[vast quail]

No that's not how this works

You are a developer here

You need to debug as well.

I am here to help answer questions and help you. Not to do the work for you.

I'm helping multiple folks at the same time

[lament badger]

Expected behaviour :
This payment method pm_card_amex_threeDSecureNotSupported should succeed on any payment (as in the docs : no 3DS secure but passing payment).
This was working since months on our test pipelines.

Experienced behaviour (since last Thursday):
Any payment with this payment method is failing. I provided the link for example
https://dashboard.stripe.com/test/payments/pi_3OJdtPKrRPyzMk3S1t5SSFnt

[vast quail]

Taking a look at that specific PaymentIntent

[vast quail]

Okay @lament badger , that PaymentIntent actually uses the pm_card_threeDSecureRequired card. There is a known bug with this specific test card, related to the deprecation of the Request 3DS if 3D Secure is required for card Radar Rule, that is being worked on internally and is cauing your issue here. A temporary workaround is to enable the Request 3DS if 3D Secure is recommended for card Radar Rule here: https://dashboard.stripe.com/settings/radar/rules

I'll also push internally for the work on this bug to get expedited

[stable mauve]

@lament badger just want to make sure you saw the message above?

[lament badger]

Yes, I'm checking