What Is a Retrieval Request and How Should Merchants Respond?

What Is a Retrieval Request?

A retrieval request is initiated by the issuing bank (the cardholder's bank) when a cardholder questions a transaction on their statement. The bank asks your acquiring bank for a copy of the original transaction documentation — this might include the sales receipt, authorization record, and any relevant transaction details.

Retrieval requests are essentially pre-chargeback inquiries. The issuing bank is gathering information before deciding whether to initiate a formal chargeback. In some cases, reviewing the transaction documentation satisfies the bank's inquiry and prevents a chargeback from being filed. In others, the documentation review is a formality before the bank proceeds with the dispute.

The card networks have different names for this process. Visa refers to them as "Transaction Enquiries." Mastercard historically used "Retrieval Requests" (though Mastercard has largely eliminated the pre-chargeback retrieval step for most dispute types under newer rules). Amex and Discover have similar inquiry processes.

Why Retrieval Requests Are Decreasing

It's worth understanding that retrieval requests have become less common over the past several years. Card networks have updated their dispute rules to move more quickly to the chargeback stage rather than the retrieval request stage. Mastercard, in particular, effectively eliminated most retrieval requests under their newer dispute rules (MC rules now move more directly to formal disputes).

For merchants processing primarily Visa and Mastercard transactions, you may receive fewer retrieval requests than in previous years. This doesn't mean you'll receive fewer disputes — it means the inquiry step has been shortened or eliminated for many dispute types, and you'll go directly to the chargeback stage.

Amex and Discover still use inquiry processes more extensively. Amex's inquiry process (sometimes called "Chargeback Inquiry" or "Inquiry Notification") functions similarly to a retrieval request — they're asking for transaction documentation before making a dispute decision.

How to Respond to a Retrieval Request

Responding to a retrieval request is straightforward but time-sensitive. You typically have 10–30 days to respond, depending on the card network and the specific request type. Missing this deadline can result in an automatic chargeback.

Provide the following documentation in response to a retrieval request: - The original transaction record (authorization code, amount, date, card type) - A copy of the sales receipt or order confirmation - Proof of delivery or service fulfillment if the request relates to a potential "item not received" dispute - Any signed agreement or authorization from the cardholder - Your merchant descriptor and contact information

Submit through your acquiring bank or processor's dispute portal. Don't send documentation directly to the issuing bank — everything goes through your processor's channels.

The goal is to provide documentation thorough enough that the issuing bank can confirm the transaction was legitimate without needing to escalate to a full chargeback. Think of it as a preview of what your representment evidence would look like.

Retrieval Requests and Chargeback Prevention

Responding effectively to retrieval requests is an underrated chargeback prevention strategy. A complete, well-organized response to a retrieval request can satisfy the bank's inquiry and prevent the transaction from ever becoming a formal chargeback.

The cardholder's inquiry may be as simple as not recognizing the merchant descriptor on their statement. If your billing descriptor clearly identifies your business and the transaction, the bank can relay this information to the cardholder and close the inquiry. A clear billing descriptor is one of the most effective passive chargeback prevention tools — it eliminates "I don't recognize this charge" inquiries before they start.

For merchants who receive frequent retrieval requests, analyze what percentage convert to chargebacks. A high conversion rate (most retrieval requests become chargebacks) may indicate that your documentation quality needs improvement, or that there's a systemic issue (unclear descriptor, delivery problems, product description issues) generating genuine buyer confusion.

Building a Retrieval Request Response System

For merchants who receive retrieval requests regularly, having a systematic response process is important. Here are the key elements:

Centralize dispute notifications. Retrieval requests go to your acquiring bank, which notifies you through your processor's dashboard or by email. Make sure these notifications go to a monitored inbox, not a spam folder. Missing a retrieval request deadline because the email went unread is a preventable loss.

Maintain accessible transaction records. When a retrieval request arrives, you need to quickly pull the original transaction documentation. If your records are scattered across multiple systems, the response process becomes slow and error-prone. Organize transaction records so you can pull documentation for any sale within minutes.

Document fulfillment for every order. Every shipment confirmation, delivery record, and service completion document should be automatically archived and linked to the transaction. This documentation is immediately available when needed for either retrieval requests or formal chargeback responses.

For high-volume merchants, ChargeMate can manage the full dispute process including retrieval request responses, ensuring timely and complete submissions at every stage.