> For the complete documentation index, see [llms.txt](https://docs.payrexx.com/merchant/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.payrexx.com/merchant/english/payment/disputes/prevention.md). # Prevention In this chapter, you will learn about the different categories of disputes and how to effectively avoid them using actionable prevention measures. ## Preventing Disputes Proactive prevention is the most effective strategy for managing disputes. To stop chargebacks before they occur, it is essential to understand their root causes and take early countermeasures. A transparent checkout process, crystal-clear communication, responsive customer service, and standard security measures play a key role in this effort. ### The 7 reasons for disputes When Payrexx notifies you that a dispute has been opened, one of the following seven reasons will always be specified. Click on a reason to learn how to best prevent disputes of this type.


Fraudulent	Occurs when stolen credit card data is misused or when a buyer unjustly disputes a legitimate transaction without cause.	Fraudulent
Credit not processed	Occurs when a merchant fails to issue an agreed refund in a timely manner following a cancellation or return.	Credit not processed
Duplicate	Occurs when a buyer's account is accidentally charged twice or multiple times for the same order.	Duplicate
Product not received	Occurs when the ordered goods fail to reach the buyer at all or when they arrive with severe delays.	Product not received
Product unacceptable	Occurs when delivered goods are damaged or differ significantly from the original product description.	Product unacceptable
Subscription canceled	Occurs when a recurring payment is charged even though the subscription was already canceled by the customer.	Subscription canceled
Unrecognized	Occurs when the opened dispute is based on other or unknown underlying reasons.	Unrecognized

--- # 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.payrexx.com/merchant/english/payment/disputes/prevention.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.