Visa Payment Decline Code

Visa Decline Code 63: Security Violation

Category Fraud or SecurityRetry Guidance Hard Decline (Editorial Classification)By Payment Defender Editorial TeamUpdated July 17, 2026Last reviewed July 17, 2026

What Visa Decline Code 63 Means

Visa response code 63 indicates a security violation. The issuer declined the transaction due to a security condition.

Where the Response May Come From

This Visa response comes from the issuing bank's authorization systems, and reflects a failed security check on the transaction.

Common Reasons for This Response

Common causes include failed security checks, a mismatch in security-related data, or an account flagged for a security concern.

Should the Merchant Retry the Payment?

Treat this as a hard decline: a failed security check on the transaction generally must change at the issuer or cardholder level first, so resubmitting the same card is unlikely to succeed and may be discouraged.

Recommended Merchant Action

Because this decline reflects a failed security check on the transaction, avoid repeated retries, ask the customer to contact their bank, and review the order for genuine fraud indicators.

What to Tell the Customer

Ask the customer to contact their issuing bank to proceed.

How to Reduce Similar Payment Failures

Tracking how often a failed security check on the transaction appears by issuer and BIN can help you add authentication such as 3-D Secure and reduce false declines.

Important Limitations

Decline-code meanings vary by processor, gateway, and payment environment, and issuers may not disclose the precise reason behind this response. The retry classification on this page is Payment Defender editorial guidance, not an official network rule. Merchants should confirm handling with their processor or gateway.

Related Decline Codes

Sources and Review Information

Last reviewed July 17, 2026

Raw network-response codes are supplemental to the complete processor or gateway response. Meanings and recommended actions can vary by issuer, processor, gateway, card network, payment method, region, and merchant configuration.

Turn the Code Into Action

Know What to Do Next

Payment Defender helps merchants connect reason codes to transaction history, dispute alerts, refunds, evidence, fraud activity, VAMP exposure, and payment-performance decisions.