Vikki

[mystic eagle]

Hello,
AFAIK nope,

they are unable to type in their verification code/password.
Do you have more details about this? like a Screenshots, PaymentIntent Id ?

[small fulcrum]

Private messaged you a paymentIntentId (actually this didnt work), and just trying to source a screenshot for you, thanks

[mystic eagle]

you can copy/past the PaymentIntentId here

[small fulcrum]

cheers, here is one of them pi_3JlzUDFMmm2LWMFg1zx4avYm

[mystic eagle]

any other details showing that the customer are unable to type in their verification code/password ?

[mystic eagle]

AS far as I can see, that the provided payment method has failed authentication, true. but this could be intended by to the card issuer bank

[small fulcrum]

unfrotuatnely we don't have too many details on it, we use Stripe connect so its our customers customer who generally report it

The reportings of it are that either that the fields are disabled/greyed out (and we believe they have tried to click into them) or the customer tries to type in and the field clears almost immediately

[mortal cobalt]

we do sometimes see issues where the merchant site(yours) steals focus from the elements in the iframe'd popup and that can cause issues.

might be worth investigating that and seeing if you have any sort of code that attempts to autofocus certain elements or uses Javascript to focus them, and try removing that. Unfortunately you can't test it very well because none of our test mode pages have an <input> you can type into to reproduce a problem(there's a feature request internally to build that)

another solution is to do a full page redirect to the 3DS page instead of our popup if you consistently have problems, that has the most compatibility overall. https://stripe.com/docs/payments/3d-secure#manual-redirect

[small fulcrum]

hmm ok, will take a look into autofocusing thanks.

Good to know for future that test mode will support inputs, thanks.

We did try to look into full page redirect but we use the stripe Elements so we can support all payment methods with confirmPayment which appears to not support that, please correct me if I'm wrong

Another potential theory we had was to do with our CSP setup?!

[mortal cobalt]

could be, we have docs here about what you need to have in your policy : https://stripe.com/docs/security/guide#content-security-policy

[mortal cobalt]

yeah I don't think the PaymentElement integration supports the manual 3DS redirect.