Stripe webhook management

Enable a disabled Stripe webhook from the CRM

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Re-enable the stored endpoint when the gateway warning reports disabled status.

Audience: CRM staffPermission: Administrator / settings accessModule v1.0.0

Jump to steps

Where to goAdmin Area → Setup → Settings → Payment Gateways → Stripe iDEAL V2 → Enable webhook

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

Re-enable the stored endpoint when the gateway warning reports disabled status. 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.
Select the enable link in the disabled-webhook warning.
Reload the page.
Verify the endpoint status is enabled.

Fields and options

Required permissionEdit settings

Category/help-centre/category/stripe-ideal-payment-gateway/

Topic/help-centre/topic/stripe-ideal-webhook-management/

Rules and limits

enable_webhook performs the API update only when staff_can(edit, settings) is true.

Check it worked

Enable a disabled Stripe webhook from the CRM 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.

Was this guide useful?Your response is stored only in this browser.