#pupilcp_unexpected
1 messages ¡ Page 1 of 1 (latest)
đ Welcome to your new thread!
â˛ď¸ We'll be here soon! Typically we respond in a few minutes, but sometimes we might take a bit longer if the server is busy or if you have a particularly tricky question.
âąď¸ We close idle threads, which makes them read-only. Once a thread is closed it won't be reopened, but you can always start a new thread if you have another question.
đ This thread will always be available, even after it's closed. You can find it again using Discord's search, or you can save this link: https://discord.com/channels/841573134531821608/1230738480758390958
đ Have more to share? Add more details, code, screenshots, videos, etc. below.
hello! the 3DS request was rejected by the issuer and challenge was not requested. You'll need to get your customer to reach out to the issuer to find out why the 3DS request was rejected
There is no 3ds pop-up window and the user has not entered the verification information. Why does 3ds fail to verify?
even prior to the 3DS pop up window (challenge) occurring, a request needs to be made to the issuer. The issuer rejected that authentication request. So the 3DS pop up window (challenge) does not occur
That means the next_action returned by the paymentIntent confirm interface does not mean that the 3DS pop-up window will definitely appear. Is that right
yes, that's correct