Unable to setup stripe

  • Resolved pinano

    (@pinano)


    2 days, 13 hours ago

    When inserting the secret stripe key and saving it i get the following error: Creating the Stripe webhook failed, so paid bookings are not marked as paid. Saving the Stripe settings tries again. Use the Check setup button to see what went wrong.

    I see nevertheless that the key is saved but when I do a Setup Check if gives the following error at the end:

    • Stripe accepts the API key
    • ✓ A webhook for this site exists in Stripe (https://de5er.be?seatreg=stripe-webhook-callback)
    • ✓ The webhook is enabled in Stripe
    • ✓ The webhook listens to all events the plugin needs
    • ✗ A webhook signing secret is saved for this registration (Save the Stripe settings again to fix this)
Viewing 8 replies - 1 through 8 (of 8 total)
  • Plugin Author Siim Kirjanen

    (@thesiim)

    2 days, 11 hours ago

    Hey
    Could you go to the Stripe settings, untick “Turn on Stripe payments” and save, then tick it again and save? That recreates the setup from scratch and should fix it.

    Thread Starter pinano

    (@pinano)

    2 days, 11 hours ago

    No, this doesn’t fix it. Tried it serveral times now

    Thread Starter pinano

    (@pinano)

    2 days, 11 hours ago

    Just as some more info, I use wordpress 7.1

    Plugin Author Siim Kirjanen

    (@thesiim)

    2 days, 11 hours ago

    Do you have access to your site database? Can you check couple of things? Look for seatreg_options table. It should have column stripe_webhook_secret on your registration row. Is that column NULL? Also check stripe_webhook_url column.

    Plugin Author Siim Kirjanen

    (@thesiim)

    2 days, 10 hours ago

    I might have found the issue. Will create a fix. You might not have the related columns in db.

    Thread Starter pinano

    (@pinano)

    2 days, 10 hours ago

    Just to inform you, stripe_webhook_secret is there but is empty. stripe_webhook_url isn’t found

    Thread Starter pinano

    (@pinano)

    2 days, 10 hours ago

    Issue can be closed. version 1.76.0 fixed the issue, thx!

    Plugin Author Siim Kirjanen

    (@thesiim)

    2 days, 10 hours ago

    That is good news. Thank you for reporting the issue.

Viewing 8 replies - 1 through 8 (of 8 total)

You must be logged in to reply to this topic.