How to configure separate webhook URLs for test and live environments when settings seem to sync across all environments?

Hi everyone,

We're new to Memberstack and are just about to go live today. However, we've encountered an issue related to webhook configuration.

When we update the webhook URL in the development settings, it seems to affect all environments. For example, we first connect our live environment to the /webhook endpoint, then later set the webhook for our test environment to /testwebhook. After doing this, the webhook for the live environment also appears to be pointing to /testwebhook.

Is this a known behavior, or should test and live environments be able to use separate webhook URLs? It's possible this could be a frontend issue, but I'm not entirely sure.

If it's expected behavior that only one webhook URL can be used across environments, it would be really helpful if there were at least a way to distinguish whether a webhook request came from a test environment—either through a header or a field in the body.

Please let me know if I'm misunderstanding something, and I’d really appreciate any guidance on how to handle this better.

Thanks,
Deniz