API - Profile
The Profiles API is used to expand the effectiveness of transaction analysis with more context through peer groups and custom profiles. A profile is a mutable set of attributes that factor into the rule engine's decision-making process during alert generation. The rule engine efficiently retrieves this data from the profile store using a fast key-value lookup. Profile updates occur through scheduled jobs, separate from the rule execution process. This ensures that the rule engine always has access to the most recent profile information without the need for real-time reconstruction.
A profile can be of the following types:
- Entity (sender or receiver)
- Combination of entities
- Peer Groups
Peer groups define entities with shared characteristics relevant to transaction analysis, such as the same business segment. Peer groups provide a baseline for expected entity behaviour related to transactions by comparing them to similar entities. For example, a business segment-based peer group can offer insights into expected transaction amounts, frequencies, and relationships e.g. how often same two entities share transactions.
Custom profiles give an additional layer of control for business rule analysis, by defining or modifying values that can be referenced by active business rules. These profiles are not directly related to any entity or transaction, instead serving as generic references. For example, a custom profile can be built to define how many transactions with the same amount, between the same entities, should trigger a business rule and change that threshold through an API call to that custom profile.