Keep test and live Stripe keys in the same environment
Prevent environment and webhook mismatches.
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
Prevent environment and webhook mismatches. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Exact step-by-step process
- Choose test or live operation.
- Enter both keys from that Stripe environment.
- Save settings.
- Create or recreate the webhook for the same environment.
Fields, choices and supported possibilities
Test detectionSecret contains sk_test
OtherwiseProduction
Category/help-centre/category/stripe-ideal-payment-gateway/
Topic/help-centre/topic/stripe-ideal-settings-activation/
Code-backed validations and workflow rules
- The environment label is inferred from whether the secret key contains sk_test.
Expected result and verification
- Keep test and live Stripe keys in the same environment 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 least-privilege account that has the stated permission.
- Use a controlled test record before applying provider, financial, public-link, email or destructive actions in production.