Duplicate Checking Items from the Transaction Server

To configure the Transaction Server to perform duplicate checking on transactions in the FTM database, use an extraction profile. The batch (ICL) is marked as duplicate detected (DUP_DETECTED column) once all transactions have been successfully processed by the Duplicate Detect engine. The batch (ICL) is marked as duplicate reviewed (DUP_REVIEWED column) once all transactions that were flagged as potential duplicates by the engine are reviewed. If the engine does not find any potential duplicates, the batch (ICL) is immediately marked as duplicate reviewed.

Transaction Server sends all non-exception transactions in a batch (ICL) to Duplicate Detect. Exception transactions are not sent to Duplicate Detect. If the transaction is an unhandled exception that is waiting on a Payment Repair or Suspect Image Review operator, it is marked as a potential duplicate. Once the transaction is reviewed, accepted, and fixed by the operator, it is sent to Duplicate Detect. If the operator rejects the transaction, the potential duplicate flag is turned off and the transaction is never sent to Duplicate Detect.

When extracting data from the FTM database, the DuplicateDetectWriter, by default, sends all non-exception transactions for each batch (ICL) to the Duplicate Detect engine for duplicate checking. The extraction process populates the following fields to send to the Duplicate Detect API. These fields match the Duplicate Detect reference implementation for checking duplicate transactions.

Table 1. Field names and source of value
Duplicate Detect Field Name	Source of Value (TABLE.COLUMN_NAME)
AMOUNT	ITEM.FIELD_1
PROCESS_CONTROL	ITEM.FIELD_2
ACCOUNT	ITEM.FIELD_3
FIELD_4	ITEM.FIELD_4
ROUTING_TRANSIT	ITEM.FIELD_5
EXT_PROC_CODE	ITEM.FIELD_6
AUX_ONUS	ITEM.FIELD_7
PAYMENT_ID	PAYMENT.PAYMENT_ID
SOURCE	PRESENTMENT.ORIGIN_TYPE
SOURCE_COMP	"TXS"
COLLECTION_TYPE	PRESENTMENT.COLLECTION_ID
ORIG_RT	PRESENTMENT.ORIGIN
ITEM_SEQ_SORTER	PAYMENT.ITEM_SEQ_SORTER
ITEM_SEQ_NUM	PAYMENT.ITEM_SEQ_NUM
BUS_DATE	BUSINESS_DAY.DATE
BUS_CATEGORY	BUSINESS_DAY.CATEGORY

Users can specify a user exit, allowing them to change the default field names and values being sent to the Duplicate Detect API. If specified, the user exit is called for each transaction before it is sent to the Duplicate Detect API. Users have the ability to add, delete, and modify the fields being passed to the API. You may also decide not to send a particular transaction to be duplicate checked at all (for instance, if you want to exclude transactions below a certain dollar amount). For more information, see Duplicate Detect User Exit.