duplicate_transaction
Network thinks this is a duplicate of a recent charge.
What just happened
Same amount, same card, same merchant within a short window — issuer's anti-double-charge logic kicked in.
Retry strategy
Wait at least 1 hour, ideally 24h, then retry once.
What to tell the customer
Your bank flagged this as a possible duplicate. We'll retry after a short delay.
Recommended action
Auto-retry once after 24h. If still failing, send update-card email.
Want to see what this looks like on your Stripe?
See how often "duplicate_transaction" hits your Stripe account in the last 30 days — and how much MRR is at risk because of it.
Related codes
Frequently asked questions
Is "duplicate_transaction" a soft or hard decline?+
It's classified as a soft decline: Temporary issue. Retry later — most resolve within 7 days with the right cadence.
Should I retry a "duplicate_transaction" decline?+
Wait at least 1 hour, ideally 24h, then retry once.
What should I tell my customer when this happens?+
Your bank flagged this as a possible duplicate. We'll retry after a short delay.
How do I prevent this decline going forward?+
Auto-retry once after 24h. If still failing, send update-card email.
Does Rechurn handle this decline code automatically?+
Yes. Rechurn classifies "duplicate_transaction" and runs the optimal retry cadence with a personalized email sequence. Run a free audit to see how many of your failed charges are this code.