Record a successful payment from the Stripe webhook
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Allow signed payment_intent.succeeded events to create the invoice payment.
Where to goStripe webhook → /ideal/webhook
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
Allow signed payment_intent.succeeded events to create the invoice payment. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Follow these steps
- Keep the webhook enabled and signing secret valid.
- Complete a payment.
- Check Stripe sends payment_intent.succeeded.
- Check the invoice payment record.
Fields and options
AmountPaymentIntent amount ÷ 100
Payment methodIDEAL - {source}
Category/help-centre/category/stripe-ideal-payment-gateway/
Topic/help-centre/topic/stripe-ideal-payment-recording/
Rules and limits
- The supplied callback/webhook code applies this rule before or during addPayment.
Check it worked
- Record a successful payment from the Stripe webhook 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.