Understand webhook environment detection
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
This guide explains that why the settings warning says test or production.
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
Know why the settings warning says test or production. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Follow these steps
- Check the configured secret key environment.
- Go to the gateway tab.
- Verify the warning references the intended environment.
Fields and options
Test ruleSecret key contains sk_test
Production ruleAll other secret-key values
Category/help-centre/category/stripe-ideal-payment-gateway/
Topic/help-centre/topic/stripe-ideal-webhook-management/
Rules and limits
- Environment detection is string-based and does not call Stripe to determine mode.
Check it worked
- Understand webhook environment detection 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.