Duplicate Order Diagnostics

Overview

Duplicate order diagnostics explain why PayPress may mention duplicate prevention when multiple Stripe webhook events refer to the same transaction.

Symptoms

• Diagnostics mention duplicate prevented or existing order updated.
• Earlier versions may show duplicate stripe_object_id insert messages.
• Only one order appears in PayPress.
• Receipt or invoice data still updates later.

Likely Causes

• Stripe sends multiple related events for the same payment.
• checkout.session.completed, payment_intent.succeeded, and charge.succeeded arrive close together.
• A later event enriches an order created by an earlier event.
• Stripe retries webhook delivery.

Resolution Steps

1. Confirm only one order exists for the payment.
2. Open Order Details and confirm identifiers and links are populated.
3. Review Event Timeline for duplicate-prevention or existing-order update messages.
4. Confirm receipt and invoice enrichment completed.
5. Treat recoverable duplicate prevention as normal unless data is missing.

Expected Result

PayPress should keep one order and merge newer Stripe data into it instead of creating duplicates.

Additional Notes

Duplicate prevention is a safety feature. It is different from a genuine database failure.

Related Articles

• Orders Overview
• Order Details
• Webhook Not Receiving Events