Understand the gateway key-check implementation caveat
Know that the internal helper returns true when the stored secret is empty.
Exact navigationTechnical review → Ideal_gateway::isGatewayKeyConfigured
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 that the internal helper returns true when the stored secret is empty. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Exact step-by-step process
- Rely on the settings activation guard and deployment tests.
- Do not bypass normal settings activation.
- Treat this as a supplied-code limitation for future remediation.
Fields, choices and supported possibilities
ImplementationEmpty secret returns true
Compensating controlSettings activation guard checks submitted keys
Category/help-centre/category/stripe-ideal-payment-gateway/
Topic/help-centre/topic/stripe-ideal-security-troubleshooting/
Code-backed validations and workflow rules
- The helper behaviour is counter-intuitive and should not be represented as successful configuration.
Expected result and verification
- Understand the gateway key-check implementation caveat 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
- Protect credentials and invoice/payment data.
- Verify Stripe state before any retry or manual finance correction.