A Stripe webhook is an automatic message Stripe sends to your website whenever something happens to a payment or subscription. When a renewal succeeds, a card is declined, or a member cancels, Stripe “calls” your site at a special URL and tells it what just happened — so your site can react.
Think of it as Stripe tapping your site on the shoulder. Instead of your site constantly asking Stripe “anything new? anything new?”, Stripe proactively notifies you the moment an event occurs.
Why membership sites depend on webhooks
This is the part that’s invisible until it breaks. With recurring billing, the important events happen on Stripe’s schedule, not yours — a monthly renewal charges automatically, a card expires and a payment fails, a member cancels from their account. Your WordPress site isn’t involved in those moments unless Stripe tells it.
Webhooks are how your site finds out. Without them, your site wouldn’t know that:
- A renewal succeeded, so the member should keep access for another cycle.
- A payment failed, so access may need to pause and the member should be nudged to update their card.
- A member cancelled, so access should end at the right time.
In short: webhooks are what keep access in sync with payment. Hosted checkout tells your site about the first payment; webhooks tell it about everything that happens afterward.
What happens when a webhook fails
This is where first-hand experience matters, because the failure mode is subtle. If a renewal webhook doesn’t reach your site — a misconfigured endpoint, a server hiccup, a missing signing secret — your site never hears that the payment went through. From the member’s side, they paid, but your site still thinks their last-known status applies. Access can drift out of sync with reality: someone who paid loses access, or someone who cancelled keeps it longer than they should.
That’s why correct webhook setup isn’t a nice-to-have. A membership site that takes recurring payments but doesn’t reliably receive webhooks will eventually have members and access records that disagree — and a stack of confusing support tickets.
A note on webhook security
Because a webhook is just a URL your site exposes, Stripe signs each message with a signing secret so your site can verify it genuinely came from Stripe and wasn’t forged. Verifying that signature is an important part of doing webhooks safely — you don’t want your site acting on fake “payment succeeded” messages.
How Members Only approaches it
Members Only uses Stripe webhooks to keep membership access in step with subscription events — renewals, failed payments, and cancellations — so what your site believes matches what Stripe knows. It can also send email notifications on those events (a new subscription, a successful renewal, a failed payment), and exposes actions and filters so developers can run custom code when Stripe events are processed. Setup is covered in Connecting to Stripe.
Next step
To set up your Stripe connection and webhooks, see Connecting to Stripe. For developer hooks around payment events, see Actions and Filters.
Related terms: What Is Hosted Checkout?, What Is Recurring Billing?, Cancel at the End of the Billing Period, What Is Stripe Test Mode?