Handle a CRM payment-record database failure
Recognise the callback alert when addPayment returns false.
Exact navigationStripe return → Invoice
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 the callback alert when addPayment returns false. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Exact step-by-step process
- Confirm the PaymentIntent succeeded in Stripe.
- Check the CRM invoice for a payment row.
- Do not ask the customer to pay again until reconciliation is complete.
- Investigate CRM logs/database.
Fields, choices and supported possibilities
Alertonline_payment_recorded_success_fail_database
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
- Handle a CRM payment-record database failure 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.