# DuplicateCheckSettings

A model the API reference uses in a request or a response. The operation pages link every field typed as this model here.

Duplicate-check permissions carried on the merchant. Only `allowOverride` is live: it
decides whether a single transaction request may waive the Duplicate Transaction Manager rule. The
rule itself, including its window, is configured under Transaction Screening on the merchant flow
configuration. The other two properties are retained for API compatibility and ignored by screening.

## Fields
- `enable` (boolean): Retained for API compatibility and ignored by screening. Whether duplicate screening runs is  decided by the Duplicate Transaction Manager rule under Transaction Screening  (`Screening.Contributors.DuplicateTransaction.Enabled`), which is the configuration that  applies. This value round-trips through create, update and read unchanged, and nothing reads  it for a screening decision.
- `includeInvoiceNumber` (boolean): Retained for API compatibility and ignored by screening. Whether the invoice number narrows  the duplicate window is decided by the Duplicate Transaction Manager rule under Transaction  Screening (`Screening.Contributors.DuplicateTransaction.IncludeInvoiceNumber`), which is  the configuration that applies. This value round-trips through create, update and read  unchanged, and nothing reads it for a screening decision.
- `allowOverride` (boolean): Whether a single transaction request may waive the Duplicate Transaction Manager rule. Unlike  the two settings above this one is live: it is the only duplicate-check permission carried on  the merchant, and the screening rule honours it per request.

## See also

- [All documentation](https://devportal.demo.winkpg.io/llms.txt): the machine-readable index of every public page on this site.