• 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 15 replies - 1 through 15 (of 28 total)
  • Plugin Author Payment Plugins

    (@mrclayton)

    @joyryde,

    Can you please provide the Stripe log for that particular payment intent? Also can you confirm this was a credit card payment via the credit card gateway? The intent should have the following property: request_three_d_secure: 'any'. If it has that property then the plugin did its job in assigning the force 3d secure property.

    Once you provide that log entry, I can confirm it has the property. If it does, then you will need to contact Stripe’s support team to inquire why their internal code did not force 3D Secure, despite the correct property being set by the plugin.

    Kind Regards,

    Thread Starter joyryde

    (@joyryde)

    Hi!

    One thing we just noticed is that your webhook has a 98% failure rate.

    Is this the log?

    Event data
    {
    “id”: “pi_0Geof4D9kjA28je2WFIIn3Gf”,
    “object”: “payment_intent”,
    “last_payment_error”: null,
    “livemode”: true,
    “next_action”: null,
    “status”: “succeeded”,
    “allowed_source_types”: [
    “card”
    ],
    “amount”: 21944,
    “amount_capturable”: 0,
    “amount_received”: 21944,
    “application”: “ca_Gp4vLOJiqHJLZGxakHW7JdbBlcgWK8Up”,
    “application_fee_amount”: null,
    “canceled_at”: null,
    “cancellation_reason”: null,
    “capture_method”: “automatic”,
    “charges”: {
    “object”: “list”,
    “data”: [
    {
    “id”: “ch_HDF9013BPDchcU”,
    “object”: “charge”,
    “amount”: 21944,
    “amount_refunded”: 0,
    “application”: “ca_Gp4vLOJiqHJLZGxakHW7JdbBlcgWK8Up”,
    “application_fee”: null,
    “application_fee_amount”: null,
    “balance_transaction”: “txn_HDF9oMZVvPhfT1”,

    }

    Thread Starter joyryde

    (@joyryde)

    Looks like the webhook had one success on May 1st when we first installed the plugin, and then 100% of the charges since then failed.

    All Apple Pay payments fail because of Stripe Radar rules that are intended only for credit cards, we have a support request into Stripe for that.

    And this issue with this guys payment getting through without 3D secure seems to be the other issue now.

    Plugin Author Payment Plugins

    (@mrclayton)

    @joyryde,

    Our plugin very rarely has webhook failures so I recommend you look to see what url your webhooks are pointing to. I remember a previous support request you created where you confused my plugin for the other Stripe plugin by WooCommerce. I bet you still have their webhook url active in your Stripe settings.

    Looks like the webhook had one success on May 1st when we first installed the plugin, and then 100% of the charges since then failed. Are you talking about webhooks failing or charges failing? It’s not clear.

    The log you provided is what I am looking for but are you 100% sure it’s for the correct order? I don’t see attributes specific to our plugin, mainly in the metadata of the payment intent we include the gateway_id, order_id, and other info.

    What is your stripe account id? You can locate it on the plugin’s API Settings page. That will allow me to look at your logs.

    Kind Regards,

    Thread Starter joyryde

    (@joyryde)

    Hello!

    We deleted the old plugin and their webhook, because yours is superior and your support is far better.

    We only have your webhook, and we only see your plugin in our checkout screen and settings.

    Thread Starter joyryde

    (@joyryde)

    The successful payment that came in prior to the one that bypassed 3D secure says this:

    Timeline

    Add note
    3D Secure was attempted for this payment, but the customer hasn’t been verified by their bank. This payment is still protected from being disputed for fraud.
    May 3, 2020, 5:54 PM
    Payment succeeded
    This payment doesn’t qualify for Chargeback Protection because it wasn’t made through Checkout.
    May 3, 2020, 5:54 PM
    1
    Stripe risk evaluation: normal
    May 3, 2020, 5:54 PM
    Payment started
    May 3, 2020, 5:54 PM

    Plugin Author Payment Plugins

    (@mrclayton)

    @joyryde

    Please provide your stripe account ID. With that account ID I can look up your account’s logs and view the entry for the payment intent in question.

    Kind regards,

    Thread Starter joyryde

    (@joyryde)

    The account ID should be D9kjA28je2YEqvvSk1j49TDDADfZviqY

    We just double checked the webhook URL and secret, both match.

    Thread Starter joyryde

    (@joyryde)

    All of the transactions from May 1st to today should have been via your plugin, as that’s when we removed the Woocommerce one.

    Plugin Author Payment Plugins

    (@mrclayton)

    @joyryde,

    Did you perform a webhook connection test? I recommend you do that and see what the response. What are all the url’s you see in your Stripe webhook settings?

    I looked up that particular order using the account ID you provided. It contains the correct property:

    "payment_method_options": {
        "card": {
          "installments": null,
          "request_three_d_secure": "any"
        }
      },

    You will need to reach out to Stripe support and have them provide an explanation on why this passed 3D Secure even though the correct value of any was provided to the API by the plugin. Please keep me in the loop on what they reply with.

    Kind Regards,

    Thread Starter joyryde

    (@joyryde)

    We tried but nowhere on the Stripe Webhook page is any such test button. We looked 5 times and can’t see anything that looks like the one in your documentation.

    We will open another Stripe support ticket for this now, we have the one opened for why they keep declining every single Apple Pay transaction too.

    Plugin Author Payment Plugins

    (@mrclayton)

    @joyryde,

    To make the test button appear, you must enable the “View test data” option located on the left hand navigation menu.

    Please provide the url’s for your configured webhooks. I can’t view them using the account ID as Stripe restricts some info from Partners.

    Update: I pinged your website using the webhook url our plugin uses and it was received. So I suspect there is an issue with the url you have configured in your Stripe Webhook settings.

    Kind Regards,

    Thread Starter joyryde

    (@joyryde)

    We can’t select the Test Data button because it hides the webhooks. They only appear if you turn that button off.

    the URL is https://djdeals.com/wp-json/wc-stripe/v1/webhook

    Thread Starter joyryde

    (@joyryde)

    When we try to look at the webhook and then click the test mode button, it says:

    Did you mean live mode?
    We couldn’t find what you were looking for in test mode, but we found it in live mode.

    Plugin Author Payment Plugins

    (@mrclayton)

    Click Home > View test data > Developers > Webhooks

    Or just provide me with some of the failed webhook log entries. Those should say why the webhook failed.

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