Client invoice payment flow

Use the customer language on the iDEAL page

This guide explains how invoice client language is loaded. 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: Invoice recipient / configured staffModule v1.0.0

Jump to steps

Where to goCustomer Invoice → Pay Now → 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

Understand how invoice client language is loaded. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.

Follow these steps

Go to the invoice as the customer.
Start iDEAL payment.
Verify CRM payment labels use the client language where translations exist.

Fields and options to review

Language sourceInvoice client ID

Category/help-centre/category/stripe-ideal-payment-gateway/

Topic/help-centre/topic/stripe-ideal-client-payment-flow/

Rules the system enforces

The flow follows the supplied controller and Stripe Session configuration.

How to confirm it worked

Use the customer language on the iDEAL page 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.

Was this guide useful?Your response is stored only in this browser.