> For the complete documentation index, see [llms.txt](https://docs.payengine.co/developer-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payengine.co/developer-docs/dispute-management/retrieval-requests-and-chargebacks.md). # Retrieval Requests & Chargebacks The Interplay of Chargebacks and Retrieval Requests in Credit Card Networks In the realm of credit card transactions, understanding the difference between chargebacks and retrieval requests is crucial for merchants. These two processes serve distinct purposes, have unique implications, and play integral roles in maintaining a balanced and fair transaction ecosystem. A chargeback is a process initiated by a credit card issuer at the request of a cardholder disputing a specific transaction. It essentially reverses a payment, withdrawing funds from the merchant's account and returning them to the cardholder. This mechanism provides a layer of protection to consumers against fraudulent charges or unsatisfactory services. However, chargebacks can lead to potential financial losses and reputation damage for merchants. On the other hand, a retrieval request is a preliminary step often taken when a cardholder questions a specific charge on their statement. This process does not immediately involve the movement of funds but rather seeks additional information about the transaction from the merchant. The issuer requests documentation or evidence to verify the validity of the transaction. Interestingly, the retrieval request phase presents an opportunity for merchants to circumvent the possible negative repercussions of a chargeback. If a merchant issues a refund during a retrieval request, this pre-empts the need for a chargeback, thereby saving on associated costs and avoiding potential damage to their standing with the credit card network. Many chargeback prevention service companies use this tactic as a key strategy in their operations. These firms closely monitor transaction disputes and, upon identification of a retrieval request, guide merchants to proactively issue refunds where applicable. This is an effective method for preventing an actual chargeback from occurring, thus offering a win-win situation for all parties involved: the customer receives their refund, the merchant avoids additional fees and potential reputational damage, and the overall integrity of the transaction process is upheld. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.payengine.co/developer-docs/dispute-management/retrieval-requests-and-chargebacks.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.