Keep test and live Stripe keys in the same environment
Prevent environment and webhook mismatches. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
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 you’ll accomplish
Prevent environment and webhook mismatches. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Follow these steps
- Select test or live operation.
- Enter both keys from that Stripe environment.
- Save settings.
- Create or recreate the webhook for the same environment.
Fields and options to review
Test detectionSecret contains sk_test
OtherwiseProduction
Category/help-centre/category/stripe-ideal-payment-gateway/
Topic/help-centre/topic/stripe-ideal-settings-activation/
Rules the system enforces
- The environment label is inferred from whether the secret key contains sk_test.
How to confirm it worked
- 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.