Skip to main content
SmartRetry - Payment Recovery Platform

Visa

Visa Issuer Response Code 28: File Update File Locked Out

soft decline

Last updated: October 8, 2026

Key details

Brand
Visa
Code
28
Response
28
Detailed Response
File update file locked out
soft decline
This transaction is retriable

Payments failing with code 28 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

Visa response code 28 indicates that an issuer or network file required to process an update or inquiry is temporarily unavailable or locked out. This is a transient technical system error on the issuing bank or network side, rather than a reflection of the cardholder's account standing. It specifies that the endpoint or file could not be accessed at the exact moment of processing.

Why does code 28 occur?

  • The issuing bank or network is undergoing temporary system maintenance affecting file access.
  • A transient technical glitch caused the required file for the update or inquiry to be locked at the moment of processing.
  • An internal synchronization issue at the issuer is temporarily blocking data inquiries or updates.

How to solve 28?

Treat the decline as a temporary system or network error. Wait for a short period to allow the issuer's file lock to clear, then resubmit the transaction using a delayed backoff schedule. If subsequent attempts return the same code, escalate the issue to your payment processor or acquirer with the transaction identifiers and timestamps.

Solving as a merchant

Pause immediate retries and utilize a delayed retry approach. Do not advise the customer that their card is invalid or prompt them for a replacement card solely based on this code. Instead, monitor your transaction logs, and if the code recurs persistently, contact your acquirer to investigate the endpoint lock or unavailability.

Solving as a client

Since this is a backend technical issue at the issuer or network level, the customer does not need to take immediate action regarding their card. If the merchant cannot resolve the error after delayed retries, the customer may be asked to provide an alternate payment method to complete the checkout.

Tip from SmartRetry Avoid rapid automated retries, as hammering the issuer during a file lock can prolong the concurrency block. Instead, schedule a multi-hour backoff or temporarily pause batch processing for that specific BIN to give the issuer's database sync time to clear.

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.