Error codes
Hard decline
Adyen
Adyen code 59 – Suspected Fraud
The transaction is suspected of fraud. The shopper should contact their issuing bank for clarification.
What does Adyen refusal code 59 mean?
Adyen refusal code 59 Suspected Fraud is returned when the issuing bank's fraud system flags the transaction as potentially fraudulent. It maps to Stripe's fraudulent. This is a serious signal — the issuer is essentially telling the merchant to stop.
Is it a soft or hard decline?
Code 59 is a hard decline. Retries risk contributing to elevated chargeback ratios and can flag the merchant as a fraud enabler in network monitoring.
Common root causes
Issuer's fraud model triggered on transaction patterns (velocity, location, amount, MCC)
Cardholder-reported suspicious activity elsewhere
Card testing or carding attack patterns
Mismatched device, IP, or behavioral signals
Recommended recovery steps
Halt retries immediately to avoid compounding fraud signals.
Review related transactions for carding or testing patterns on your platform.
Verify customer identity carefully before collecting a new payment method — you don't want to re-enable fraud.
Strengthen fraud defenses (3DS, Radar rules, velocity limits) if 59 rates are rising.
How FlyCode handles Adyen code 59
FlyCode treats 59 as a hard decline and stops retries immediately to protect chargeback ratios. Before any outreach, FlyCode considers the risk profile; legitimate customers are contacted through cautious verification flows, while suspected fraud signals trigger review rather than recovery.
What does Adyen refusal code 59 mean?
Adyen refusal code 59 Suspected Fraud is returned when the issuing bank's fraud system flags the transaction as potentially fraudulent. It maps to Stripe's fraudulent. This is a serious signal — the issuer is essentially telling the merchant to stop.
Is it a soft or hard decline?
Code 59 is a hard decline. Retries risk contributing to elevated chargeback ratios and can flag the merchant as a fraud enabler in network monitoring.
Common root causes
Issuer's fraud model triggered on transaction patterns (velocity, location, amount, MCC)
Cardholder-reported suspicious activity elsewhere
Card testing or carding attack patterns
Mismatched device, IP, or behavioral signals
Recommended recovery steps
Halt retries immediately to avoid compounding fraud signals.
Review related transactions for carding or testing patterns on your platform.
Verify customer identity carefully before collecting a new payment method — you don't want to re-enable fraud.
Strengthen fraud defenses (3DS, Radar rules, velocity limits) if 59 rates are rising.
How FlyCode handles Adyen code 59
FlyCode treats 59 as a hard decline and stops retries immediately to protect chargeback ratios. Before any outreach, FlyCode considers the risk profile; legitimate customers are contacted through cautious verification flows, while suspected fraud signals trigger review rather than recovery.
What does Adyen refusal code 59 mean?
Adyen refusal code 59 Suspected Fraud is returned when the issuing bank's fraud system flags the transaction as potentially fraudulent. It maps to Stripe's fraudulent. This is a serious signal — the issuer is essentially telling the merchant to stop.
Is it a soft or hard decline?
Code 59 is a hard decline. Retries risk contributing to elevated chargeback ratios and can flag the merchant as a fraud enabler in network monitoring.
Common root causes
Issuer's fraud model triggered on transaction patterns (velocity, location, amount, MCC)
Cardholder-reported suspicious activity elsewhere
Card testing or carding attack patterns
Mismatched device, IP, or behavioral signals
Recommended recovery steps
Halt retries immediately to avoid compounding fraud signals.
Review related transactions for carding or testing patterns on your platform.
Verify customer identity carefully before collecting a new payment method — you don't want to re-enable fraud.
Strengthen fraud defenses (3DS, Radar rules, velocity limits) if 59 rates are rising.
How FlyCode handles Adyen code 59
FlyCode treats 59 as a hard decline and stops retries immediately to protect chargeback ratios. Before any outreach, FlyCode considers the risk profile; legitimate customers are contacted through cautious verification flows, while suspected fraud signals trigger review rather than recovery.
Understanding This Decline Code
Extended content body
Frequently Asked Questions
Is Adyen code 59 a soft or hard decline?
Does Adyen 59 affect chargeback rates?
Yes — repeated retries on 59 can increase the merchant's chargeback ratio and trigger network monitoring programs like Visa VAMP or Mastercard ECM. Halt retries and investigate the underlying pattern.
How does FlyCode handle Adyen code 59?
FlyCode classifies 59 as a hard decline, halts retries, protects chargeback ratios, and uses cautious customer verification before collecting a new payment method — avoiding fraud re-exposure.
