#jonasakessonlynkco_13568
1 messages · Page 1 of 1 (latest)
Sure but looking at that to start
From test pi_3NvK0iEL29J7Defj02qeNIFW
Hmm I only see a single 3DS attempt that seems to have timed out for that PaymentIntent in production.
Can you tell me more about what you mean when you say:
"/v1/3ds2/authenticate" is called twice.
Where do you see that exactly?
That is all internal stuff and shouldn't necessarily matter. Is something preventing you from completing 3DS?
Like is the 3DS modal not presenting?
3DS model is presenting for a few seconds but no there is no time to be able to complete
Loading and redirecting
How are you presenting the 3DS modal here?
Trying to understand why the problem is not reproducing in test environment.
3DS is embedded in an iFrame. The 3DS is working fine when were for example adding a new card and the client is redirected to a full 3ds page
Right, it seems like there is some issue here with the iframe presentation. It is possible that it is being rendered twice or something and that is canceling the first attempt and breaking the flow.
Have you added breakpoints to try and see what is happening in your code client-side?
The content-length in response headers differes between the two calls, not sure if that would matter