Retrieval request
DEFINITION
A retrieval request is a request from a cardholder's issuing bank asking a merchant for more information about a transaction, often before a chargeback.
TABLE OF CONTENTS
RELATED TERMS
A retrieval request is a request from a cardholder's issuing bank to a merchant for more information about a specific transaction, usually a copy of the sales record or supporting documentation. It asks for details, not for money back, and it often comes before a formal chargeback.
Retrieval requests typically arise when a cardholder does not recognize a charge, questions its details, or when the issuer needs documentation to resolve an inquiry. By responding promptly with clear evidence of a legitimate transaction, a merchant can often satisfy the issuer and head off a dispute before it becomes a chargeback. Because the request is a chance to clarify rather than an automatic loss of funds, how quickly and completely a merchant answers matters. A subscription platform such as Recurly holds the transaction and billing records a merchant would draw on to respond, while the request itself flows through the acquirer and card network.
Why a retrieval request matters for subscription businesses
A retrieval request is an early chance to prevent a chargeback. Chargebacks cost the merchant the disputed amount plus fees and can, if frequent, raise processing costs or put the account at risk. Answering a retrieval request well, with proof that the charge was valid, can resolve the cardholder's question before it escalates.
Subscription businesses see these inquiries partly because recurring charges are easy for a customer to forget. A subscriber may not recognize a renewal on their statement, especially if the billing descriptor is unclear, and reach out to their bank. A clear billing descriptor and easy access to transaction history reduce both the number of retrieval requests and the effort to answer them. Recurly merchants set the billing descriptor through descriptor settings, which control how a charge appears on the cardholder's statement.
How a retrieval request works
A retrieval request moves between the issuer, the network, the acquirer, and the merchant:
A cardholder questions a charge or does not recognize it, and contacts the issuing bank.
The issuer sends a retrieval request through the card network to the merchant's acquirer, asking for transaction details.
The merchant receives the request and gathers the supporting records, such as the transaction receipt, subscription terms, and proof of delivery or access.
The merchant responds within the required window with the requested documentation.
The issuer reviews the response and either closes the inquiry or, if it is unresolved, the case may proceed to a chargeback.
Meeting the response deadline is critical, because a missing or late response can lead directly to a chargeback. The response window is set by the card network and applies to all merchants regardless of the billing or SaaS platform used.
Benefits and examples
Handling retrieval requests well delivers clear value:
A chance to prevent chargebacks, since a strong response can resolve the issuer's inquiry before it escalates.
Lower dispute costs, because avoided chargebacks mean avoided fees and disputed amounts.
Insight into billing clarity, as a pattern of requests can reveal a confusing descriptor or renewal experience.
A healthier processing profile, since fewer chargebacks help keep the merchant account in good standing.
As an illustration, consider a hypothetical subscriber who sees a renewal charge they do not recognize and asks their bank about it. The issuer sends a retrieval request, and the merchant responds with the sign-up record, the subscription terms, and the renewal history showing the customer's consent and use. Satisfied, the issuer closes the inquiry and no chargeback follows. The subscription platform maintains the billing records that make this kind of response possible.
Frequently asked questions
What is a retrieval request? It is a request from a cardholder's issuing bank for more information about a transaction, usually a copy of the sales record. It asks for documentation rather than an immediate refund, and it often comes before a chargeback.
Is a retrieval request the same as a chargeback? No. A retrieval request asks the merchant for information about a transaction. A chargeback reverses the charge and returns funds to the cardholder. Responding well to a retrieval request can prevent a chargeback, but the two are separate steps.
How should a merchant respond to a retrieval request? Gather the supporting records, such as the transaction receipt, the subscription terms, and evidence of delivery or access, and submit them within the required window. A complete, timely response gives the issuer what it needs to resolve the inquiry.
Why do subscription businesses receive retrieval requests? Recurring charges are easy for customers to forget, so a subscriber may not recognize a renewal on their statement and ask their bank about it. A clear billing descriptor and accessible transaction history reduce both the volume of requests and the work to answer them.
