Understand invoice restriction checks
This guide explains that that both payment-page and callback access validate invoice ID and hash.
Where to goCustomer invoice URL → 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 this guide helps you do
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.
Follow these steps
- Use the original customer invoice link.
- Do not edit the invoice ID or hash.
- Restart from the invoice if access is rejected.
Fields and options
Guardcheck_invoice_restrictions(id, hash)
Category/help-centre/category/stripe-ideal-payment-gateway/
Topic/help-centre/topic/stripe-ideal-client-payment-flow/
Rules and limits
- The flow follows the supplied controller and Stripe Session configuration.
Check it worked
- 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.
Related guides
Was this guide useful?Your response is stored only in this browser.