Does suspected fraud code 59 mean my customer is a fraudster?

Usually not. It means the issuer's model found the transaction unusual for that cardholder. False positives are extremely common, and a quick confirmation between the customer and their bank typically clears the next attempt.

How do I reduce code 59 declines on my store?

Send richer data with every authorization: full AVS, CVV, and 3D Secure where supported. Authenticated, well-documented transactions give issuer fraud models reasons to approve, and for high-risk merchants, routing through better-trusted acquiring BINs also measurably helps.

Decline code · Soft decline

Decline code 59: Suspected Fraud

The issuer's fraud systems scored this transaction as likely fraudulent and blocked it. Nothing is definitively wrong with the account, and the card is not in a fraud status like 07 or 43; the issuer just does not believe this particular transaction is the cardholder. Legitimate customers trip this constantly.

Should you retry?

Retry after the cardholder confirms with their bank or through a 3DS-authenticated flow, where success rates are strong. Cold retries without new evidence tend to fail and accumulate against Visa's 15-in-30-days reattempt ceiling, so make each attempt carry something new.

Why code 59 happens

The transaction deviates from the cardholder's pattern in amount, merchant type, geography, or time of day.
Your merchant category or acquiring region carries elevated fraud rates, which raises the model's baseline suspicion for everything you submit.
The card recently appeared in a breach dataset and the issuer is scoring it defensively while deciding whether to reissue.
Missing authentication signals, such as no 3DS on a large first-time purchase from a new device or IP, left the model without exculpatory evidence.
Velocity across merchants, like several online purchases within minutes, made this attempt look like a stolen-card spree.

What to do about it

Ask the customer to approve the transaction with their bank; issuers increasingly push real-time verification texts, and a confirmed cardholder converts on the next attempt.
Route the retry through 3D Secure where available, since authenticated transactions give the issuer's model the evidence it needs and shift fraud liability.
Send complete AVS and CVV data on every attempt, because thin authorization data reads as risk.
Retry once after cardholder confirmation rather than repeatedly, as unconfirmed reattempts reinforce the fraud signature.
Review your own fraud screening on the order too; sometimes the issuer is right.

Frequently asked questions

Does suspected fraud code 59 mean my customer is a fraudster?: Usually not. It means the issuer's model found the transaction unusual for that cardholder. False positives are extremely common, and a quick confirmation between the customer and their bank typically clears the next attempt.
How do I reduce code 59 declines on my store?: Send richer data with every authorization: full AVS, CVV, and 3D Secure where supported. Authenticated, well-documented transactions give issuer fraud models reasons to approve, and for high-risk merchants, routing through better-trusted acquiring BINs also measurably helps.

Related decline codes