Security, limitations and troubleshooting

Understand unsupported webhook events

Do not expect failed, cancelled, refunded or chargeback events to be processed.

Audience: CRM staffPermission: Administrator / finance / technical supportModule v1.0.0
Exact navigationStripe Dashboard → Webhook endpoint
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

Do not expect failed, cancelled, refunded or chargeback events to be processed. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.

Exact step-by-step process

  1. Review other Stripe events in Stripe Dashboard.
  2. Handle failures/refunds/disputes under separate operational procedures.

Fields, choices and supported possibilities

Handled eventpayment_intent.succeeded only
Category/help-centre/category/stripe-ideal-payment-gateway/
Topic/help-centre/topic/stripe-ideal-security-troubleshooting/

Code-backed validations and workflow rules

  • The supplied module implements or omits this behaviour exactly as described.

Expected result and verification

  • Understand unsupported webhook events 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.