> 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/duplicate.md).

# Duplicate

In this article, you will learn how to prevent duplicate payment disputes using appropriate preventive measures.

Duplicate payments often occur due to technical issues in the webshop. If a technical error occurs during the ordering process and the customer repeats the transaction, it might result in two transactions being processed. If the cardholder sees a payment duplicated or multiplied on their statement, they may dispute these charges.

Don't worry: There are several strategies to minimize "Duplicate" disputes.

### Recommendations

* Regularly check the webshop for potential technical issues.
* Implement automated or at least manual reviews of the ordering system for duplicate and multiple orders.
* Promptly remove any obvious duplicate and multiple orders.
* Engage in immediate customer communication in cases of duplicate and multiple orders.
* Send clear and detailed order confirmations.
* Promptly fulfill refund requests for duplicate payments.

If you nevertheless receive a dispute of this type, the following article provides helpful tips to help you resolve the dispute in your favor:

{% content-ref url="/pages/GSxff5nTAvrR2nLIY3bp" %}
[Duplicate](/merchant/english/payment/disputes/processing-and-submitting-evidence/duplicate.md)
{% endcontent-ref %}


---

# 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/duplicate.md?ask=<question>&goal=<user_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.