Retrieval Requests: How to Answer Before They Become Chargebacks
A retrieval request is your cheapest chance to stop a chargeback. See which documents issuers want and how to answer before your processor's deadline.
Photo: Pixabay
On this page 6 sections
- What a Retrieval Request Is and Why Issuers Send It
- How Inquiries Differ Across Visa, Mastercard, American Express and Discover
- How an Ignored Copy Request Becomes a Chargeback
- What to Put in a Retrieval Request Response
- Retrieval Request Response Deadlines: Beat Your Processor's Date
- Turn Every Inquiry Into an Early Warning
A retrieval request is a card issuer asking you, through your processor, for the records behind one specific charge. The cardholder has questioned the transaction or doesn't recognize it, and the issuer wants your side before deciding whether to file a chargeback. No money has left your account at this stage, which makes it the cheapest point in the dispute process to end the matter. Send a complete, readable response before your deadline, and the issuer has what it needs to tell the cardholder the charge stands.
Plenty of merchants treat these notices like junk mail. That habit turns simple questions into chargebacks.
What a Retrieval Request Is and Why Issuers Send It
The issuer is the bank that gave your customer the card. When a cardholder calls about a charge, the issuer either opens a dispute right away or asks the merchant for the transaction record first. That second path is the retrieval request.
Processor portals don't all use the same name for it. Some screens say "copy request," others say "inquiry," and a few describe it as a request for information on a credit card transaction. The mechanics are the same in every case: the issuer wants paper, and you're the only one who has it.
The triggers are ordinary ones:
- The billing descriptor on the cardholder's statement doesn't match the name on your sign or website.
- Someone else in the household or business used the card without telling the cardholder.
- The final amount differs from what the customer expected, like a hotel folio with incidentals or a tip added after authorization.
- The cardholder needs an itemized receipt for an expense report or a tax file.
Nobody has accused you of fraud, and no chargeback exists yet. The request itself doesn't debit your account or count toward your chargeback ratio. Some processors do bill a fee for each retrieval request they handle. That fee is your processor's pricing, not a network rule, so look for it on your statement and fee schedule. To see where this stage sits in the full process, read our walkthrough of the chargeback lifecycle from inquiry to arbitration.
How Inquiries Differ Across Visa, Mastercard, American Express and Discover
Each network runs this stage its own way and revises its dispute rules on its own schedule. Use what follows as orientation, then confirm current procedures with your processor.
Visa's current dispute rules have moved away from the stand-alone copy request that older guides describe. On Visa cards, the first notice you get about a problem is likely to be the dispute itself. Your records need to be ready before anyone asks for them.
Mastercard still uses retrieval requests in its dispute process. The issuer sends the request to your acquirer, the bank that sponsors your merchant account, and your response travels back along the same path.
American Express calls this stage an inquiry, and a missed one carries real weight. Failing to reply can itself become the grounds for a chargeback. Where the inquiry shows up depends on how you accept Amex. Merchants with a direct Amex relationship hear from Amex. Merchants whose Amex acceptance runs through their processor find inquiries in the processor's portal.
Discover routes its inquiries through the acquirer as well. Leave one unanswered and nothing stops the issuer from moving ahead with a dispute.
For more on how the two smaller networks code their disputes, see how Amex and Discover dispute codes differ from Visa.
How an Ignored Copy Request Becomes a Chargeback
With no response, the issuer decides on the cardholder's account alone. On some networks, silence supports a chargeback outright. On the rest, the issuer has no reason to doubt the cardholder. Either way, a question one receipt would have closed becomes a dispute. The funds come out of your deposits, and you're writing a rebuttal against a deadline. Your processor's fee schedule shows what it charges on top of that for each chargeback.
Illustrative example. These assumptions are invented to show the arithmetic and don't come from any real merchant. A 20-room inn runs 1,200 card transactions a month and normally sees 9 chargebacks. During a sold-out month, three inquiries land in the processor portal and nobody opens them. Each one turns into a chargeback, so the month closes with 12 instead of 9. Sales volume didn't change, so the inn's chargeback ratio rose by a third because of three unread notices. Pulling three folios and registration cards would have taken less time than writing one rebuttal.
A strong rebuttal can win the money back. The extra count on your ratio stays. Card networks and processors watch that ratio closely, and a rising one leads to monitoring programs and reserves. The formula differs by network and program, so read how to calculate your chargeback ratio and what counts as too high before you assume you have room to spare.
What to Put in a Retrieval Request Response
A good response lets a busy analyst at the issuer match your document to the transaction at a glance. Every response should include:
- Details that identify the sale: date, amount, last four digits of the card and the authorization code.
- An itemized record of what was bought, as a legible scan or PDF. A faded thermal receipt photographed at an angle won't do.
- Your business name exactly as it appears on the cardholder's statement, plus a phone number customers can call.
- A short cover note in plain language explaining what the customer bought and how they received it.
Mask the card number to the last four digits. Never send a full card number or security code, and leave out unrelated customer records. Past that baseline, what persuades an issuer depends on how you sell.
Retail Stores: The Receipt and the Terminal Record
For a chip or tap sale, send the itemized receipt along with the terminal's transaction record showing the card was read at the counter. That record is your strongest evidence the card was present. If the sale was keyed because the chip failed, say so, and add whatever ties the sale to the customer, such as a loyalty account or a special order in their name. Issuers judge keyed sales like remote orders, as our comparison of card-present and card-not-present rules explains.
Hotels: The Folio Tells the Story
Send the final folio with the stay dates and room rate, plus every tax and incidental line. Attach the signed registration card and any policy the guest acknowledged at booking or check-in, such as deposit and cancellation terms. The classic hotel inquiry is a gap between the quoted rate and the final bill. A folio that itemizes the minibar and parking charges answers it. Our page on hotel payment processing covers the front-desk side.
E-Commerce: Prove Who Ordered and What Arrived
Start with the order confirmation showing the billing and shipping addresses. Add the address verification and card security code results from your gateway, along with the customer's IP address. Then attach carrier tracking that shows delivery to the shipping address on the order. If the customer accepted your terms at checkout, include the record of that acceptance. Orders authenticated with 3-D Secure authentication carry one more piece of evidence worth attaching.
Professional Services: Show the Agreement and the Work
Send the signed engagement letter or estimate with the invoice, then show the work happened. Time entries do that. So does a completed work order or an email thread confirming delivery. If you charged a card on file or took the payment over the phone, include the customer's written authorization for that specific charge.
If the customer is clearly right, refund the charge instead of arguing. First read whether to refund a customer who already filed a chargeback so you don't pay twice if a dispute is already open.
Retrieval Request Response Deadlines: Beat Your Processor's Date
The network gives the issuer a window to receive your response. Your processor uses part of that window to review what you send and forward it, so the deadline in your portal is shorter than the network's. Plan around the portal date, and ask your processor how much of the network window it keeps for itself.
Four habits keep you ahead of it:
- Name one owner. One person, with a named backup, checks the dispute portal on a fixed schedule and keeps email alerts turned on.
- File records so you can find them by date and amount. If finding a receipt means digging through a shoebox, busy months will cost you deadlines.
- Answer within a few business days of the notice. An early answer leaves time to fix a rejected upload or chase a missing document.
- Keep records as long as disputes can arrive. Cardholders file disputes months after the sale. Get your processor's retention guidance in writing and set your policy to match.
Turn Every Inquiry Into an Early Warning
Every inquiry points to something that confused a customer. Log each one with the date, amount, sales channel and the reason you think it came in. After a quarter, sort the log by reason. Patterns show up fast, and each one has a fix:
- Descriptor confusion. Ask your processor to update your descriptor to the name customers know, and add a phone number where the field allows it.
- Surprise amounts. Hotels can walk guests through incidentals at check-out. Service businesses can send a pre-billing notice before charging a card on file.
- Keyed and remote sales. Move phone payments to payment links or a hosted checkout with authentication, and have in-person customers tap or insert instead of keying their numbers.
- Receipt requests. If cardholders keep asking for itemized receipts, email one automatically with every sale.
These fixes overlap with our 15 chargeback prevention steps, and they cost far less than fighting disputes one at a time.
Start this week. Open your processor portal and pull every retrieval request from the last quarter, answered or not. If you can't find them, or your processor never surfaced them, add that to the questions to ask before choosing a merchant service provider. If you're comparing processors, request a free quote and a MannyPay specialist will get back to you within one business day.
This article is for general educational purposes and is not legal, tax or financial advice. Card network rules and state laws change; confirm current requirements for your business.
