Stripe webhook management

Understand the required Stripe webhook event

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

The module subscribes only to successful PaymentIntent events.

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

The module subscribes only to successful PaymentIntent events. 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.
Check the webhook warning or existing Stripe endpoint.
Verify payment_intent.succeeded is enabled.

Fields and options

Required eventpayment_intent.succeeded

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

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

Rules and limits

idealModuleWebhookEvents returns only Stripe Event TYPE_PAYMENT_INTENT_SUCCEEDED.

Check it worked

Understand the required Stripe webhook event 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.