duplicate_transactionDo not retryStripe decline code: Duplicate transaction
An identical charge was just submitted.
Recovery outlook
Do not retry. A hard or fraud-flagged decline. Retrying wastes attempts and can raise your fraud signals. Flag it and move to a new payment method.
What it means
A transaction with the same amount and details was submitted very recently, so the issuer treated this one as a duplicate.
Why it happens
Usually a double-submit. A retried request, a client-side double click, or overlapping charge attempts.
Can you retry it?
Don't retry blindly; you may double-charge. Confirm whether the first charge actually succeeded, and use idempotency keys so a retry can't create a duplicate.
Recovery playbook
- 1Check whether the original charge succeeded before retrying.
- 2Use idempotency keys on charge requests.
- 3De-duplicate client-side submits (disable the button on submit).
- 4Only retry once you've confirmed no charge went through.
How Reecova handles duplicate_transaction
Reecova marks duplicate_transaction as a hard decline, stops retries so you don't stack fraud signals, and surfaces it for a clean payment-method switch or write-off. It runs across your whole Stripe account automatically, and shows the dollars each code is costing you.