Understand the saved Stripe customer branch
Know when Checkout uses an existing Stripe customer.
Exact navigationCustomer Invoice → Pay Now → 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 when Checkout uses an existing Stripe customer. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Exact step-by-step process
- Open the customer record and verify whether a Stripe customer ID exists.
- Start a controlled iDEAL payment.
- Confirm the Checkout Session uses the customer association when present.
Fields, choices and supported possibilities
ConditionClient has stripe_id
Effectcustomer set and payment_method_save enabled
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 the saved Stripe customer branch 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.