Understand the saved Stripe customer branch
This guide explains that when Checkout uses an existing Stripe customer. 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.
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
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.
Follow these steps
- Go to the customer record and verify whether a Stripe customer ID exists.
- Start a controlled iDEAL payment.
- Verify the Checkout Session uses the customer association when present.
Fields and options to review
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/
Rules the system enforces
- The flow follows the supplied controller and Stripe Session configuration.
How to confirm it worked
- 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.