Retrieval Request

What Is a Retrieval Request?

A retrieval request (also called a "request for information" or "RFI") is a formal notice from a card-issuing bank to a merchant's acquirer asking for documentation about a specific transaction. It is not a chargeback: no funds are debited from the merchant's account, and no fees are assessed at this stage. The issuer simply wants to verify transaction details before deciding whether to escalate the dispute.

Retrieval requests sit at the beginning of the dispute resolution lifecycle. The full sequence typically runs: retrieval request, chargeback, pre-arbitration, and arbitration. By resolving questions at the retrieval stage, merchants can often prevent the dispute from advancing further.

The concept originated in a paper-based era when issuers literally needed to retrieve a physical copy of the signed sales draft. Today the process is electronic, but the name persists in industry terminology.

How It Works

The retrieval request process follows the four-party model that governs card payment disputes. Each participant has a defined role:

1. A cardholder contacts their issuing bank about an unfamiliar or questionable charge on their statement
2. The issuer generates a retrieval request with a reason code and sends it through the card network to the merchant's acquirer
3. The acquirer forwards the request to the merchant, who must gather and submit the requested documentation
4. The merchant responds with transaction records: signed receipts, authorization logs, delivery confirmation, or billing descriptor details
5. The issuer reviews the evidence and either closes the inquiry or proceeds to file a formal chargeback

Response deadlines vary by network. American Express typically allows 20 days. Mastercard historically allowed 30 calendar days from the central site processing date for its retrieval requests on debit transactions. Failing to respond within the deadline often results in an automatic escalation to a chargeback that the merchant cannot reverse.

Reason Codes

Each retrieval request includes a reason code that tells the merchant why the issuer is requesting documentation. Common categories include:

• Cardholder inquiry: the cardholder does not recognize the transaction and wants more information, such as the merchant name or purchase details
• Fraud investigation: the issuer suspects unauthorized use of the card and needs evidence of cardholder authorization
• Compliance documentation: the issuer needs records for regulatory or audit purposes, such as verifying that proper authorization was obtained
• Transaction not recognized: the cardholder acknowledges making purchases with the merchant but cannot match a specific charge to a purchase

Mastercard historically used codes such as 6323 (cardholder does not recognize the transaction), 6341 (fraud investigation), and 6342 (potential chargeback or compliance). American Express uses codes like 6014 (cardholder requests proof of authorization) and 6016 (cardholder needs documentation for personal records).

What a Proper Response Includes

A complete retrieval response typically contains some or all of the following:

• A copy of the sales receipt or invoice, ideally with the cardholder signature or CVV verification
• Proof of delivery: tracking numbers, signed delivery receipts, or shipping confirmation with timestamps
• Authorization records showing the transaction was approved, including the authorization code and acquirer reference number
• Communication logs such as order confirmation emails sent to the cardholder
• For card-not-present transactions: IP address logs, device fingerprints, or 3D Secure authentication records

Network-Specific Differences

The major card networks handle retrieval requests differently, and the landscape has shifted significantly in recent years:

Visa

Visa eliminated its traditional retrieval request process in October 2020. In its place, Visa introduced Order Insight (formerly Verifi), a platform that allows issuers to pull transaction details digitally in real time. This lets cardholders and issuers resolve questions before a dispute is ever filed. US issuers may still generate retrieval-like requests in limited categories such as healthcare, but merchants are generally not required to respond to them.

Mastercard

Mastercard largely phased out retrieval requests in October 2021. They survive primarily for Maestro debit card transactions and through Mastercard's Collaboration program, which functions similarly to Visa's Order Insight. When a retrieval request does occur, Mastercard allows 30 calendar days for the merchant to respond. Failure to respond can trigger a chargeback under reason code 4801 (requested transaction data not received).

American Express and Discover

American Express and Discover continue to use retrieval requests as a standard part of their dispute process. American Express gives merchants 20 days to respond, and Discover (which calls them "Inquiries") operates on a similar timeline. For merchants processing on these networks, retrieval requests remain a critical part of dispute management.

Use Cases

While major networks have moved toward automated dispute resolution, retrieval requests still serve important functions in the payments ecosystem:

Fraud Prevention

When an issuer detects suspicious activity on a card, retrieval requests allow them to gather evidence before deciding whether to block the card or file a chargeback. This is especially important for card-not-present transactions in e-commerce, where fraud rates are higher. Merchants who respond quickly with AVS match results, CVV verification, and 3D Secure authentication records can often resolve the inquiry without a chargeback.

Customer Service Resolution

Many retrieval requests originate from simple cardholder confusion. A customer may not recognize a charge because the billing descriptor on their statement does not match the merchant's storefront name. By providing clear transaction details at the retrieval stage, merchants can resolve the confusion before it becomes a formal dispute.

Compliance and Auditing

Issuers sometimes send retrieval requests for regulatory compliance purposes: verifying that transactions meet card network rules, checking that proper authorization was obtained for high-value transactions, or gathering documentation for anti-fraud audits.

Retrieval Requests and Crypto Payments

Cryptocurrency and stablecoin payment processors face a unique challenge when card-funded crypto purchases trigger retrieval requests. The core problem is a fundamental mismatch: card network disputes assume transactions can be reversed, but blockchain transactions are irreversible once confirmed.

When a cardholder uses a credit card to purchase cryptocurrency through a payment processor, and the issuer later sends a retrieval request or chargeback, the processor cannot "undo" the blockchain transfer. The crypto may have already been moved to another wallet, swapped for a different token, or withdrawn to a self-custodial address. This creates what industry analysts call a "reversal gap": the processor may have to refund fiat even though the corresponding crypto has been irreversibly delivered.

This mismatch is one reason why many crypto platforms classify card purchases as high-risk and apply additional fraud scoring, lower transaction limits, and extended holding periods before releasing purchased assets. It also motivates the broader shift toward native crypto payment rails and stablecoin payment infrastructure that avoids the card network dispute process entirely. For a deeper analysis of this dynamic, see the research article on the stablecoin chargeback gap.

Retrieval Request vs. Chargeback

It is important to understand the distinction between a retrieval request and a chargeback, as they are often confused:

Because retrieval requests carry no immediate financial penalty, some merchants deprioritize them. This is a mistake: an unanswered retrieval request almost always escalates to a chargeback, which does carry fees, fund debits, and ratio consequences. Treating retrieval requests as urgent is one of the most effective ways to reduce a merchant's overall chargeback ratio.

Risks and Considerations

Missed Deadlines

The most common risk is failing to respond within the network's deadline. Once the response window closes, the issuer typically escalates to a chargeback automatically. Evidence submitted after the deadline will not reverse the chargeback. Merchants should configure alerts in their payment gateway or processor dashboard to flag incoming retrieval requests immediately.

Incomplete Documentation

Submitting a response that does not fully address the reason code can be as ineffective as not responding at all. A fraud investigation code requires different evidence than a cardholder inquiry code. Merchants should maintain organized records of all transactions, including authorization logs, delivery receipts, and customer communications, so they can assemble a complete response quickly.

Evolving Network Rules

With Visa and Mastercard having phased out traditional retrieval requests, merchants need to stay current on each network's dispute process. What was a retrieval request workflow five years ago may now be handled through an automated platform like Visa's Order Insight or Mastercard's Collaboration. Merchants processing on multiple networks should work with their acquirer to understand the current requirements for each.

Volume and Monitoring

A sudden spike in retrieval requests can signal emerging fraud patterns on a merchant's account, such as a compromised card batch or a card testing attack. Merchants should track retrieval request volume as an early-warning metric alongside their chargeback ratio. Proactive transaction monitoring and fraud scoring can help identify and resolve issues before they generate retrieval requests in the first place.

This glossary entry is for informational purposes only and does not constitute financial or investment advice. Always do your own research before using any protocol or technology.