When you run an anonymized data refresh from production to a staging environment, the system removes webhook definitions. This keeps your testing data safe and prevents it from reaching your live production systems.
How the data refresh works
The "refresh from production" process completely replaces your sandbox or staging database; it does not merge new data with what is already there.
Instead, the system wipes the current staging database and replaces it with a sanitized copy of your production data. This process anonymizes customer information and strips out sensitive credentials so the environment is safe for testing.
Why webhooks are removed
The system removes webhook definitions for safety. If the refresh copied production webhooks to your staging environment, your testing could send data to your live production endpoints.
The system also removes credentials for payment gateways and third-party integrations. This stops the staging environment from triggering real payments or connecting to live external systems.
Managing webhooks after a refresh
Because the refresh replaces the database, you lose any webhooks you previously set up in the staging environment.
If you need webhooks for testing after a refresh, you must recreate them manually. Make sure to configure these new webhooks to point to your testing or staging endpoints, not your production URLs.
Related articles