Handle a Stripe API error during callback
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Return safely to the invoice when Session or PaymentIntent retrieval fails.
Where to goStripe return → iDEAL callback → Invoice
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
Return safely to the invoice when Session or PaymentIntent retrieval fails. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Follow these steps
- Read the failure alert.
- Check Stripe API availability and keys.
- Verify the transaction in Stripe before retrying to avoid duplicate customer action.
Fields and options
Caught exceptionStripe ApiErrorException
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 Stripe API error during callback 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.