Gateway settings and activation

Configure the encrypted Stripe secret key

Save the server-side secret key in the gateway encrypted setting.

Audience: CRM staffPermission: Administrator / settings accessModule v1.0.0

Exact navigationAdmin Area → Setup → Settings → Payment Gateways → Stripe iDEAL V2 → API secret key

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

Save the server-side secret key in the gateway encrypted setting. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.

Exact step-by-step process

Open the gateway tab.
Paste the Stripe secret key for the intended test or live environment.
Save settings.
Return to the tab and resolve any API-key warning.

Fields, choices and supported possibilities

FieldAPI secret key

Storage declarationencrypted = true

Category/help-centre/category/stripe-ideal-payment-gateway/

Topic/help-centre/topic/stripe-ideal-settings-activation/

Code-backed validations and workflow rules

The App_gateway setting is declared encrypted.
The Stripe client decrypts this setting before API calls.

Expected result and verification

Configure the encrypted Stripe secret key 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.