Security, limitations and troubleshooting

Understand unsupported non-EUR payments

Use another gateway for invoices requiring another currency.

Audience: CRM staffPermission: Administrator / finance / technical supportModule v1.0.0
Exact navigationCustomer Invoice → Pay Now
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

Use another gateway for invoices requiring another currency. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.

Exact step-by-step process

  1. Check the invoice currency.
  2. Use Stripe iDEAL V2 only when eligible for EUR.
  3. Choose another configured gateway otherwise.

Fields, choices and supported possibilities

Supported currencyEUR only
Category/help-centre/category/stripe-ideal-payment-gateway/
Topic/help-centre/topic/stripe-ideal-security-troubleshooting/

Code-backed validations and workflow rules

  • The supplied module implements or omits this behaviour exactly as described.

Expected result and verification

  • Understand unsupported non-EUR payments 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

  • Protect credentials and invoice/payment data.
  • Verify Stripe state before any retry or manual finance correction.