Verify the payment-attempt reference
Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.
Confirm the CRM payment record receives the original attempt reference.
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 this guide helps you do
Confirm the CRM payment record receives the original attempt reference. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Follow these steps
- Go to the successful invoice payment.
- Compare the stored attempt reference with the PaymentIntent metadata.
Fields and options
Fieldpayment_attempt_reference
Category/help-centre/category/stripe-ideal-payment-gateway/
Topic/help-centre/topic/stripe-ideal-payment-recording/
Rules and limits
- The supplied callback/webhook code applies this rule before or during addPayment.
Check it worked
- Verify the payment-attempt reference 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.
Related guides
Was this guide useful?Your response is stored only in this browser.