Troubleshoot an iDEAL payment that is not recorded
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Check callback, webhook, transaction ID and CRM addPayment outcome before retrying.
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 this guide helps you do
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
EvidencePaymentIntent ID, Session status, webhook delivery
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
- 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.
Related guides
Was this guide useful?Your response is stored only in this browser.