Protecting subscriptions as the Payhip webhook list grows
I began staging a central Payhip Webhook Hub so a growing number of SaaSYeti subscriptions can eventually be handled without relying on an overcrowded list of webhook URLs.
As the SaaSYeti portfolio grew, I ran into a very practical limitation: Payhip's webhook settings were becoming difficult to manage across multiple applications.
The solution under test is a separate central Webhook Hub that can route events to the correct application, keep logs and recover from failures. The highest priority is preserving existing Payhip and Stripe subscriptions and making sure customers do not unexpectedly lose access.
The Hub has been installed in a staging environment for testing. I deliberately kept it separate from live webhook delivery while checking product mapping, safety and rollback. I would rather take longer here than risk an interruption to someone's paid subscription.
What I learned: behind-the-scenes subscription plumbing deserves the same care as the public sales page.