Customer work, connected.

Help & supportMyAccount
Security, limitations and troubleshooting

Understand the absence of an iDEAL report

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

Follow this guide to use core invoice payments and Stripe Dashboard for reporting.

Audience: CRM staffPermission: Administrator / finance / technical supportModule v1.0.0
Jump to steps
Where to goAdmin Area → Sales → Invoices / 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

Use core invoice payments and Stripe Dashboard for reporting. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.

Follow these steps

  1. Filter core invoice payments.
  2. Use PaymentIntent IDs to reconcile with Stripe.

Fields and options

Dedicated module reportNot implemented
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 the absence of an iDEAL report 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.

Search the platform, integrations and practical Help Centre guides.

Press Esc to close.Browse every page