Retrieval Request

A retrieval request is a card issuer asking a business to produce the paperwork behind a payment. The cardholder has queried a charge. The issuer wants to see what was sold, when and to whom, and the request passes down through the acquirer to the business that took the money. No money moves at first. Nothing has been disputed yet, and nothing has been decided. It is a question, and the answer decides whether the matter stops there or turns into something that costs money.

The older names for it give the game away: a copy request, or a ticket retrieval, from the days when the answer was a paper slip pulled from a drawer. The duty behind it still sits in the card scheme rules. The Visa Core Rules and Visa Product and Service Rules set out what a transaction receipt has to contain and who has to be able to produce it. Scheme rules are revised, so the version in force is the one that governs.

Why An Issuer Asks

Most requests start with a cardholder who does not recognise a line on a statement. Sometimes the charge really is wrong. More often the trading name on the statement looks nothing like the shop they bought from, or a subscription has renewed and nobody remembers signing up. The issuer asks before it decides. That makes a retrieval request a cheap point in the dispute chain at which to sort the matter out.

What You Are Expected To Send

The request names what it wants, and the list is duller than people expect. A copy of the receipt or the order note. Proof the goods went out or the service was used. The date, the amount and the wording as the cardholder would know it. Any record that the cardholder was there, such as a signature, an address check or the result of a login step. Sending the right documents in the right format matters as much as having them. A scan that cannot be read, or a file the scheme will not accept, counts as nothing sent.

The Clock Is The Hard Part

Most schemes set a deadline, and missing it is generally treated as no answer at all. Those windows are measured in days, not weeks. They are revised from time to time, so the current figures are worth getting from the acquirer and not from an old note in a folder. A business that sends these to an inbox nobody owns will learn the deadline only after it has gone. The fix is dull and it works: one named owner, one queue, and a date on every item in it.

Where It Sits In The Dispute Chain

A retrieval request is the step before a formal dispute, not a dispute in itself. Answer it well and the issuer closes the query. Answer it late or badly and the case can move on to a chargeback, which carries a fee, a reversal of the funds and a mark against the account. The Mastercard chargeback guide for merchants sets out how the later stages run once a case has moved on.

The Descriptor Does Most Of The Work

A large share of these requests exist because nobody can place the billing descriptor. A legal entity name nobody has heard of, a payment processor's name in place of the shop's, or a code with no words in it will all produce queries from customers who did nothing wrong. Fixing the descriptor is usually a settings change with the acquirer. It removes requests instead of answering them faster.

Finding The Payment Again

The request arrives with a scheme reference, an amount and a date, which is not much to search on. So every payment wants a stable transaction ID and a payment reference held against the order. One lookup should then bring back the order, the delivery record and the customer. Where a business runs several providers, a merchant dashboard that spans them saves opening four systems to answer one question.

A Rising Rate Is A Symptom

Retrieval requests are worth counting on their own, because the number moves before the dispute number does. A jump usually points at one of three things: a change to the descriptor, a new product or market where the billing is unclear, or latent fraud working its way through. Watching the rate next to the chargeback ratio gives an earlier warning than watching disputes alone. This piece on chargeback management in regulated markets covers what happens when the numbers get away from a business.

Answering One Properly

Send requests to a named owner with a deadline they can see. Keep receipts, proof of delivery and the checks you ran together against the order, not in three systems. Answer in the shape the scheme asks for, since a good answer in the wrong shape still fails. Reply early rather than on the last day. Log the cause behind every request, since the pattern tells you more than any single case. And treat a run of them as a descriptor problem until proved otherwise. Chargeback management is designed to help with the stages that follow. This guide on cutting chargebacks without hurting the customer journey covers the prevention side.

‍