National merchant dispute guidance
What Is a Retrieval Request?
A retrieval request is a request for transaction information that may occur before a formal chargeback. It is also called an inquiry or request for information in some provider workflows. The issuer is generally asking for records that clarify a cardholder's question about a purchase.
The short answer
An inquiry is not automatically a chargeback
A traditional retrieval request usually seeks a copy of a receipt or other transaction details without immediately reversing the sale. A chargeback is a formal dispute that can move funds under network and provider rules. An unanswered or insufficient inquiry may escalate, but the exact result depends on the network, reason, provider, and case.
Why it arrives
What the issuer may be trying to confirm
Purchase recognition
The cardholder may not recognize the statement descriptor, transaction date, amount, or business name and wants more context before deciding whether to dispute the charge.
Receipt or order details
The issuer may seek a receipt, invoice, order description, or other record that connects the payment to the goods or services purchased.
Delivery or service information
A request may ask when and how an order was delivered or a service was provided. The relevant record depends on the question presented in the case.
Credit or cancellation status
The case may concern a promised refund, canceled order, recurring payment, or another customer-service event that needs a clear timeline.
Practical workflow
How to respond to a retrieval request
Confirm the request is genuine
Open the case through the known processor, acquirer, or payment-provider portal. Do not send transaction records to an unfamiliar email address or enter credentials through an unexpected link.
Record the deadline and instructions
Capture the displayed due date, time zone, accepted file types, size limits, and submission channel. Set an earlier internal deadline for review.
Match the exact transaction
Verify the transaction identifier, date, amount, currency, payment channel, order number, customer record, and any refunds before collecting evidence.
Answer the question directly
Provide relevant, legible records in a simple sequence. Explain how each item identifies the purchase or resolves the inquiry instead of submitting a large bundle of unrelated material.
Save proof of submission
Keep the case number, submitted files, timestamp, confirmation, and status. Continue monitoring the approved portal because an inquiry may close, require more information, or progress to another stage.
Evidence checklist
Useful records depend on the request
Transaction record
Receipt, invoice, order number, item or service description, amount, currency, and transaction date can help identify the purchase.
Customer authorization context
Relevant records can include the accepted order details, recurring-payment consent, or authentication results available through the provider.
Fulfillment record
Delivery confirmation, pickup record, appointment history, or service-completion documentation may answer a fulfillment question.
Communication and credits
Customer messages, cancellation history, and refund confirmation can establish a clear timeline when the inquiry concerns service or a credit.
Network differences
The term is historical in some workflows
Visa announced that its traditional retrieval-request process would end in October 2020, while preserving a specific healthcare receipt-request process. Current Stripe guidance says American Express and Discover are the networks that most often use an inquiry phase and notes that Visa and Mastercard no longer use that phase in its standard workflow. These points should not be generalized to every provider, region, or transaction. The live case notice remains the operational source.
Operational readiness
Make information requests easier to handle
Use recognizable descriptors
Keep the approved statement descriptor and customer-facing business identity consistent so cardholders can connect a charge to the purchase.
Connect payment and order data
Use stable identifiers across payment, order, fulfillment, support, and refund systems so staff can retrieve a complete timeline.
Assign case ownership
Document who monitors notices, gathers records, approves responses, submits files, and reconciles the final status.
Keep records readable
Preserve transaction records in formats that remain legible and can be exported without exposing unnecessary sensitive information.
Common questions
Retrieval request FAQ
Does a retrieval request remove funds?
A traditional information inquiry generally does not reverse the payment by itself, but provider handling varies. Check the live case and account activity rather than assuming.
Can a retrieval request become a chargeback?
Some unresolved inquiries may escalate to a formal dispute. The route depends on the network, provider, case type, and response.
Should a merchant send every available document?
No. Submit a concise, readable response that answers the stated question and follows the provider's instructions.
Where should a merchant respond?
Use the approved portal or submission channel named by the processor, acquirer, or payment provider for that merchant account.
Last editorial review: August 11, 2026. Sources reviewed: current Stripe dispute workflow and evidence guidance plus Visa's official retrieval-request sunset notice. Provider and network processes can change.
Next step
Build a repeatable inquiry workflow
Document who monitors notices, where records live, how deadlines are tracked, and how each submission and outcome is reconciled.
To learn more about how TSYS can help improve the way your organization accepts payments, markets to new customers, or manages its HR responsibilities, get in touch by calling 585-981-8463 to get started.
CONTACT US