Payment recording and reconciliation

Prevent a duplicate callback payment

Pixie CRM guidance. Follow the route for your workspace, check your role and enabled modules, and verify the result before moving on.

This guide explains the transaction-ID idempotency check.

Audience: CRM staffPermission: Finance staff / technical supportModule v1.0.0

Jump to steps

Where to goStripe return → iDEAL callback

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

Understand the transaction-ID idempotency check. These instructions follow the supplied module’s live hooks, menus, controllers, forms, model rules and downstream effects.

Follow these steps

If the customer refreshes or returns twice, verify only one payment exists.
Use the Stripe PaymentIntent ID to reconcile.

Fields and options

Duplicate keyinvoicepaymentrecords.transactionid

Category/help-centre/category/stripe-ideal-payment-gateway/

Topic/help-centre/topic/stripe-ideal-payment-recording/

Rules and limits

The callback exits to the invoice when a row already has the PaymentIntent ID.

Check it worked

Prevent a duplicate callback payment 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.

Was this guide useful?Your response is stored only in this browser.