v5.3.3
Payment webhook and dispute-alert routes now only accept BACKEND_MANAGER_WEBHOOK_KEY,
matching the marketing webhook routes. The legacy BACKEND_MANAGER_KEY fallback
(added in Phase 1 for gradual migration) is removed — all consumer brands must
have BACKEND_MANAGER_WEBHOOK_KEY set and registered with their payment providers.