Skip to main content

Visa, Mastercard

Decline Code 59 (Visa) / 83 (Mastercard): Suspected Fraud

soft decline

Last updated: November 20, 2026

Key details

Brand
Visa, Mastercard
Code
59 / 83
Category
Issuer Response Codes
Response
59
Detailed Response
Suspected fraud
soft decline

Code by card network

NetworkCodeOfficial wording
Visa59Suspected fraud
Mastercard83Fraud/Security (Mastercard use only)
Diners59Suspected Fraud
Discover59Suspected Fraud
V Pay59Suspected fraud
Maestro83Fraud/Security (Mastercard use only)
Discover83Domain Restriction Controls FailureDifferent meaning
This transaction is retriable

Payments failing with code 59 / 83 are often recoverable with the right retry timing and routing. SmartRetry recovers up to 70% of soft declines with smart retries!

Actually, a big part of your declined transactions can be recovered

Recover your revenue >

What it means

Decline code 59 on Visa and code 83 on Mastercard indicate that the issuing bank refused the transaction due to suspected fraudulent or security-related activity on the card. Visa calls it "Suspected fraud", while Mastercard calls it "Fraud/Security (Mastercard use only)". Even if the card has not been formally reported lost or stolen, the issuer's risk systems determined that the transaction's characteristics warranted a refusal out of caution.

Why does code 59 / 83 occur?

  • A combination of risk factors—such as a high-value transaction made cross-border at an unusual hour—prompted the issuer to err on the side of caution.
  • The transaction was submitted without additional authentication, leaving the issuer unable to verify the cardholder's identity during a high-risk check.

How to solve 59 / 83?

To resolve a suspected fraud decline, do not immediately resubmit the identical authorization request, as the issuer's risk parameters will continue to refuse it until the security concern is addressed. If the customer is active at checkout, prompt them to complete a new attempt with additional authentication or ask them to confirm the activity directly with their issuing bank before trying again. Alternatively, offer the shopper a different payment method to complete the purchase.

Solving as a merchant

Inspect the raw acquirer response to identify this refusal reason and configure your retry logic to prevent automated, unauthenticated resubmissions that could trigger network system integrity fees for excessive retries. For interactive checkouts, route subsequent attempts through additional authentication flows or prompt the customer to use an alternative payment credential.

Solving as a client

Contact the issuing bank using the number on the back of the card or respond to any fraud alerts from the bank to confirm the purchase is legitimate, then attempt the transaction again or use a different payment method.

Frequently asked questions about this topic

Share this article

Share on XShare on FacebookShare on LinkedIn
Kyle Regacho

Author

Kyle Regacho
LinkedInFind me on Linkedin

Focused on payment recovery, decline codes, and authorization optimization at SmartRetry. Helps payment teams turn failed transactions into recovered revenue

Read all articles >

How providers report this

  • Adyen: 31 (Issuer Suspected Fraud)
  • PayPal: 9500 (Suspected Fraud)
View all
SmartRetry - Payment Recovery Platform

Decline codes tell you why. We fix it.

SmartRetry reads every decline reason and applies the right retry strategy for each one. Your recovery rate goes up without any changes to your payment provider.