All Stripe Webhook Tests Return 400 and Have This Error
Has anybody seen this when trying to test strip webhooks . - seems to be no matter what event I send...
No signatures found matching the expected signature for payload
/home/sysprog/.rvm/gems/ruby-2.6.5/gems/stripe-5.11.0/lib/stripe/webhook.rb:73:in `verify_header'
/home/sysprog/.rvm/gems/ruby-2.6.5/gems/stripe-5.11.0/lib/stripe/webhook.rb:13:in `construct_event'
/home/sysprog/.rvm/gems/ruby-2.6.5/gems/stripe_event-2.3.0/app/controllers/stripe_event/webhook_controller.rb:24:in `block in verified_event'
/home/sysprog/.rvm/gems/ruby-2.6.5/gems/stripe_event-2.3.0/app/controllers/stripe_event/webhook_controller.rb:22:in `each'
-Andy
No signatures found matching the expected signature for payload
/home/sysprog/.rvm/gems/ruby-2.6.5/gems/stripe-5.11.0/lib/stripe/webhook.rb:73:in `verify_header'
/home/sysprog/.rvm/gems/ruby-2.6.5/gems/stripe-5.11.0/lib/stripe/webhook.rb:13:in `construct_event'
/home/sysprog/.rvm/gems/ruby-2.6.5/gems/stripe_event-2.3.0/app/controllers/stripe_event/webhook_controller.rb:24:in `block in verified_event'
/home/sysprog/.rvm/gems/ruby-2.6.5/gems/stripe_event-2.3.0/app/controllers/stripe_event/webhook_controller.rb:22:in `each'
-Andy
Ran into this today. The Stripe CLI listen command outputs your webhook signing secret when you connect. It is based on your device name and api key, so as long as those do not change, the secret shouldn't either. You can add it to your development credentials under stripe/signing_secret to eliminate the 400 errors.
Notifications
You’re not receiving notifications from this thread.