Retrieval Request
Cardholder or issuing bank request for transaction details. Often precedes chargeback. Responding within 48 hours can prevent 30-40% of chargebacks.
Overview
What is Retrieval Request?
A retrieval request — also called an inquiry — is a cardholder or issuing bank asking for transaction details before a formal chargeback is filed, usually because the customer doesn't recognize a charge. The bank sends the request to the acquirer, who forwards it to the merchant, and the merchant typically has 24-72 hours to respond.
A useful response includes the transaction receipt, a plain explanation of what the billing descriptor means, proof of delivery, and any prior customer communication, submitted through the PSP's retrieval portal. If the bank forwards a satisfactory explanation and the cardholder accepts it, the matter closes there; if not, it proceeds to a formal chargeback.
Responding promptly resolves 30-40% of retrievals without them ever becoming a chargeback — a meaningful save, since a chargeback carries its own fee and counts against the merchant's chargeback rate while a resolved retrieval costs only the time to respond. Most retrievals trace back to a handful of recurring causes: unrecognized descriptors, forgotten purchases, a family member using the card, or a subscription renewal the customer didn't expect.
Merchants who template their responses and automate the data pull — integrating the PSP with shipping or CRM systems — cut response time from days to hours and resolve a meaningfully higher share of retrievals as a result. Merchants who ignore retrievals or answer past the deadline see nearly every one convert straight into a chargeback instead, and tracking retrieval reasons over time pays off directly: if a large share trace back to descriptor confusion, fixing the descriptor prevents the next batch of retrievals from arriving at all.
In depth
Everything you need to know.
Customer calls issuing bank: "I don't recognize charge from ACME*SHOP." Bank sends retrieval request to acquirer requesting transaction details. Acquirer forwards to merchant (usually automated email). Merchant has 24-72 hours to respond with: transaction receipt, customer details, descriptor explanation ("ACME*SHOP is your subscription to ACME Shop"), delivery tracking, product/service description. Merchant submits via PSP portal. Bank reviews, forwards explanation to customer. Customer satisfied: accepts charge, no chargeback. Customer unsatisfied: proceeds to chargeback filing.
Retrievals are chargeback prevention opportunities. 30-40% of retrievals resolve without chargebacks if merchant responds promptly with clear information. For merchant with $5M annual, 2% retrieval rate, that's $100K in retrievals annually. Resolving 35% prevents $35K in chargebacks, saving $525-3,500 in chargeback fees plus preserving chargeback rate (0.7% lower). Additionally, retrieval responses educate customers - reducing future disputes. Most retrievals stem from: unrecognized descriptors, forgotten purchases, spouse/family member purchases, subscription renewals.
Illustrative example — not a specific client engagement.
- Subscription service descriptor 'TXN*4829'. 40% of retrievals from descriptor confusion. Changed to 'ACMESERVICE'. Retrievals dropped 55%, chargebacks down 0.3% (from 1.2% to 0.9%). Saved $45K annually.
- Merchant ignored retrievals (auto-deleted emails). 100 monthly retrievals became 100 chargebacks. $2,500 monthly in chargeback fees. Implemented 24-hour response policy. 38% retrievals resolved without chargeback. Saved $950 monthly in fees, 0.4% chargeback rate reduction.
- High-volume merchant automated retrieval responses. Integrated PSP + shipping API. Auto-compiled: receipt, tracking, delivery confirmation, customer email. Response time 2 hours vs 48 manual. Resolution rate improved from 32% to 41%.
- Respond to 100% of retrievals within 24 hours - maximize chargeback prevention
- Create retrieval response templates: standard information blocks for fast accurate responses
- Include in every response: clear descriptor explanation, transaction date, amount, product/service, delivery proof
- For subscriptions: emphasize renewal notification emails, trial terms acceptance, easy cancellation availability
- Track retrieval reasons: if 50%+ are descriptor confusion, change descriptor to be more recognizable
- Automate retrieval responses where possible - integrate PSP, CRM, shipping to auto-compile data
- Analyze retrieval-to-chargeback conversion rate - if >70% escalate despite responses, investigate root cause
- Ignoring retrievals - treating as unimportant, missing 30-40% chargeback prevention opportunity
- Responding after deadline - late responses auto-escalate to chargeback
- Providing vague responses - 'Customer purchased product' insufficient, need specific details
- Not explaining descriptor clearly - customer confused by 'XYZ*123' needs 'XYZ*123 is your subscription to ABC Service'
- Treating retrievals as chargebacks - different process, different response requirements
- Not tracking retrieval patterns - missing that 60% retrievals are descriptor confusion, fixable upstream
Keep exploring
Related terms
Put this to work
for your business.
MIDs structures high-risk acquiring across 30+ banks — smart routing, fraud and chargeback control built in. Tell us your category and volume and we'll build the setup around it.