Symptoms

• Same order appears more than once in POS or backend reports
• Customer is charged twice for a single transaction
• Duplicate receipts are printed
• Issue often reported after slow response or retry action

Likely Causes

• Operator retrying action due to delayed response
• Network latency causing duplicate submission
• Payment or order service timeout with retry
• Terminal clock or sync anomaly

Supporting Procedures

• P-000064-01 — Identify and confirm duplicate transactions
• P-000064-02 — Check timestamps and transaction IDs
• P-000064-03 — Verify payment processor records
• P-000064-04 — Prevent further retries and stabilize system
• P-000064-05 — Duplicate transaction escalation

Notes

• Duplicate charges are customer-sensitive and require careful handling
• Never delete records without confirming true duplication