DuplicateTransactionContributorConfig
A model the API reference uses in a request or a response. The operation pages link every field typed as this model here.
Duplicate Transaction Manager configuration: how long a transaction stays on record for duplicate detection, and what makes two transactions the same.
Values
Fields
| Field | Type | Description | ||||||
|---|---|---|---|---|---|---|---|---|
enabled
required |
boolean | Whether this rule runs. False, the default, means the rule is skipped and never flags a
transaction. A rule that is enabled but has no usable settings also screens nothing.
Values:
Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
| ||||||
actionWhenTriggered
required |
ActionWhenTriggeredType ActionWhenTriggeredType | What happens when this rule flags a transaction. `AuditOnly`, the default, records the
detection and lets the transaction continue. `Stop` halts the transaction before
authorization, and the caller receives HTTP 403 with the error code
`SCREENING_STOPPED`. `HoldForReview` parks the transaction on the fraud review
queue until a reviewer approves or declines it, or the merchant's hold deadline passes.
Whatever the action, the verdict is recorded on the transaction.
Values:
Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
| ||||||
settings
required |
DuplicateTransactionSettings DuplicateTransactionSettings | The duplicate-detection settings. Null leaves the rule unconfigured, which screens nothing.
Values:
Values combine: send one or more member names separated by a comma and a space, or the integer sum of their values. Responses carry the names.
| ||||||
Fields of DuplicateTransactionSettings: This body has no documented fields. | ||||||||
This model has no documented fields.