Data in Risk Analytics: relationship hierarchy

Data inside Risk Analytics is stored in a relationship hierarchy. This serves to organize the data in a single-customer view. In Risk Analytics Presentation Service A highly dynamic web interface that provides webpages for the user to intuitively interact with Risk Analytics. It is a Microsoft .NET 4.7.2 ASP.NET application hosted inside Microsoft Internet Information Services (IIS)., this hierarchy consists of several layers, or items, and is rendered and managed in form of pending alerts.

Pending alerts contain information on transactions or non-monetary events (NME) that have matched a rule Rules are used to define sets of criteria to verify if an event (transaction and non-monetary event) matches any fraudulent behavior. If an event matches a previously defined rule, an alert can be raised..

Relationship

Represents one customer, irrespective of the number of applications or accounts held for that customer.

Application

Application for accounts. An application can hold any number of accounts for one customer, and they can be applications across all channels.

Account

Contains the financial transactions. Such a transaction can be a bank account, a credit card account, a savings account, or a group of different kinds of banking accounts related to the application level.

Transaction

Operation on a single account; e.g. credit card transactions, account payments etc.

Non-monetary event

For example logging in to an account.

Every monetary event is attached to an account in Risk Analytics Presentation Service, whereas non-monetary events can be attached to an account as well as an application or a relationship.

Any event record is processed unhindered, regardless if an account record exists!