What Does Code 25: Unable to Locate Record in File Mean?
The decline code “25: Unable to locate record in file” in a credit card transaction typically indicates that the information provided for the transaction does not match any records on file with the credit card issuer or the processing network. This could mean several things, such as the credit card number or other pertinent details entered are incorrect, or there is no existing account associated with the information provided. Essentially, the payment processor is unable to find an account or transaction record that corresponds to the details entered, leading to the transaction being declined. This code prompts the cardholder to check the card details entered and try again or contact their bank for further clarification.
Key Takeaways
- Code: 25
- Standard meaning: Unable to locate record in file
- Plain-English meaning: The system cannot find the account, card, authorization, or transaction record needed for the request
- Likely source: Issuer account record, original authorization, transaction ID, gateway reference, settlement status, tokenization data, or processor mapping
- Best first action: Confirm the transaction type and locate the card or original transaction record
- Best merchant action: Avoid blind retries and reconcile records before retrying, voiding, reversing, refunding, or fulfilling
Code 25 is the payment system saying, “I cannot find the record this request depends on.” That makes it different from a low-balance decline, a stolen-card warning, or a simple processor outage.
The practical merchant rule is: identify what kind of record is missing before taking the next step. A sale attempt needs card-data verification. A void, reversal, capture, or refund needs transaction-record reconciliation.
What Code 25 Means in Plain English
Payment systems rely on records. A card authorization needs a recognizable card or account record. A void, reversal, refund, or capture needs a matching original transaction record. If the system cannot find the required record, it may return Decline Code 25: Unable to Locate Record in File.
This code is easy to misread because different processors describe it from different angles. Some focus on the issuer not recognizing the card details. Others focus on a follow-up request that cannot match the original transaction.
Both views point to the same operating issue: the merchant should not guess. Check the card details, transaction references, authorization status, and settlement stage before retrying, refunding, voiding, or shipping.
Common Reasons Code 25 Happens
Code 25 can appear when card details, transaction records, or follow-up references do not line up.
- Issuer cannot match the submitted card details to an account record
- Card number, expiration date, or billing details were entered incorrectly
- Original authorization cannot be found for a void, reversal, capture, or refund
- Wrong transaction ID, authorization code, or gateway reference was used
- Transaction already settled and now requires a refund rather than a void
- Original transaction was already voided, reversed, refunded, or expired
- Authorization is no longer available for capture
- Stored-payment or tokenized card data is outdated or corrupted
- Gateway, POS, or processor records do not match
- Processor maps an account-record or original-transaction mismatch to Code 25
The missing record is the clue. The merchant should determine whether the issue is card data, saved payment data, transaction reference data, or settlement timing.
What the Merchant Should Do
Handle Code 25 with a record-check process before retrying or adjusting the payment.
- Confirm the transaction type. Identify whether the request was a sale, authorization, capture, void, reversal, refund, inquiry, or file update.
- For a sale attempt, verify card details. Ask the customer to check the card number, expiration date, billing ZIP, and other required fields.
- For follow-up actions, locate the original record. Check transaction ID, authorization code, gateway reference, amount, card brand, timestamp, and order ID.
- Check settlement status. If the transaction already settled, the correct action may be a refund, not a void or reversal.
- Avoid blind retries. Repeating the same bad data or wrong reference usually creates the same result.
- Escalate repeated events. Give your processor the transaction type, timestamp, amount, gateway ID, original transaction reference, card brand, BIN range, and response code.
What Not To Do
Code 25 can create accounting and fulfillment problems if staff treat it like a simple card decline.
- Do not assume the customer has insufficient funds.
- Do not ship or provide service without a clean approval and capture.
- Do not retry unchanged card details over and over.
- Do not issue both a void and refund without checking settlement status.
- Do not reverse or refund against the wrong transaction record.
- Do not ignore repeated Code 25 events after a gateway, POS, tokenization, or processor change.
The right question is not “Can we run it again?” It is “Which record could not be found, and what does the current transaction status show?”
When Merchants Should Look Deeper
One Code 25 may be a simple data mismatch. Repeated Code 25 responses point to a payment-process problem.
- Virtual terminal or manually keyed transactions
- Ecommerce checkout fields with weak card-data validation
- Void, reversal, refund, capture, or delayed-capture workflows
- Stored-payment, tokenization, or subscription billing records
- Settlement timing and batch-close procedures
- Gateway reports that do not match processor records
- Staff workflows that use the wrong transaction reference
- Partial approvals, split payments, or adjusted transactions
- Recent POS, gateway, processor, API, or shopping-cart changes
- Specific issuers, BIN ranges, card brands, or payment channels
If Code 25 clusters around one workflow, payment channel, gateway, or staff process, the issue may be record handling—not the customer’s willingness or ability to pay.
How Durango Merchant Services Can Help
Durango Merchant Services helps merchants turn vague transaction responses into clear payment decisions.
For high-risk, ecommerce, MOTO, subscription, travel, nutraceutical, large-ticket, and cross-border merchants, Code 25 can affect authorization, fulfillment, voids, captures, refunds, reconciliation, accounting, and customer service.
The fix may involve cleaner gateway reporting, better transaction-reference handling, stronger staff procedures, improved tokenization records, clearer settlement workflows, or a processor with better transaction visibility.
If Code 25 keeps showing up in your reports, contact Durango Merchant Services. We can help you review the pattern, reduce payment uncertainty, and build a cleaner processing workflow.
FAQs For Decline Code 25
It means the payment system could not locate the record needed to complete the request. Depending on the transaction type, that may be a card or account record, or it may be the original transaction record for a void, reversal, refund, capture, or inquiry.
No. Code 25 is a record-location or record-matching issue. It does not automatically mean the customer lacks funds.
Do not retry blindly. First verify the card details or original transaction reference. If the error is corrected and no valid payment exists, one clean new attempt may be appropriate.
Investigate when Code 25 repeats across one gateway, POS system, virtual terminal, stored-payment flow, void/refund process, settlement batch, card brand, or processor setup.