Understand matching-endpoint deletion during creation
This guide explains that which Stripe endpoints the create action can delete. The guide then takes you through the correct route, the checks to complete before making changes, the workflow in order, and the evidence to review afterwards.
Where to goAdmin Area → Setup → Settings → Payment Gateways → Stripe iDEAL V2 → Create/Re-create 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 you’ll accomplish
Know which Stripe endpoints the create action can delete. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Follow these steps
- Before selecting Create or Re-create, review existing Stripe endpoints.
- Verify no unrelated endpoint uses the same exact URL.
- Run the action and verify the remaining endpoint.
Fields and options to review
Match 1metadata.identification_key
Match 2Exact webhook URL
Category/help-centre/category/stripe-ideal-payment-gateway/
Topic/help-centre/topic/stripe-ideal-webhook-management/
Rules the system enforces
- The controller deletes every endpoint matching the module identification key or exact endpoint URL before creating the new one.
How to confirm it worked
- Understand matching-endpoint deletion during creation 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 correct Stripe test/live account and protect signing credentials.
- Do not call webhook-management routes from an untrusted session.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.