Troubleshoot an iDEAL payment that is not recorded
Check callback, webhook, transaction ID and CRM addPayment outcome before retrying.
Exact navigationInvoice → 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
Check callback, webhook, transaction ID and CRM addPayment outcome before retrying. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Exact step-by-step process
- Check Stripe for a successful PaymentIntent.
- Search the CRM invoice payments by transaction ID.
- Review webhook response and callback alert.
- Reconcile manually under approved finance controls if Stripe succeeded but CRM did not record.
Fields, choices and supported possibilities
EvidencePaymentIntent ID, Session status, webhook delivery
Category/help-centre/category/stripe-ideal-payment-gateway/
Topic/help-centre/topic/stripe-ideal-security-troubleshooting/
Code-backed validations and workflow rules
- The supplied module implements or omits this behaviour exactly as described.
Expected result and verification
- Troubleshoot an iDEAL payment that is not recorded 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.