Skip to main content
FrankieOne’s Transaction and Activity Monitoring solution actively monitors both financial and non-financial activities against predefined rulesets to identify potential fraud and money laundering risks. This guide will walk you through how to review and manage these results within the FrankieOne Portal.

Reviewing Transaction and Activity Monitoring check results

Image
In the entities table, those with active Transaction and Activity monitoring issues will have an issue marked as Activity. To view all of these entities, find the Issues filter and select Activity. Issues Select an entity from the filtered results to go to the entity view. This view will display the workflow events tab with the transaction and activity monitoring check results.

Entity view

Activity and Alerts

An activity refers to an event or transaction that occurs within the FrankieOne system, such as a customer profile being created, a bank deposit transaction, or a login/registration event. An alert is created when an activity triggers certain thresholds or rules. Alerts indicate a potential issue, such as fraud or AML concerns, and often require review and action by a Fraud or Compliance Officer. Here’s a breakdown of their relationship:
  • Activity initiates a check: An activity (e.g., a transaction) triggers a check.
  • Check results in an Alert: If the check identifies something suspicious based on configured rules, an alert is generated.
  • Alerts are managed: Fraud and AML officers then manage these alerts, which might involve resolving them, creating a case for further investigation, or assigning them to a colleague.
Essentially, an “activity” is the transaction or event itself, while an “alert” is a notification or flag raised due to the risk assessment of that activity.

Alerts (Check results)

When the Evaluate API is called and the system detects potential transaction and activity monitoring issues, alerts are generated. These alerts indicate potential fraud or AML concerns that require investigation and resolution. These alerts are categorized into two primary sections:
  • AML transactions and activities - includes alerts related to suspicious financial transactions (for example, transfers, deposits, withdrawals) and activity patterns that may indicate money laundering or other financial crimes.
  • Fraud transactions and activities - includes alerts related to fraudulent transactions (for example, unauthorized payments) and high-risk behavioral activities (for example, unusual login attempts and account changes) often associated with account takeover or identity fraud.

Collapsed view

The collapsed view provides a high-level summary of the check results. This allows for a quick assessment of outstanding alerts or those currently flagged as ‘In Review’. It prominently highlights the specific rules that were triggered during the check, offering immediate insight into the potential risk areas. Collapsed view showing triggered rules summary

Expanded view

Expanding either the AML Transactions and Activities or Fraud Transactions and Activities section will reveal all individual alerts related to that issue type, along with their detailed information. Expanded view of AML and Fraud transaction alerts From here, you can select an alert from the table. This will open up a drawer on the right side showing the details of the alert such as: Alert details drawer showing activity and transaction information
  • Activity Details and Triggered Rules: Specific information about the activity that generated the alert and the rules that were triggered.
  • Transaction Details: Comprehensive information about the financial transaction, if applicable.
  • Device Signals: Data related to the device used, such as VPN detection, remote monitoring, and other device intelligence.
  • IP Signals: Information regarding the IP address, including location and associated risk.
For further investigation, select More details* to open an external link to the provider’s system in a new tab. This allows you to delve directly into the raw data or extended context provided by the underlying service. To learn more on Alerts, visit our Implementation Guide - Transaction and Activity monitoring.