Stripe Gateway Handling

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.

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.

Ok, am looking into handling the next_action behavior server side in addition to Stripe JS. I've no idea why the 3DS did not popup for them. They are correct that 3DS is required the payment is blocked and is the case in all my tests with single and recurring with Stripes 3DS test cards. The server side handling of next_action should solve this though as when processing the SetupIntent or PaymentIntent it will see a 3DS redirect is needed and send them to it.

Looked into this further and it maybe due to your Radar settings within Stripe. If not setup correctly it won't request 3DS. Suggest contacting Stripe to make sure your Radar settings are correct. Am still going to implement the server side handling of next_action as a precaution though.

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