Only available on the Pro plan.

​
Overview

Protecting your financial operations from fraudulent activities requires a careful balance of security measures and operational efficiency. This guide will walk you through the essential settings for configuring fraud detection parameters, helping you establish effective barriers against unauthorized or suspicious transactions while minimizing false positives that could impact legitimate business operations. Whether you’re new to fraud prevention or looking to optimize your existing security measures, understanding these thresholds is crucial for maintaining a robust defense against financial fraud.

​
Setting thresholds

Blnk automatically sets a minimum configuration once anomalies are activated for your Cloud workspace.

​
Similar transactions

Together, these settings create a balanced system for detecting suspicious patterns while minimizing false alarms. For example, to trigger an alert, you would need at least 3 transactions (Minimum Similar Count) within 30 minutes (Time Window) that are within 5% of each other’s value (Amount Difference) and share at least 70% of their characteristics (Similarity Score).

​
Immediate withdrawals

Consider a new deposit of $2,000. Because this exceeds the minimum amount ($1,000), the system begins monitoring. If someone attempts to withdraw $1,500 (75% of the deposit) within 5 minutes of the deposit, this would trigger an alert because it exceeds the 70% withdrawal ratio within the time window.

​
Balance frequency

​
Dormant balance

Consider an account with a balance of $5,000 that hasn’t had any transactions (deposits, withdrawals, or transfers) for 12 days. Because this account exceeds the minimum amount threshold of $100 and has been inactive longer than the 10-day dormancy period, it would be flagged for review.

​
Suspicious word patterns

Let’s say you’ve added custom keywords related to your industry’s specific risks. If a transaction description contains “rush processing” or “urgent transfer” (examples of potential custom keywords), the system would flag it because it meets the minimum match count of 1.

​
Amount deviation

Let’s say you’ve added custom keywords related to your industry’s specific risks. If a transaction description contains “rush processing” or “urgent transfer” (examples of potential custom keywords), the system would flag it because it meets the minimum match count of 1.

​
High risk countries

You can specify the state and street of a location via: [Country]-[State]-[Street]. For example, Brazil-Rio.

​
PEP screening

To enable PEP screening for your organization:
  1. Toggle on the main PEP Screening switch at the top to activate the overall monitoring system.
  2. Verify that Individual Screening is enabled (blue switch).
  3. Enable Organization Screening by clicking its switch, ensuring you can monitor both individual PEPs and organizations where PEPs have significant control (25% ownership or more).

​
Need help?

Let’s help you get started with Cloud! Whether you’re setting up your first workspace or adding Cloud to your existing tools, our team is here to help you succeed. Contact our Support team to get answers and expert guidance on making the most of Cloud.