Record a successful payment from the Stripe webhook
Allow signed payment_intent.succeeded events to create the invoice payment.
Exact navigationStripe webhook → /ideal/webhook
Before you begin
- Use the exact navigation above and confirm the intended invoice, case, client, property, document or environment.
- Confirm 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 covers
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.
Exact step-by-step process
- Keep the webhook enabled and signing secret valid.
- Complete a payment.
- Verify Stripe sends payment_intent.succeeded.
- Check the invoice payment record.
Fields, choices and supported possibilities
AmountPaymentIntent amount ÷ 100
Payment methodIDEAL - {source}
Category/help-centre/category/stripe-ideal-payment-gateway/
Topic/help-centre/topic/stripe-ideal-payment-recording/
Code-backed validations and workflow rules
- The supplied callback/webhook code applies this rule before or during addPayment.
Expected result and verification
- 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.