Reconcile an iDEAL payment with Stripe
Match amount, invoice metadata, attempt reference and PaymentIntent ID.
Exact navigationAdmin Area → Sales → Invoices → Invoice → Payments and Stripe Dashboard
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
Match amount, invoice metadata, attempt reference and PaymentIntent ID. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Exact step-by-step process
- Open the CRM invoice payment.
- Open the matching PaymentIntent in Stripe.
- Compare amount, invoice_id metadata and attempt_reference.
- Resolve any missing record before retrying customer payment.
Fields, choices and supported possibilities
Primary keyPaymentIntent ID
Amount unitsStripe cents converted to CRM decimal amount
Category/help-centre/category/stripe-ideal-payment-gateway/
Topic/help-centre/topic/stripe-ideal-payment-recording/
Code-backed validations and workflow rules
- The supplied callback/webhook code applies this rule before or during addPayment.
Expected result and verification
- Reconcile an iDEAL payment with Stripe 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.