Duplicate Transactions loading for Visa VCF4 Format due to issue with Transaction Reference Number
When a user has a lost or stolen card, the Visa company provides a new card with a new number. The unpaid transactions from the old card are transferred to the new card. The Visa company then sends these transactions to Fusion with a link to the new card.
Since these transactions already exist in Fusion, they should be recognized as duplicates and not load into Fusion. Fusion controls this via the "Transaction Reference Number", If this number is the same it will recognize it as a duplicate.
But from what we are seeing, only for the Visa VCF4 format, Fusion is creating a new "Transaction Reference Number" by concatenating 4 of the fields in the file. This is not happening for any other format. For the Visa VCF4 format transaction reference number is being created as a concatenation of the below 4 fields