> For the complete documentation index, see [llms.txt](https://docs.compliance.phalcon.blocksec.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.compliance.phalcon.blocksec.com/manual/configure/risk-engines/behavior.md).

# Behavioral Risk Engine

The Behavioral Risk Engine is designed to identify suspicious transaction patterns.

Behavioral rules evaluate their thresholds directly: an alert triggers when all configured thresholds are met simultaneously.

## Address Behavior Engine

Phalcon provides three detection templates for identifying risky address behavior.

### 1. Large Transfer <a href="#id-1-large-transfers" id="id-1-large-transfers"></a>

Flags addresses with transaction volumes significantly exceeding thresholds for typical user behavior.

**Configuration:**

* **Direction** — Incoming, Outgoing, or both.
* **Min Transfer Value** — The minimum value of a single transfer (for example, ≥ $50,000).

**Example**: Address `0x742d35Cc6634C0532925a3b844Bc454e4438f44e` transfers out $100,000 in a single transaction, triggering an alert.

### 2. High-Frequency Transfer <a href="#id-2-high-frequency-transfers" id="id-2-high-frequency-transfers"></a>

Identifies addresses that conduct frequent transactions within a short time window, which may indicate structured transfers or layering.

**Configuration:**

* **Direction** — Incoming, Outgoing, or both.
* **Transfer Count** — The minimum number of transfers required (for example, ≥ 10 transfers).
* **Time Window** — The time period to evaluate (for example, within 60 minutes).
* **Transfer Value** — The value range per transfer. Set a minimum (for example, ≥ $500) and optionally a maximum.

**Example**: An address makes 15 incoming transfers within 30 minutes, each valued at $500 or more.

### 3. Transit Address <a href="#id-3-transit-addresses" id="id-3-transit-addresses"></a>

Detects addresses that act as intermediaries by quickly relaying received funds — a common money laundering technique.

**Configuration:**

* **Min Transfer Value** — The minimum received amount (for example, ≥ $10,000).
* **Time Window** — How quickly funds must be sent out after being received (for example, within 30 minutes).
* **Min Outflow Percentage** — The minimum percentage of received funds that must be sent out (for example, ≥ 80%).

**Example**: An address receives $50,000 and sends out 90% of it within 20 minutes.

## Transaction Behavior Engine

The Transaction Behavior Engine provides two detection templates for identifying and flagging risky transaction behavior to enable proactive risk monitoring.

### 1. Large Transfer <a href="#id-1-large-transfers-1" id="id-1-large-transfers-1"></a>

Identifies transactions with transfer amounts exceeding user-defined thresholds, as large transfers often require more rigorous review.

**Configuration:**

* **Direction** — Incoming, Outgoing, or both.
* **Min Transfer Value** — The minimum transfer amount (for example, ≥ $100,000).

**Example**: A transfer of $500,000 from Address A to Address B exceeds the configured threshold of $100,000, triggering an alert.

### 2. Rapid Transit <a href="#id-2-rapid-relay" id="id-2-rapid-relay"></a>

Detects transactions where received funds are rapidly sent out, indicating potential layering or evasion.

**Configuration:**

* **Time Window** — How quickly funds must be relayed (for example, within 10 minutes).
* **Min Transfer Value** — The minimum transfer amount (for example, ≥ $10,000).

This template applies to deposit transactions only — the direction is fixed and cannot be changed.

**Example**: A transaction receives $100,000 and the recipient sends it out within 10 minutes.
