The short answer
A retrieval request (also called a "copy request" or "ticket retrieval") is initiated when a cardholder questions a charge and the issuing bank needs documentation — a receipt copy, order details, shipping confirmation, invoice — to answer the cardholder. The issuer sends the retrieval to the acquirer; the acquirer forwards it to the merchant. The merchant has a defined window (usually 15–28 days depending on network and dispute reason) to respond with the requested documentation. A retrieval request is a warning shot, not a financial reversal — no money moves. But if the merchant fails to respond or provides inadequate documentation, the retrieval can escalate to a formal chargeback.
Retrieval request vs. chargeback
- Retrieval request: no money moves. The issuer wants information to answer the cardholder. Merchant response deadline: 15–28 days. No fee unless you ignore it.
- Chargeback: the issuer has debited the transaction back. Merchant can represent (dispute) the chargeback but must produce compelling evidence. Fee assessed: $15–$100 per chargeback plus any network assessments if ratios are exceeded.
Roughly 30–40% of unanswered or poorly-answered retrieval requests escalate to chargebacks. Answering the retrieval correctly is the highest-leverage cardholder-dispute intervention you have.
What operators need to know
- Respond within 15 days even if 28 is the formal deadline. Issuer dispute analysts close the cardholder file as soon as your documentation arrives. Faster response = earlier closure = no escalation.
- Send what they asked for, not what you have. If the retrieval asks for "signed delivery confirmation," sending a shipment tracking URL is not the same thing. Requests vary by reason code — check the reason field and respond precisely.
- Good documentation per-transaction. Keep the full transaction trail: order confirmation email, line-item receipt, IP/device fingerprint at checkout, shipping/delivery confirmation, refund/return policy URL at time of checkout, communication log with customer. Retrieval responses draw from this trail.
- Retrieval fees are small but add up. Each retrieval is usually $2–$7 at the acquirer. If your retrieval rate exceeds your gross chargeback rate, something in customer-facing copy is confusing and driving inquiries.
- Retrieval rates are a leading indicator of chargeback pressure. Watch the ratio of retrievals to charges monthly. Rising retrievals = rising confusion = rising disputes in 30–60 days. Catch the root cause (unclear descriptor, surprise subscription auto-renew, delivery expectations mis-set) early.
Common retrieval triggers
- Descriptor confusion. Customer sees a charge they don't recognize because the billing descriptor doesn't match the brand they bought from. A clean soft descriptor fixes this at source.
- Subscription renewal surprise. Customer forgot they subscribed; sees a renewal charge; requests info before disputing.
- Duplicate-charge suspicion. Customer sees a pending + captured authorization and mistakes it for two charges.
- Shipping vs. charge timing mismatch. Card charged at order, shipped 3 weeks later, customer has forgotten the purchase by the time the shipping email arrives.
How multiflow handles retrievals
The operator portal surfaces retrieval requests across your portfolio in one queue (not per-brand, per-processor). Each retrieval has an auto-populated response packet pulling from your order system: confirmation email, line-item receipt, shipping confirmation, refund policy snapshot. You review, approve, and submit. Historical resolution-rate is tracked per sub-brand so you can see which brand's customer experience is producing the most cardholder confusion. See dispute resolution for the downstream workflow when retrievals do escalate to chargebacks.