Understand callback and webhook payment labels
Recognise why labels can differ depending on which path records first.
Exact navigationInvoice → Payment record
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
Recognise why labels can differ depending on which path records first. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Exact step-by-step process
- Open the payment record.
- Use transaction ID—not only the label—to reconcile with Stripe.
Fields, choices and supported possibilities
Callback labelIDEAL
Webhook labelIDEAL - {PaymentIntent source}
Category/help-centre/category/stripe-ideal-payment-gateway/
Topic/help-centre/topic/stripe-ideal-payment-recording/
Code-backed validations and workflow rules
- The first idempotent path to record the transaction determines the stored label.
Expected result and verification
- Understand callback and webhook payment labels 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.