Understand callback and webhook payment labels
Recognise why labels can differ depending on which path records first. 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 goInvoice → Payment record
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
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.
Follow these steps
- Go to the payment record.
- Use transaction ID—not only the label—to reconcile with Stripe.
Fields and options to review
Callback labelIDEAL
Webhook labelIDEAL - {PaymentIntent source}
Category/help-centre/category/stripe-ideal-payment-gateway/
Topic/help-centre/topic/stripe-ideal-payment-recording/
Rules the system enforces
- The first idempotent path to record the transaction determines the stored label.
How to confirm it worked
- 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.
Continue with related guidance
Was this guide useful?Your response is stored only in this browser.