Configure the Stripe publishable key
Save the client-side Stripe publishable key used by Stripe.js. 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 → API publishable key
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
Save the client-side Stripe publishable key used by Stripe.js. 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.
- Paste the Stripe publishable key for the intended environment.
- Save settings.
- Run a controlled invoice payment and confirm embedded Checkout loads.
Fields and options to review
FieldAPI publishable key
UseStripe.js initialisation
Category/help-centre/category/stripe-ideal-payment-gateway/
Topic/help-centre/topic/stripe-ideal-settings-activation/
Rules the system enforces
- The key is exposed to Stripe.js as expected for a publishable key.
- Use the key from the same environment as the secret key.
How to confirm it worked
- Configure the Stripe publishable 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.