Overview, requirements and lifecycle

Understand Stripe iDEAL V2

Identify the module as an EUR-only Stripe embedded Checkout gateway for invoice payments. 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.

Audience: CRM staffPermission: Administrator / settings accessModule v1.0.0
Jump to steps
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

Identify the module as an EUR-only Stripe embedded Checkout gateway for invoice payments. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.

Follow these steps

  1. Go to the payment-gateway settings page.
  2. Find Stripe iDEAL V2 in the online payment gateways.
  3. Check the configured keys, EUR currency and description before activation.
  4. Use a controlled EUR invoice to verify the customer payment option.

Fields and options to review

Module nameStripe Ideal V2
Gateway display nameStripe iDEAL V2
Module version1.0.0
Minimum CRM version3.1.6
Gateway IDIdeal_gateway
Category/help-centre/category/stripe-ideal-payment-gateway/
Topic/help-centre/topic/stripe-ideal-overview-lifecycle/

Rules the system enforces

  • The module registers a payment gateway, not a separate sidebar workspace.
  • The provider flow uses Stripe embedded Checkout with payment_method_types set to ideal.

How to confirm it worked

  • Understand Stripe iDEAL V2 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.