Handle a missing callback session ID
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
This guide explains why the callback silently returns to the invoice.
Where to goStripe return → iDEAL callback
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
Understand why the callback silently returns to the invoice. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Follow these steps
- Return through the Stripe Checkout flow.
- If no session ID is present, restart the payment from the invoice.
- Do not manually construct the callback URL.
Fields and options
Required querysession_id
Category/help-centre/category/stripe-ideal-payment-gateway/
Topic/help-centre/topic/stripe-ideal-client-payment-flow/
Rules and limits
- The flow follows the supplied controller and Stripe Session configuration.
Check it worked
- Handle a missing callback session ID 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.
Related guides
Was this guide useful?Your response is stored only in this browser.