Skip to main content
SmartRetry - Payment Recovery Platform

Visa

Visa Issuer Response Code 25: Unable to locate record on file

hard decline

Last updated: October 8, 2026

Key details

Brand
Visa
Code
25
Response
25
Detailed Response
Unable to locate record on file
hard decline
This transaction is not retriable

Payments failing with code 25 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 25 indicates that the issuing bank or payment processing system was unable to locate the relevant transaction or account record in its file. It frequently functions as a system or data error indicating that the account number was missing from the inquiry, or that a linked transaction reference was malformed. It is distinct from an invalid account number decline and should primarily be treated as a data formatting or record-location problem.

Why does code 25 occur?

  • The transaction request omitted the account number or other mandatory account data.
  • An inquiry, reversal, or subsequent message referenced an original transaction ID that could not be found.
  • The submitted credit card details or network token were not recognized by the issuer's system.
  • A system error occurred at the processor or network level preventing the location of the account record.

How to solve 25?

First, inspect your gateway and acquirer logs to verify that the request payload was constructed properly, ensuring that the primary account number (PAN), token, or account details were not missing. For reversals or inquiries, confirm that the retrieval reference number or original transaction ID correctly links to an existing transaction. If all data fields are populated correctly and the issue persists, route the technical details to your acquirer for investigation, as this may be a system-level routing or mapping error.

Solving as a merchant

Validate the request payload for missing account data and verify any transaction references linked to previous authorizations. Limit retries to a single attempt after validating the payment method mapping and account data, and offer the customer an alternative payment method if the single retry fails. Do not set up infinite automated retries, which could risk duplicate processing and poor customer experience.

Solving as a client

Check the credit card information entered for any typos or missing details. If the card details are correct but the payment still fails, try using an alternative payment method or contact the issuing bank to ensure the account is active.

Tip from SmartRetry Avoid immediate, automated retries with identical payloads, as unverified reference IDs will trigger recurring declines; instead, gate retries behind automated payload validation or test routing through a secondary acquirer connection if fields appear correct.

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.