Overview, requirements and lifecycle

Deactivate Stripe iDEAL V2 safely

Stop offering the gateway without assuming Stripe endpoints or CRM payment records are deleted. 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 → Deactivate
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

Stop offering the gateway without assuming Stripe endpoints or CRM payment records are deleted. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.

Follow these steps

  1. First make the gateway inactive in Payment Gateways.
  2. Verify no active invoice payment is in progress.
  3. Go to Setup → Modules and deactivate Stripe Ideal V2.
  4. Check Stripe Dashboard separately if the webhook must also be disabled or removed.

Fields and options to review

CRM effectStops module execution
External effectThe code supplies no deactivation cleanup for Stripe webhooks
Category/help-centre/category/stripe-ideal-payment-gateway/
Topic/help-centre/topic/stripe-ideal-overview-lifecycle/

Rules the system enforces

  • The module defines an activation hook but no deactivation or uninstall cleanup hook.
  • Existing invoice payment records remain core CRM records.

How to confirm it worked

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