Understand invoice and attempt metadata
This guide explains that what the module stores on the PaymentIntent. 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 goStripe Checkout Session → PaymentIntent metadata
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 what the module stores on the PaymentIntent. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.
Follow these steps
- Start a controlled payment.
- Inspect the PaymentIntent metadata in Stripe.
- Match invoice_id and attempt_reference to the CRM invoice/payment attempt.
Fields and options to review
invoice_idCRM invoice ID
attempt_referenceCore payment-attempt reference
attempt_feeCore payment-attempt fee
Category/help-centre/category/stripe-ideal-payment-gateway/
Topic/help-centre/topic/stripe-ideal-payment-recording/
Rules the system enforces
- The supplied callback/webhook code applies this rule before or during addPayment.
How to confirm it worked
- Understand invoice and attempt metadata 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.