Understand bank selection ownership
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
This guide explains that that Stripe embedded Checkout—not the CRM module—presents eligible iDEAL bank/payment steps.
Where to goStripe iDEAL V2 embedded checkout
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 Stripe embedded Checkout—not the CRM module—presents eligible iDEAL bank/payment steps. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Follow these steps
- Do not expect a bank list in CRM settings.
- Complete the choices presented by Stripe Checkout.
Fields and options
Bank UIProvided by Stripe
Category/help-centre/category/stripe-ideal-payment-gateway/
Topic/help-centre/topic/stripe-ideal-security-troubleshooting/
Rules and limits
- The supplied module implements or omits this behaviour exactly as described.
Check it worked
- Understand bank selection ownership 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
- Protect credentials and invoice/payment data.
- Verify Stripe state before any retry or manual finance correction.
Related guides
Was this guide useful?Your response is stored only in this browser.