Payment recording and reconciliation
Understand payment metadata, idempotency, transaction labels and CRM invoice-payment records.
Record a successful payment from the browser callback
Create the core invoice payment after a complete Checkout Session.
Open guide →How-to guideRecord a successful payment from the Stripe webhook
Allow signed payment_intent.succeeded events to create the invoice payment.
Open guide →How-to guidePrevent a duplicate callback payment
Understand the transaction-ID idempotency check.
Open guide →How-to guidePrevent a duplicate webhook payment
Understand the webhook idempotency check.
Open guide →How-to guideUnderstand invoice and attempt metadata
Know what the module stores on the PaymentIntent.
Open guide →How-to guideVerify the recorded Stripe transaction ID
Use the PaymentIntent ID as the unique CRM payment transaction.
Open guide →How-to guideVerify the payment-attempt reference
Confirm the CRM payment record receives the original attempt reference.
Open guide →How-to guideUnderstand callback and webhook payment labels
Recognise why labels can differ depending on which path records first.
Open guide →How-to guideHandle a CRM payment-record database failure
Recognise the callback alert when addPayment returns false.
Open guide →How-to guideReconcile an iDEAL payment with Stripe
Match amount, invoice metadata, attempt reference and PaymentIntent ID.
Open guide →How-to guideUnderstand session cleanup after callback
Know which temporary values are removed on return.
Open guide →