A retrieval request is one of the earliest warning signals in the payment dispute lifecycle. When a cardholder contacts their bank about a transaction they don't recognize or question, the bank may issue a retrieval request to the merchant before opening a formal dispute. Think of it as a paper trail check — the network wants to see whether the merchant can prove the sale happened exactly as claimed.
Understanding retrieval requests is essential for any merchant who wants to manage their chargeback rate proactively. Getting ahead of this process can be the difference between resolving an inquiry quietly and absorbing a costly chargeback with associated fees and ratio penalties.
How Retrieval Request Works
The retrieval request process follows a defined sequence across card networks. Each step is time-sensitive, and delays at any point increase the risk of escalation.
Cardholder Raises an Inquiry
The cardholder contacts their issuing bank to question a charge — often because the billing descriptor is unfamiliar, the amount looks wrong, or they don't remember the purchase. This inquiry prompts the bank to investigate before filing a formal dispute.
Issuing Bank Sends a Retrieval Request
The issuing bank submits a retrieval request through the card network (Visa, Mastercard, Amex, or Discover) to the merchant's acquiring bank. The request specifies the transaction date, amount, and card details along with a deadline for response.
Acquirer Notifies the Merchant
The acquiring bank forwards the retrieval request to the merchant, typically via their payment gateway or merchant portal. Some processors send email alerts; others require merchants to log in and check a queue. Response windows are usually 20–30 days.
Merchant Compiles Documentation
The merchant gathers all relevant transaction evidence: receipts, order confirmations, shipping or delivery records, authorization logs, IP data, and any signed cardholder agreements. The documentation must be specific to that transaction reference number.
Response Is Submitted Through the Acquirer
The merchant submits the documentation through their acquirer or directly in the network's dispute portal (e.g., Visa Resolve Online or Mastercard Connect). The acquirer forwards it to the issuing bank for review.
Issuing Bank Reviews and Decides
If the documentation is satisfactory, the inquiry is closed in the merchant's favor and no chargeback is filed. If the evidence is insufficient or no response is received, the issuing bank escalates the case to a formal chargeback.
Why Retrieval Request Matters
Retrieval requests sit at a critical inflection point in the dispute lifecycle. Handled well, they cost little. Ignored, they convert into chargebacks that carry fees, network penalties, and ratio damage.
Industry data from Chargebacks911 indicates that merchants who respond to retrieval requests within the deadline prevent chargebacks in roughly 40% of cases — a significant saving given that the average chargeback costs merchants $3.75 for every $1 of the original transaction value when fees, operational overhead, and lost merchandise are included (Midigator, 2023). For high-volume merchants processing tens of thousands of transactions monthly, that ratio math compounds quickly.
Card network threshold rules add urgency. Visa and Mastercard both flag merchants whose chargeback-to-transaction ratio exceeds 1% in any rolling month. Since unanswered retrieval requests reliably convert to chargebacks, a backlog of even 20–30 ignored requests can push a mid-volume merchant into a monitoring program. The MATCH list — the industry blacklist maintained by Mastercard — is a real downstream risk for merchants who let dispute management slide.
Visa vs. Mastercard Workflow
Visa substantially removed the retrieval request step from its dispute process in 2018 with the introduction of Visa Claims Resolution (VCR). Most Visa disputes now go straight to a chargeback. Mastercard still uses pre-dispute retrieval requests in many cases. If you process both networks, your workflows need to account for both paths.
Retrieval Request vs. Chargeback
Merchants often conflate retrieval requests and chargebacks, but they are structurally different with different consequences.
| Dimension | Retrieval Request | Chargeback |
|---|---|---|
| Stage in process | Pre-dispute inquiry | Formal dispute filing |
| Initiated by | Issuing bank on cardholder's behalf | Issuing bank after inquiry or directly |
| Counts toward chargeback ratio | No | Yes |
| Financial liability | No funds moved yet | Funds reversed immediately |
| Response window | 20–30 days (network-dependent) | 20–45 days for rebuttal |
| Escalation risk | Converts to chargeback if unanswered | Moves to chargeback representment if contested |
| Cost if ignored | Chargeback + fees | Chargeback stands, merchant loses |
The key practical difference: at the retrieval request stage, no money has moved. Responding effectively means you can resolve the dispute before it ever touches your chargeback ratio or your settlement balance.
Types of Retrieval Request
Retrieval requests are not one-size-fits-all. Networks issue different request types depending on the nature of the cardholder inquiry.
Copy Requests are the most common form. The issuing bank simply wants a legible copy of the transaction receipt or order confirmation to show the cardholder. These are the easiest to fulfill with basic transaction records.
Fulfillment Requests arise when a cardholder claims they did not receive goods or services. The merchant must provide shipping confirmation, delivery tracking, or proof of digital delivery such as download logs or activation records.
Authorization Disputes occur when the cardholder claims they never authorized the charge. Merchants should respond with authorization codes, device fingerprint data, signed agreements, and IP address logs.
Recurring Billing Inquiries are triggered when cardholders question a subscription or recurring charge — often because they forgot they signed up or dispute a price change. The response should include the original enrollment record, terms acceptance, and notification history.
Best Practices
For Merchants
Keep transaction documentation organized and retrievable for at minimum 18 months. Most card networks can issue retrieval requests within 120 days of the transaction, but some dispute windows extend longer. Use a consistent filing system keyed to transaction reference numbers so you can pull records in minutes, not hours.
Review your billing descriptors regularly. A large share of retrieval requests are triggered simply because the cardholder doesn't recognize the merchant name on their statement. A clear, brand-matched descriptor that includes a customer service phone number or website is one of the cheapest chargeback-prevention investments available.
Set up real-time alerts for retrieval requests in your acquirer portal. Deadline management is everything — a missed response is a guaranteed chargeback. Assign a designated person or team to own the retrieval request queue and define an internal SLA of 48–72 hours to begin compiling a response.
For Developers
Build retrieval request handling into your dispute management integration from day one. Acquirer and gateway APIs (Stripe, Adyen, Braintree, and others) surface retrieval requests as webhook events — listen for them, map them to order records in your database, and trigger automated evidence assembly pipelines where possible.
Log rich transaction metadata at the time of sale: IP address, device fingerprint, user agent, geolocation, card present/not-present flag, 3DS authentication result, and any AVS/CVV match codes. This data is trivially cheap to store and disproportionately valuable when you need to prove authorization. Integrate it with your dispute response tooling so it surfaces automatically when a retrieval request arrives.
Common Mistakes
Ignoring low-value retrieval requests. Merchants sometimes make a cost-benefit judgment and decide small transactions aren't worth the effort to defend. This is a false economy — even a $12 chargeback counts against your ratio, and patterns of non-response signal to acquirers that your dispute management is weak.
Submitting generic documentation. Sending a template response that isn't tied to the specific transaction reference number frustrates issuers and rarely resolves the inquiry. Every response must be precisely matched to the retrieval request's transaction ID, date, and amount.
Missing the deadline. The most common and most avoidable mistake. Processors don't always send aggressive reminders. Build calendar-based escalation into your internal workflow so that a retrieval request approaching its deadline triggers an immediate priority alert.
Providing illegible or incomplete copies. A scanned receipt that's blurry, cropped incorrectly, or missing the cardholder's signature is functionally the same as no response. Invest in document quality before submission.
Failing to address the cardholder's specific concern. If the inquiry is about non-receipt of goods, sending only the authorization receipt misses the point. Match your evidence to the reason code — delivery disputes need delivery proof; authorization disputes need auth logs.
Retrieval Request and Tagada
Tagada's payment orchestration layer gives merchants unified visibility across all their payment processors and acquirers in a single dashboard. Because retrieval requests arrive through different acquirer portals with inconsistent formatting and deadlines, merchants running multi-acquirer setups often miss them entirely — especially when transaction volume is high.
When routing payments through Tagada, dispute and retrieval request events from connected acquirers can be normalized into a single event stream. This means your dispute management team works from one queue rather than checking five separate portals, and automated evidence assembly can be triggered from your existing order management data without manual copy-paste.
For developers integrating with Tagada's orchestration API, mapping retrieval request webhook events to internal order records early in the integration reduces response times dramatically — often from days to hours — which is the primary driver of pre-chargeback resolution rates.