Client invoice payment flow

Understand invoice restriction checks

Know that both payment-page and callback access validate invoice ID and hash.

Audience: CRM staffPermission: Invoice recipient / configured staffModule v1.0.0

Exact navigationCustomer invoice URL → Stripe iDEAL V2

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

Know that both payment-page and callback access validate invoice ID and hash. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.

Exact step-by-step process

Use the original customer invoice link.
Do not edit the invoice ID or hash.
Restart from the invoice if access is rejected.

Fields, choices and supported possibilities

Guardcheck_invoice_restrictions(id, hash)

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

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

Code-backed validations and workflow rules

The flow follows the supplied controller and Stripe Session configuration.

Expected result and verification

Understand invoice restriction checks 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.