Skip to main content
SmartRetry - Payment Recovery Platform

Visa

Visa Issuer Response Code 46: Closed Account

hard decline

Last updated: October 8, 2026

Key details

Brand
Visa
Code
46
Response
46
Detailed Response
Closed account
hard decline
This transaction is not retriable

Payments failing with code 46 are hard declines and typically cannot be recovered by retrying. SmartRetry still helps you avoid future hard declines with smarter routing and validation.

But many other declines in your payment flow may still be recoverable. SmartRetry identifies which failed transactions have recovery potential and applies the right strategy to recover them.

Find out what you can recover >

What it means

Visa issuer response code 46 indicates that the account associated with the provided primary account number (PAN) or network token has been permanently closed by the cardholder or the issuing bank. It is a final status for the specific payment credential, not a temporary authorization block or a simple expiration issue.

Why does code 46 occur?

  • The cardholder voluntarily closed their credit or debit card account with the issuing bank.
  • The issuing bank permanently closed the account due to inactivity, account default, or policy violations.
  • The card network flagged the specific PAN or token as permanently invalid and mapped it to a closed account status.

How to solve 46?

Treat code 46 as a hard decline and immediately halt all automated retries for the associated PAN or network token. Visa network rules strictly require this code to indicate a permanently closed account, meaning subsequent authorization attempts using the same credentials will fail and may generate unnecessary authorization traffic. To resolve the decline, you must obtain updated payment details either directly from the cardholder or through the Visa Account Updater (VAU) service.

Solving as a merchant

Suppress any scheduled recurring billing retries for this specific payment method in your system. Check your Visa Account Updater (VAU) reports, as VAU may provide new account information, a contact-cardholder advice, or a closed-account confirmation within two business days. If an updated PAN or token is provided by VAU, apply it to your token vault before requesting a new authorization. If no automatic update is available, proactively message the customer to request a replacement payment method.

Solving as a client

Log into the merchant's portal to provide a new, active payment method to replace the closed account. If you believe the current account is still active, contact your issuing bank for clarification.

Tip from SmartRetry Configure your billing system to immediately blacklist this credential across all recurring schedules to prevent card-brand excessive retry fines, and automatically prompt the cardholder for a secondary payment method.

See the full list of Visa's decline codes >Find code on Visa's website >

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 >

Articles you may find interesting:

View all
How Payment Teams Can Prevent Gateway Holds and Manage Dispute Ratios

How Payment Teams Can Prevent Gateway Holds and Manage Dispute Ratios

Discover how automated risk reviews trigger gateway freezes and how payment teams can insulate revenue through multi-acquirer setups and smart retry logic.

Why Credit Cards Get Declined and How Payment Teams Can Fix It

Why Credit Cards Get Declined and How Payment Teams Can Fix It

Payment rejections cost merchants billions in lost sales and unforced churn. Discover the root causes behind issuer declines and how intelligent recovery strategies salvage legitimate revenue.

Why Payment Tests Pass in Staging and Fail in Production

Why Payment Tests Pass in Staging and Fail in Production

Passing a sandbox check rarely guarantees live authorization success. Learn how real-world issuer ambiguity, webhook delays, and network retry rules impact revenue pipelines.

Testing Payment Systems: Why Sandboxes Lie and How to Test in Production

Testing Payment Systems: Why Sandboxes Lie and How to Test in Production

Sandboxes verify API formatting, but live issuers determine transaction success. Discover how multi-layered testing, safe retry logic, and real-time observability safeguard authorization rates and reduce involuntary customer churn.

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.