All Webhook attempts with error 400

  • Resolved Beats247

    (@beats247)


    3 years, 12 months ago

    Hello there,
    I am using your WooCommerce Stripe plugin on my website but have an issue with failed webhook attempts (error 400). I have been using EDD and Stripe in the past without having any of such issues though.

    I have connected WooCommerce with Stripe through your plugin and created a new webhook in the developers section of my Stripe dashboard (url/?wc-api=wc_stripe). I created a 2016 version and also a 2020 one. All webhook attempts fail with error 400 though. Payments are going through but there seem to be issues afterwards getting to the thank you page sometimes. I already contacted the Stripe support about this twice. Their only reply was: “I completely understand the importance of dealing with the error 400 got for failing webhooks when payments were successful, I’m here for you. There is likely something wrong in your code or server. You will need to inspect your script’s code to find the problem as it’s something on your side.”

    Could you please help me out here? If you need anything else let me know. Thank you!

    The page I need help with: [log in to see the link]

Viewing 2 replies - 1 through 2 (of 2 total)
  • Plugin Support AW a11n

    (@slash1andy)

    Automattic Happiness Engineer

    Hey there!

    This is more in line with something that your host can help with if the webhooks you add to your Stripe dashboard are following the documentation for the WooCommerce plugin (and it seems that they are).

    That means that there’s an issue with the server loading the endpoints for your use. Your host should have logs and insights into why that is the case.

    Plugin Support AW a11n

    (@slash1andy)

    Automattic Happiness Engineer

    We haven’t heard back from you in a while, so I’m going to mark this as resolved – if you have any further questions, you can start a new thread.

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘All Webhook attempts with error 400’ is closed to new replies.