Retrieval Request Fee

Also called ticket retrieval fee, copy request fee, transaction documentation request

A charge for responding to an issuer's request for a copy of a sales receipt - the step before a chargeback.

What it is

A retrieval request, sometimes called a copy request or ticket retrieval, is an issuing bank asking for documentation of a transaction on a cardholder's behalf. It typically precedes a chargeback: the cardholder doesn't recognize a charge, the issuer asks the acquirer for the receipt, and the acquirer asks you. Processors charge $5 to $15 per request to handle it. The deadline is short - commonly a matter of days - and missing it usually converts the retrieval into a chargeback, which costs $15 to $50 plus the disputed amount. So a retrieval request is best understood not as a fee but as an early warning with a clock on it. Retrievals have declined as a share of disputes since the networks streamlined into collaboration and pre-dispute resolution flows, and many issuers now go straight to a chargeback. But they persist, and they cluster around the same causes: an unrecognizable billing descriptor, a delayed charge, a recurring billing charge the cardholder forgot signing up for, or a large ticket the issuer wants documented. A business that receives frequent retrievals has a recognition problem, not a fraud problem. That distinction is worth making because the fixes are completely different and only one of them is free.

Why it matters to your business

The fee is small - $5 to $15 - but the escalation is not. Missing a retrieval turns a $10 charge into a $35 chargeback fee plus the lost sale plus the ratio impact that feeds network monitoring programs. For a merchant with a recurring billing book or a large-ticket business, retrievals are a leading indicator. If you're getting them regularly, you have a descriptor, receipting or communication problem that will become a chargeback problem within a quarter.

Where it gets contested

The economics are the same as chargeback fees, one step earlier: your processor earns revenue from your disputes and has no revenue interest in reducing them. But the retrieval-specific issue is notification quality. The clock is short, and a retrieval request delivered by an unread email or a portal notification the merchant never logs into becomes a chargeback by default. Merchants who get hit with a chargeback often had a retrieval they never saw. That is a fixable operational failure on the processor's side, and whether it gets fixed depends on whether anyone considers it their job. The second issue is stacking. Some processors charge for the retrieval, then charge a chargeback fee if it escalates, then charge a representment fee if you fight it. Three fees on one disputed sale, and the merchant may still lose. Ask whether the retrieval fee is credited if the retrieval resolves the matter - a reasonable ask that reasonable processors will grant.

How to check it yourself

Ask your processor exactly how retrieval requests are delivered to you - email, portal, fax, mail - and confirm the destination is an address a human reads daily. Then ask what the response deadline is and whether the fee is credited when you respond successfully. If your only notification channel is a portal you have never logged into, fix that today.

Receipts

Claims above that are checkable, with where to check them. Published so you do not have to take anyone's word for it.

Excessive chargebacks are MATCH reason code 04 with a five-year standard listing duration
paymentcloudinc.com ↗
An honest disclosure standard requires every non-interchange fee to be named, defined and quantified before signature
ftc.gov ↗