Troubleshoot an iDEAL payment that is not recorded
Check callback, webhook, transaction ID and CRM addPayment outcome before retrying. 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 goInvoice → Payments and Stripe Dashboard
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
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.
Follow these steps
- Check Stripe for a successful PaymentIntent.
- Search the CRM invoice payments by transaction ID.
- Check webhook response and callback alert.
- Reconcile manually under approved finance controls if Stripe succeeded but CRM did not record.
Fields and options to review
EvidencePaymentIntent ID, Session status, webhook delivery
Category/help-centre/category/stripe-ideal-payment-gateway/
Topic/help-centre/topic/stripe-ideal-security-troubleshooting/
Rules the system enforces
- The supplied module implements or omits this behaviour exactly as described.
How to confirm it worked
- 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.