• Resolved joyryde

    (@joyryde)


    Hi,

    We have this setting enabled:

    Force 3D Secure
    Stripe internally determines when 3D secure should be presented based on their SCA engine. If Force 3D Secure is enabled, 3D Secure will be forced for ALL credit card transactions.

    Today we got an order and it completely bypassed 3D secure.

    Stripe show the payment info as:

    Payment succeeded
    This payment doesn’t qualify for Chargeback Protection because it wasn’t made through Checkout.

    Stripe risk evaluation: normal

    Payment started

    So the payment is no protected by 3D secure, and additionally was not made through their Checkout process.

    How did this happen if the plugin setting is checked to force 3D secure?

Viewing 13 replies - 16 through 28 (of 28 total)
  • Thread Starter joyryde

    (@joyryde)

    That doesn’t work because as soon as you click the test dat abutton, the live webhooks disappear, and it says:

    You have not defined any webhooks yet
    Did you mean live mode?
    We couldn’t find what you were looking for in test mode, but we found it in live mode.

    Thread Starter joyryde

    (@joyryde)

    I’ll wait 24 hours for some new orders and see if they continue to say that it’s failing; I’ve disabled it and reenabled it again.

    Plugin Author Payment Plugins

    (@mrclayton)

    Then create a webhook in test mode and perform a connection test on it.

    It’s the same url so if it works in test mode it will work in live mode.

    Per my previous reply, if you provide some log entries of t he failed webhooks I can see why it’s failing.

    Thread Starter joyryde

    (@joyryde)

    Our biggest priority is the 3D Secure failure and Apple Pay failing…do you think that Radar is the cause of those issues?

    We use very secure Radar rules:

    https://tinyurl.com/ydy67ddb

    We know that the Apple Pay is failing because of Radar rules. Stripe is forcing all Apple Pay Payments through the Radar rules, causing them to be declined.

    Plugin Author Payment Plugins

    (@mrclayton)

    Yes it’s possible your radar rules are overriding the force 3D since it looks like you’re using the paid version of radar.

    Let me know when Stripe responds to your request then we will know for sure.

    Plugin Author Payment Plugins

    (@mrclayton)

    Marking as resolved since this isn’t a plugin bug. Waiting on reply from @joyryde regarding their inquiry to Stripe.

    Thread Starter joyryde

    (@joyryde)

    Stripe isn’t responding to either request.

    Thread Starter joyryde

    (@joyryde)

    Should I just totally disable Radar ad stop paying for it, and then leave it up to the plugin to force 3D secure?

    Also, does the plugin have a way to stop this issue?

    “This payment doesn’t qualify for Chargeback Protection because it wasn’t made through Checkout.”

    Plugin Author Payment Plugins

    (@mrclayton)

    @joyryde

    If all you care about is forcing 3DS for everything then you probably could stop paying for it but there are other benefits to the radar service like declining payments that go over a certain risk threshold.

    No that response is coming directly from stripe and stripe is saying that payment is OK therefore our plug-in treats it as being OK.

    Thread Starter joyryde

    (@joyryde)

    I guess my questions still remain then, because if I disable Radar, 3D secure will work correctly, but with it enabled, we are still seeing the problem that I reported in this post originally…orders go through without it, even though it’s mandatory per the plugin.

    Also, How do we “enable Checkout” to guarantee chargeback protection?

    Plugin Author Payment Plugins

    (@mrclayton)

    I’d wait and see what Stripe replies with.

    Checkout is not supported by this plugin. Checkout is a Stripe hosted payment page. I assume that’s what that message is referring to.

    You can read more about it on Stripe’s website.

    https://stripe.com/payments/checkout

    Thread Starter joyryde

    (@joyryde)

    Well, Stripe replied and their response makes no sense.

    I sent them this post so they knew what the issues were, and their response was:

    Looking into the question, it seems the developer pretends that to be an issue but it is the work flow of this protection and 3D secure nature is designed to be like that. This feature is applicable for specifically payments processed through Stripe checkout only. These tools are specially made for Stripe Checkout. If you use an external Stripe plugin with a third-party this will not be applicable.

    Plugin Author Payment Plugins

    (@mrclayton)

    Hi @joyryde,

    Ya that response doesn’t make sense to me. The payment intent API is not something exclusive to Stripe Checkout:

    https://stripe.com/docs/api/payment_intents/object#payment_intent_object-payment_method_options-card-request_three_d_secure

    Can you please contact me via our support email and send me your email chain with Stripe? I want to get this into the right hands at Stripe.

    Kind Regards,

Viewing 13 replies - 16 through 28 (of 28 total)
  • The topic ‘Force 3D Secure’ is closed to new replies.