Overview, requirements and lifecycle

Check the supported CRM version

Verify the module-declared minimum CRM version before activation. 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: AdministratorModule v1.0.0
Jump to steps
Where to goAdmin Area → Setup → Modules → 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

Verify the module-declared minimum CRM version before activation. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.

Follow these steps

  1. Go to Setup → Modules.
  2. Find Stripe Ideal V2 and confirm version 1.0.0.
  3. Verify the CRM is version 3.1.6 or newer before activation.
  4. Do not activate on an older unsupported core version.

Fields and options to review

Required CRM version3.1.6 or newer
Module version1.0.0
Category/help-centre/category/stripe-ideal-payment-gateway/
Topic/help-centre/topic/stripe-ideal-overview-lifecycle/

Rules the system enforces

  • The requirement is declared in ideal.php.

How to confirm it worked

  • Check the supported CRM version 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.