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.
Visa
Visa Issuer Response Code 25: Unable to locate record on file
technical declinehard decline
Last updated: September 25, 2026
About 25 - "Unable to locate record on file"
Key details
- 25
- Issuer Response Codes
- 25
- Unable to locate record on file
technical declinehard decline
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.
Classification & retryability
technicalhardRetryable: conditional
Do not perform automated blind retries. You may attempt one controlled retry only after manually verifying that the PAN, token, expiration date, and any required original-transaction references are properly populated in the request payload.
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 customer
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.
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.