Retrieval Request

Retrieval requests occur when cardholders contact their issuing banks with questions about charges appearing on their statements. Before filing a formal chargeback, issuers may initiate retrieval requests to gather transaction details and determine whether the charge is legitimate. The issuer sends the retrieval request through the card network to the merchant's acquiring bank, which notifies the merchant and requests supporting documentation such as signed receipts or order confirmations, proof of delivery with tracking information, correspondence with the customer, terms and conditions the customer agreed to, or other evidence supporting the validity of the transaction.

Merchants typically have 5 to 10 days to respond to retrieval requests, with timeframes varying by card network and specific reason codes. Timely, complete responses are critical—if merchants fail to respond or provide inadequate documentation, the issuer will likely proceed with a chargeback in favor of the cardholder. Even when merchants respond adequately, the issuer may still initiate a chargeback if the cardholder's dispute involves issues beyond simple transaction verification, such as product quality disputes or services not rendered.

Retrieval requests don't incur direct fees in most cases, unlike chargebacks which carry $15 to $100 per-incident costs. However, they require staff time to locate and submit documentation, and failure to respond converts them into chargebacks that do incur fees and count toward chargeback ratios. Best practices for managing retrieval requests include maintaining organized transaction records that are easily retrievable, responding promptly with complete documentation, including clear explanations in response letters, tracking retrieval request patterns to identify potential problems with descriptors or customer service, and using retrieval requests as early warnings to implement preventive measures before issues escalate to chargebacks.