Electronic Case Management

If a card transaction is classified as suspicious – whether it is by the monitoring system or by a different source – the system creates an electronic record - a case. Automatic case creation after the occurrence of pre-defined events is also possible. In order to collect all relevant card holder and transaction information linked to a case, the application interfaces to all relevant systems (monitoring system, authorisation system, card management, etc.). Subsequent investigation processes are facilitated by automated correspondence generation or reminder functionalities. Card and case history, which are essential information for detailed and effective case analysis, are also provided by the application. To complete the case management tool set, the fraud loss per case is calculated automatically and all transactions are marked with the corresponding fraud type (e.g. Counterfeit, card not present, etc.).

Marking Transactions

To facilitate evaluation and interpretation of the available fraud figures, MINTify allows adding further information to the already existing transaction data elements. Amongst others this includes specifying a fraud type for declined authorisation requests, highlighting cards that have been detected in a previous CPP search or those included in a scheme alert. SAFE and TC40 reporting data is held in the data base and can be assigned to existing authorisation transactions. Information is automatically added to a transaction, such as by whom the transaction has been marked as suspicious or if the cardholder registered a complaint. This additional information added to a transaction allows a significant gain when interpreting key performance indicators.

Forwarding to Dispute

MINTify provides support at all levels of fraud prevention beginning at a suspicious transaction up to confirmed fraud. This includes forwarding fraud cases directly to the chargeback system in order to prevent manually re-entry of data and reducing the processing time. Simultaneously fraud reporting is achieved as the fraud type code is also provided. Depending on the scope of the interface, fraud reporting data can be re-delivered to the application and stored in the data base and information about the fraud case status can be exchanged.