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.
Visa
Visa Issuer Response Code 46: Closed Account
hard decline
Last updated: September 25, 2026
About 46 - "Closed account"
Key details
- 46
- Issuer Response Codes
- 46
- Closed account
hard decline
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.
Classification & retryability
hardRetryable: no
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 customer
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.
Frequently asked questions about this topic
Share this article
Author
Kyle Regacho
Find me on LinkedinFocused on payment recovery, decline codes, and authorization optimization at SmartRetry. Helps payment teams turn failed transactions into recovered revenue
Read all articles >Related codes
Articles you may find interesting:
View all
Turning Payment Declines into Revenue with Context-Aware Retry Logic
Blind retries waste fees and damage issuer trust. By analyzing decline codes and timing reattempts around payroll cycles, payment teams can successfully salvage recurring revenue without customer disruption.
Why Payments Fail: Decoding Decline Codes and Modernizing Retry Logic
Surface-level decline messages conceal critical issuer signals. Discover how intelligent retries, network tokens, and behavioral timing protect MID health and systematically recover lost recurring revenue.
Decoding Payment Declines: Turning Authorization Failures into Recovered Revenue
Blindly retrying failed transactions hurts authorization rates and risks network fines. Discover how decoding issuer responses turns card declines into recovered revenue.
The Real Cost of Payment Declines and How to Recover Lost Revenue
Payment failures cost merchants billions in uncaptured revenue and customer churn. Discover how data-driven retries and response code intelligence help teams recover failed transactions and protect conversion.