Understand the create-webhook authorisation limitation
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Record that create_webhook lacks an explicit capability check.
Where to goTechnical route → /ideal/create_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
Record that create_webhook lacks an explicit capability check. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Follow these steps
- Restrict route access operationally.
- Use authenticated administrator workflows only.
- Consider hardening in the application module separately from this Help Centre.
Fields and options
Explicit guardNone in supplied method
Category/help-centre/category/stripe-ideal-payment-gateway/
Topic/help-centre/topic/stripe-ideal-security-troubleshooting/
Rules and limits
- The supplied module implements or omits this behaviour exactly as described.
Check it worked
- Understand the create-webhook authorisation limitation 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
- Protect credentials and invoice/payment data.
- Verify Stripe state before any retry or manual finance correction.
Related guides
Was this guide useful?Your response is stored only in this browser.