Understand the missing-key activation guard
Diagnose why the gateway refuses to remain active. 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
Diagnose why the gateway refuses to remain active. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Follow these steps
- Go to the gateway tab after the failed save.
- Check both publishable and secret key fields.
- Correct the missing value.
- Save and reactivate.
Fields and options to review
Alert keyideal_gateway_cannot_be_activated_keys_not_configured
Category/help-centre/category/stripe-ideal-payment-gateway/
Topic/help-centre/topic/stripe-ideal-settings-activation/
Rules the system enforces
- The guard checks the submitted system-options payload, not only previously stored values.
How to confirm it worked
- Understand the missing-key activation guard 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.