3Ds not getting triggered for any payment after 10th Oct 5:30 PM IST

  • Resolved Ashish Desai

    (@shubhamgulati12)


    2 years, 5 months ago

    Hi Team,

    I can see that starting 10th October at 5:30 PM IST none of the payments are going through 3DS. There was no change on my Stripe dashboard under Radar and by default, the force 3D secure setting is enabled from the plugin’s end.

    Can you please confirm if this is related to some issue with the plugin or Stripe’s backend issue?

Viewing 5 replies - 1 through 5 (of 5 total)
  • Plugin Author Payment Plugins

    (@mrclayton)

    @shubhamgulati12 this is not related to any issue with the Stripe plugin.

    You’ll notice there hasn’t been an update to the Stripe plugin in 2 weeks.

    I’d recommend you contact Stripe support regarding any concerns related to 3DS not triggering.

    Kind regards

    Thread Starter Ashish Desai

    (@shubhamgulati12)

    Here is what they are saying about this:

    “Thanks for reaching out and chatting earlier with me today!
    I’m truly glad I was able to assist and solve your doubts regarding 3ds.
    As mentioned in our chat interaction please reach out to your third party woocommerce plugin as they are not triggering the 3ds verification.”

    Can you give me the response I should provide them which will ensure that 3DS is getting triggered from the plugin’s end but not from Stripe’s backened?

    Thread Starter Ashish Desai

    (@shubhamgulati12)

    Hi Team,

    I just downgraded my plugin to Version 3.3.25 and 3DS started working again.
    I know there wasn’t any update from the last 2 weeks but I don’t have auto-update enabled for this plugin and hence I manually updated the plugin on 10th October. That’s the reason why I started having that error after it.

    Can you please help check the reason for this?

    Plugin Author Payment Plugins

    (@mrclayton)

    As mentioned in our chat interaction please reach out to your third party woocommerce plugin as they are not triggering the 3ds verification

    Stripe support is wrong, the plugin doesn’t control when 3DS is triggered beyond one setting (the force 3DS setting) option. Even that option does not 100% guarantee 3DS will be triggered if the customer’s payment method doesn’t support it.

    Stripe’s API controls when 3DS is shown to the custom based on their internal logic, not the plugin.

    Can you please help check the reason for this?

    3DS is working perfectly in our testing. If 3DS was broken in the plugin, we’d be flooded with support requests given how many merchants use the plugin.

    I just downgraded my plugin to Version 3.3.25 and 3DS started working again.

    This could easily be a coincidence of timing. Upgrade the plugin again and test again.

    Thanks

    Plugin Author Payment Plugins

    (@mrclayton)

    @shubhamgulati12 Any update?

Viewing 5 replies - 1 through 5 (of 5 total)
  • The topic ‘3Ds not getting triggered for any payment after 10th Oct 5:30 PM IST’ is closed to new replies.