Thank you for the response. This makes sense, however is there a way to NOT allow the user to pass and get to the point of a pending status without passing the authentication properly?

I've changed the gateway = Hosted Checkout, so hopefully the user will now be able to complete. That being said, it seems strange the user was allowed to be sent the CBSubs pending message because once they receive that message via our site, Stripe has told me there is no way for them to send the user a way to authenticate. So it should be completed during the checkout process or the user shouldn't be allowed to proceed. Does this sound correct to you?

krileon wrote:

Was this for a single payment or recurring payment? Looking into this further as to where things might of gone wrong. Single payments via payment intents seam to be fully functional with the 3DS popup. Reviewing SetupIntents, which are used for recurring, but they should behave the same.

Edit: Recurring are also showing the 3DS popup.

This was a recurring payment subscription.

They said all should be good. You can require 3DS via API, this is per Stripe:
"3D Secure conversion
3D Secure is a verification step with the card issuer during a payment or when saving a card, to reduce fraud. You can request 3D Secure via Radar or the API. Additionally, Stripe triggers 3D Secure when required by regulation. Understand how your authentication impacts your payment conversion. See more"

stripe.com/docs/payments/3d-secure