Recreate a mismatched Stripe webhook
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Follow this guide to delete the old matching endpoint and replace stored webhook credentials.
Where to goAdmin Area → Setup → Settings → Payment Gateways → Stripe iDEAL V2 → Webhook ID mismatch → Re-create
Before you start
- Use the exact navigation above and confirm the intended invoice, case, client, property, document or environment.
- Verify module activation and the stated permission before attempting the action.
- Use a controlled test record for payments, emails, public/portal access, provider calls and deletion.
What this guide helps you do
Delete the old matching endpoint and replace stored webhook credentials. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Follow these steps
- Go to the gateway tab.
- Use the re-create link only after confirming the intended Stripe environment.
- Allow the module to remove matching old endpoints and create a new one.
- Check the stored ID and new signing secret.
Fields and options
Action route/ideal/create_webhook?recreate=true
Category/help-centre/category/stripe-ideal-payment-gateway/
Topic/help-centre/topic/stripe-ideal-webhook-management/
Rules and limits
- The recreate query clears the stored webhook ID and signing secret before creating the replacement.
Check it worked
- Recreate a mismatched Stripe webhook completes through the supplied module flow.
- Reopen the source record or settings page and verify the stored value, status, payment, file, timeline entry or notification.
Security, privacy and operational checks
- Use the correct Stripe test/live account and protect signing credentials.
- Do not call webhook-management routes from an untrusted session.
Related guides
Was this guide useful?Your response is stored only in this browser.