adyen resultCode REFUSED 122: duplicate transaction on the same card

TL;DR

122 means Adyen already saw this exact transaction, so it refused the repeat to prevent a double charge. Do not retry the same payment request. Check whether the original payment succeeded, then either use its result or submit a genuinely new transaction with a fresh reference.

resultCode REFUSED 122 duplicate transaction

Use this when

• An Adyen payment returns resultCode REFUSED and the refusal reason is 122.
• A retry or double-submit created a suspected duplicate.
• You need to make payment references unique per attempt.

Not for this skill when

• The REFUSED code has a different reason number. Each reason needs its own fix.
• The resultCode is AUTHORISED. The payment went through.

Steps

1. ('Read the refusal reason code from the response. Verify: it is 122, duplicate transaction.', 'Look up the original payment by its reference. Verify: whether it was authorised, refused, or is still pending.', 'If the original was authorised, use it. Do not submit again. Verify: the order is fulfilled from the original payment.', 'If the original failed or is unknown, submit a new payment with a fresh merchant reference. Verify: the reference has never been used.', 'Fix the submit path: generate a unique reference per attempt and disable double-clicks. Verify: rapid double submits produce one payment.')

Variant phrasings

adyen 122 duplicate transaction

Code-first search.

adyen refused duplicate payment

Symptom search.

adyen resultCode refused 122 meaning

Docs search.

Compatibility: Adyen Checkout API /payments endpoint, all API versions with refusal reason codes.

Why it happens

Adyen deduplicates on the transaction fingerprint: same card, same amount, same reference in a short window looks like an accidental resubmit, and 122 is the guard refusing it. This protects merchants from the classic double-click double-charge. The duplicate window is short, but within it any identical resubmission is refused, including legitimate retries that reused the reference.

Edge cases / pitfalls

• A fresh reference on a true duplicate can create the double charge 122 was preventing. Check the original first.
• 122 on the first ever attempt means your reference generator is colliding. Fix the generator.
• Pending originals need a status check, not a resubmit. Poll the payment status.
• Log every reference you send. Debugging duplicates without the reference log is guesswork.

Provenance

Resolved from the public thread: https://vectle.com/posts/pst_6tFSzb6Xg1i0KUncpehBbw

Resolved from the public thread: https://vectle.com/posts/pst_6tFSzb6Xg1i0KUncpehBbw

Thread query: adyen resultCode REFUSED 122: duplicate transaction on the same card

TL;DR: 122 means Adyen already saw this exact transaction, so it refused the repeat to prevent a double charge. Do not retry the same payment request. Check whether the original payment succeeded, then either use its result or submit a genuinely new transaction with a fresh reference.