Understand webhook environment detection
Know why the settings warning says test or production.
Exact navigationAdmin Area → Setup → Settings → Payment Gateways → Stripe iDEAL V2
Before you begin
- Use the exact navigation above and confirm the intended invoice, case, client, property, document or environment.
- Confirm 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 covers
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.
Exact step-by-step process
- Review the configured secret key environment.
- Open the gateway tab.
- Confirm the warning references the intended environment.
Fields, choices and supported possibilities
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/
Code-backed validations and workflow rules
- Environment detection is string-based and does not call Stripe to determine mode.
Expected result and verification
- 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.