> For the complete documentation index, see [llms.txt](https://docs.xplorpay.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.xplorpay.com/guides/cloud-emv/manage-duplicate-transactions.md).

# Manage duplicate transactions

The [semi-integrated transactions API](https://docs.xplorpay.com/api-references/payments/cards/transaction-emv) endpoints let you configure enhanced settings to manage duplicate transactions.

The following settings help prevent duplicate transactions when you integrate with Cloud EMV solution:

## Check-field

The `check-field` lets you assign the value of another field—such as `invoice` or `purchase-order`—to help manage duplicate transactions. When you send a `check-field` request to the [semi-integrated transaction API](https://docs.xplorpay.com/api-references/payments/cards/transaction-emv) endpoint, the system checks for duplicate transactions using the `check-field`, transaction type, an Approved status, and the amount.

The `check-field` in the request checks for duplicate transactions before calling the cloud solution service to activate the [payment terminal](https://docs.xplorpay.com/getting-started/devices). If a duplicate is found, the API endpoint returns an HTTP 200 status code and includes the `check-field-duplicate` field with a value of `true`.

The `check-field-mid` field lets you query all terminals associated with a merchant identifier (MID).

{% hint style="warning" %}
The `transaction-emv` service checks for duplicate transactions by matching the last four digits of the card, the amount, an Approved status, and a time window of the past eight minutes.
{% endhint %}

## OLS gateway duplicate module

The OLS gateway duplicate module checks for duplicate transactions using the last four digits of the card, a time window of the past five minutes, an Approved status, and whether the `Include Invoice` setting is enabled in the duplicate check query.

The OLS gateway duplicate module triggers a query when a [payment terminal](https://docs.xplorpay.com/getting-started/devices) response returns a duplicate transaction with the `check-field-duplicate` field as `true`.

If duplicate check query is configured to return a success response (HTTP 200), Cloud EMV solution returns a “Transaction previously approved” message to the terminal when a duplicate transaction is found.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.xplorpay.com/guides/cloud-emv/manage-duplicate-transactions.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.