Stripe webhook management

Verify the stored webhook ID

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

Confirm the CRM webhook ID matches the endpoint found in Stripe.

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

Jump to steps

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

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

Confirm the CRM webhook ID matches the endpoint found in Stripe. 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.
If an ID mismatch warning appears, compare the endpoint/environment in Stripe.
Use Re-create rather than editing database values manually.

Fields and options

Stored optionideal_module_stripe_webhook_id

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

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

Rules and limits

The check compares Stripe webhook object id with the stored option.

Check it worked

Verify the stored webhook ID 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.