wrong webhook

Resolved GregHP
(@greghp)

6 months, 3 weeks ago

Hi,

I use Ultimate Membership PRO + WooCommerce and WooCommerce Stripe Payment Gateway.

Since the Stripe update on the UMP and WooCommerce (last update with stripe connect), I’ve been having problems with informations being passed between the payment and the membership… The Stripe update (Stripe Connect) changes the webhook, so I reconfigured a new webhook and endpoint for it works with UMB.

On the WooCommerce side, i’ll try logging out of the account, deactivate the Stripe Gateway extension, clearing the cache, and deleting the old webhook from the Stripe account…Damn it automatically recreates the old webhook and the plugin reconnectes again the wrong webhook… I tried to modify or delete the old webhook in the database, but it doesn’t store it, or it’s managed via the API…

I’ve tried everything, but nothing works… Since it points to the wrong webhook (which recreates itself every time),

Thank you for your help…how to fix it?

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

Plugin Support Frank Remmy (woo-hc)
(@frankremmy)

6 months, 3 weeks ago
Hi @greghp,

Thanks so much for reaching out, and I can absolutely understand how frustrating it is to see the wrong webhook persist despite your efforts to reset it.

What you’re experiencing is tied to how the Stripe plugin manages its webhook registration. When the plugin is activated or reconnected, it automatically creates a default webhook endpoint in Stripe to ensure it can receive essential event notifications. This was introduced in version version 8.6.1: https://woocommerce.com/document/stripe/setup-and-configuration/stripe-webhooks/#reconfiguring.

It’s possible that this behavior can override custom webhook configurations, especially when integrating with other systems like Ultimate Membership Pro (UMP).

Here’s what we recommend to help you move forward:
- Check Stripe and confirm that your webhook URL for our plugin is to this endpoint: https://www.example.com/?wc-api=wc_stripe. Is it also the same for UMP?
- Temporarily deactivate the Stripe plugin. This will prevent it from auto-registering the webhook while you configure UMP’s endpoint.
- Manually set up your preferred webhook in Stripe. Make sure it includes only the events required by UMP. You can find these in their documentation or support resources.
- After UMP’s webhook is in place, reactivate the plugin. If it recreates the default WooCommerce webhook again, you may need to leave both endpoints active, but ensure they don’t conflict.
Let us know your findings!
Thread Starter GregHP
(@greghp)

6 months, 3 weeks ago
Hi Franck Remmy,

Thanks for your answer!

Since the Stripe update, the webhook has changed. I had to create the one requested by UMB => ?ihc_action=stripe_connect, then I added the new webhook with the endpoints requested by UMB. on my Stripe account.

Each time, the old webhook is automatically recreated as soon as the connection to the account is made…

I can actually leave both, but UMB can no longer manage memberships because the Stripe Gateway + Wocommerce plugin is linked to a different webhook than UMB and Some types of membership do not works correctly
- This reply was modified 6 months, 3 weeks ago by GregHP.
- This reply was modified 6 months, 3 weeks ago by GregHP.
- This reply was modified 6 months, 3 weeks ago by GregHP.
- This reply was modified 6 months, 3 weeks ago by GregHP.
Moses M. (woo-hc)
(@mosesmedh)

6 months, 3 weeks ago

Hi @greghp,

Thanks for getting back and for the detailed explanation. From what you’ve described, it looks like you’re trying to make WooCommerce Stripe use the same endpoint as UMP.

To clarify, WooCommerce Stripe and UMP can each have their own endpoint — they don’t need to match. The key is making sure both endpoints are set up in your Stripe dashboard. Stripe supports multiple endpoints.

Once both are in place, you can go to Stripe Dashboard > Developers > Webhooks and specify which events go to each endpoint. For example, WooCommerce could handle order/payment events, while UMP receives only membership-related events.

It’s also possible the issue isn’t with the endpoints but with UMP’s settings and endpoint. You can test this by disabling WooCommerce Stripe temporarily and running payments through UMP alone to see if it works.

Since this involves a third-party plugin integrating with WooCommerce and Stripe, it’s not something we can fully troubleshoot here. The best step would be to reach out directly to UMP support, as they’ll be in the best position to guide you on resolving or working around this issue.

Thread Starter GregHP
(@greghp)

6 months, 3 weeks ago

Hi,

indeed, if I disable the WooCommerce Payment Integration module, everything works… Memberships are visible, as are members and payment history, but obviously no orders are created in WooCommerce.

Damn…UMP is really bad since the update…

Moses M. (woo-hc)
(@mosesmedh)

6 months, 3 weeks ago

Hi @greghp,

That does sound like a tough one. I’d recommend trying the workaround I mentioned earlier — keeping both endpoints active and then using your Stripe dashboard to decide which events go to which.

If you need a more customized workflow between the two plugins, you might consider reaching out to Woo experts on platforms like codeable.io. Still, the Ultimate Membership Pro support team would be in the best position to guide you, since they know their plugin inside out and can suggest the right integration approach.

Since this issue falls outside what we can handle here, I’ll go ahead and close this thread. If you have more questions, feel free to start a new topic anytime.

In the meantime, if our responses have been helpful, we’d really appreciate it if you could leave us a review based on your experience: https://wordpress.org/support/plugin/woocommerce-gateway-stripe/reviews/#new-post

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

The topic ‘wrong webhook’ is closed to new replies.