WebHook Stripe : Error 400

  • Resolved Fantou

    (@fantou)


    1 year, 7 months ago

    Hello

    My Webhook Stripe returns a perfect 100% score of : error 400.. ??
    The only message there is in the Stripe Dashboard for the answer is :

    400 (Bad Request)
    -1

    I checked the differents keys and it’s ok. I tried with a new webhook : same problem.

    When I test the connexion Stripe/WooCommerce, the plugin WooCommerce Stripe Gateaway says “it’s ok”.
    Paiements are received

    I tried to disable plugin and enable one by one and webhook have a 200 statut on Stripe Dashboard only if WooCommerce is disabled…
    It’s a bit weird like of course, I did not receive it (I’m using Plugin “WooCommerce Stripe Gateaway” for connecting WooCommerce and Stripe and when WooCommerce is deactivated, this plugin is not working.)

    I’ve checked the time zones and it’s ok.

    I’ve contacted Stripe support but with no results.

    I did not find some relevant errors in the server logs

    So I’m posting here this problem in case you have some idea to resolve this. Because I don’t know anymore where to search for resolving it… ^^

    • This topic was modified 1 year, 7 months ago by Fantou.
Viewing 2 replies - 1 through 2 (of 2 total)
  • Thread Starter Fantou

    (@fantou)

    Re-hello,

    Just for information : I replace the “WooCommerce Stripe Gateaway” plugin by “Payment Plugins for Stripe WooCommerce” and I have no more the webhook problem.

    Have a nice day!

    Hi @fantou

    We appreciate your updates on this thread.

    This 400 (Bad Request) error usually indicates that the server couldn’t understand the request due to invalid syntax, sometimes due to some conflicting plugins. We recommend ensuring that the plugins are up-to-date if you encounter the same issue in the future.

    Please don’t hesitate to start a new topic if you have any more questions down the line.

    Have a fantastic day!

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘WebHook Stripe : Error 400’ is closed to new replies.