SMASH® is a solution for Enterprise Fraud Management of type Transaction Monitoring, working in real-time services of a financial nature, such as classic online banking or online payment in kind, in other words it is able to analyze real-time flows devices and to produce reports and / or blocks, always in real time.

SMASH® can be powered and customized, depending on the needs, even offline through the acquisition of large flows batch.

It is possible to configure SMASH® to check an arbitrary operation, generally any transaction subject to possible fraudulent use or that may facilitate the identification of irregularities. Fall into these categories:

• authentication (login) to the service;
• convey instructions (transfers, refills, etc..);
• other operations that may be critical in terms of security (setting of security parameters such as passwords, telephone numbers where to send SMS alerts, etc..) or operations that might be appropriate to monitor because sensitive (eg. request for account stated).

The "core" of the solution is constituted by an expert system able to "learn to recognize" users of the service, this core engine is based on over a hundred parameters that uniquely characterize the user of the service.

The benefits and the advantages of using SMASH

The solution is able to significantly reduce fraud in transactional scope without requiring the same time changes to applications to be protected.

Strengthens the part of authentication through the ability to use additional systems Out of Band (One Time Password sent via SMS), for the cases in which there is doubt about the adequacy of authentication.

It is based on behavioral analysis algorithms that can deal with even the new types of attack that will occur in the near future. It is not in fact of the application of static rules that must be updated periodically, but of a system able to learn from the feedback it receives from the management group-Fraud Office.

It offers a set of tools to manage the rapid identification and resolution of various incidents, thus optimizing the verification activities.

It is a "transparent" layer whose activation does not change the usual method of use, except in case of suspicious transactions that require, for instance,  a second test such as authentication.