> 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/screening/transactions.md).

# Transaction Screening

In Phalcon, the Transactions module enables users to screen on-chain transactions for risks, typically involving interactions between customers and your platform. By scanning every incoming or outgoing transaction in real time, Phalcon helps you promptly detect risky funds and ensure effective risk mitigation.

The smallest unit of transaction screening is a single transfer. If a transaction contains multiple transfers, you can screen them individually or in batches to comprehensively assess the overall risk of the transaction.

<figure><img src="https://1419887533-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPfx6yOSRmp0GCnHv5rhy%2Fuploads%2Fgit-blob-1b8dad20b48097600f7f3bbc930b6d5714ad92c2%2Fimage.png?alt=media" alt="Transaction screening page overview"><figcaption></figcaption></figure>

## Key Concepts

### Direction

The direction of a transaction or transfer determines the screening strategy applied.

* **Deposit**: When a transaction involves customer funds being deposited into the platform, set the direction to Deposit.
* **Withdrawal**: When a transaction involves customer funds being withdrawn from the platform, set the direction to Withdrawal.

Note: Specifying a direction affects the risk screening strategy. For example:

* If a risk engine is configured for **Deposit** transactions, it will not apply to transactions with the **Withdrawal** direction.
* For **Deposit** transactions, only incoming fund flows are traced and screened.
* For **Withdrawal** transactions, only outgoing fund flows and destination addresses are traced and screened.
* Setting the direction correctly allows customized risk rules to be applied to incoming and outgoing fund flows, reducing false positives.

If no direction is specified, transactions are screened as both Deposit and Withdrawal by default.

### Notes

Users can add notes to any transaction or transfer to record additional context or observations.

## Screening Transactions

Phalcon supports two methods for importing transactions:

1. Screen a single transaction hash.
2. Screen transactions in batches via CSV.

All transactions are automatically screened against active risk engines and displayed in the transaction list.

### Screening a Single Transaction

To screen a single transaction:

1. Enter the transaction hash you want to add. Phalcon will automatically retrieve the transfer data associated with the transaction.
2. Select the transfers you want to process.
3. You can:

   * Set the direction (Deposit or Withdrawal) to define the screening scope.
   * Assign labels to provide additional context.
   * Associate the transfer or transaction with a specific customer.

   <figure><img src="https://1419887533-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPfx6yOSRmp0GCnHv5rhy%2Fuploads%2Fgit-blob-7e8deb4476a07eabf10a579788d640dcdd78a67d%2Fimage.png?alt=media" alt="Screening a single transaction with direction and label options"><figcaption></figcaption></figure>

### Batch Screening via CSV

<figure><img src="https://1419887533-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPfx6yOSRmp0GCnHv5rhy%2Fuploads%2Fgit-blob-767067e96512b3836ee28117bab3b08c58f4b30e%2Fimage.png?alt=media" alt="Bulk transaction screening via CSV upload"><figcaption></figcaption></figure>

Users can import multiple transactions at once using a CSV file.

* Download the provided CSV template.
* Upload up to 400 transactions per batch.
* Complete the template using the following fields:

| Field            | Description                                                                    |
| ---------------- | ------------------------------------------------------------------------------ |
| Chain            | The specific chain name specified in the template                              |
| Transaction Hash | Blockchain transaction hash.                                                   |
| Label            | User-defined private label (optional)                                          |
| Direction        | Specify "Deposit" or "Withdrawal" to define the transfer direction. (Optional) |
| Customer ID      | Identifier of an existing or new customer (optional)                           |
| Transfer From    | Used with "Transfer To" to locate a specific transfer (optional)               |
| Transfer To      | Used with "Transfer From" to locate a specific transfer (optional)             |

* Upload the CSV file.
* Review the import results in the pop-up window and ensure that every required transaction has been imported successfully.

## Transaction List

All screened transactions are displayed on the transaction list page with the following details:

* Transaction hash
* Risk summary
* Screening direction
* Unresolved alerts
* Last screening time
* Value (USD)
* Token amount
* Assets involved
* Source and destination addresses
* Transaction timestamp
* Customer
* Labels
* Added timestamp

For transactions containing multiple transfers, the transfers are collapsed by default. Click to expand and view the details of each transfer.

<figure><img src="https://1419887533-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPfx6yOSRmp0GCnHv5rhy%2Fuploads%2Fgit-blob-feaf67be23ffc79fa963b78cfe40984981319083%2Fimage.png?alt=media" alt="Transaction list with expandable transfer details"><figcaption></figcaption></figure>

## Exporting Transactions

You can export the transaction list as a CSV file by clicking the **Export** button on the transaction list page. This feature is available only to users on paid plans.

The exported CSV contains the following fields:

| Field                           | Description                                                                                                                         | Example                                 |
| ------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------- |
| Chain                           | Blockchain network                                                                                                                  | ETH                                     |
| Tx Hash                         | Transaction hash                                                                                                                    | 0xa51fa6e0ccc6b9b3...                   |
| Transfer Index                  | Index of the transfer within the transaction. `0` if there is only one transfer                                                     | 0                                       |
| Risk Level                      | Risk level of the transfer                                                                                                          | Critical                                |
| Participant Risk Tags           | Risk tags of participating addresses. Multiple tags are separated by `;`                                                            | Scam; Blocked                           |
| Interaction Risk Breakdown      | Interaction risk indicators and details. Format: `{Risk Tag}: {Direction} {Value} ({Ratio})`. Multiple entries are separated by `;` | No KYC Exchange: Incoming $0.02 (0.08%) |
| Participant Risk Details (JSON) | Structured JSON for participant risks, used for programmatic parsing                                                                | See below                               |
| Interaction Risk Details (JSON) | Structured JSON for interaction risks, used for programmatic parsing                                                                | See below                               |
| Screen Direction                | Screening direction                                                                                                                 | Both                                    |
| Unresolved Alerts               | Number of unresolved alerts                                                                                                         | 2                                       |
| Last Screening Time             | Time of the most recent screening                                                                                                   | 2026-03-31 10:23:45                     |
| Value (USD)                     | Transfer value (USD)                                                                                                                | 5478.25                                 |
| Token                           | Token address or asset identifier                                                                                                   | BTC                                     |
| Amount                          | Token amount                                                                                                                        | 0.08199                                 |
| From Address                    | Sender address                                                                                                                      | bc1qhva56p9cnsc9d8j96...                |
| From Label                      | System label of the sender address                                                                                                  | Binance Hot Wallet                      |
| To Address                      | Recipient address                                                                                                                   | 3LhsVdFsMeSZhn...                       |
| To Label                        | System label of the recipient address                                                                                               | ChangeNow Hot Wallet                    |
| Transaction Time                | Time when the transaction occurred                                                                                                  | 2026-03-31 09:58:02                     |
| Customer                        | Associated customer ID                                                                                                              | Customer123                             |
| Note                            | User-added note                                                                                                                     | VIP deposit address                     |
| Added Time                      | Time when the data was added                                                                                                        | 2026-03-30 15:20:11                     |

**Participant Risk Details (JSON) example:**

```json
[
  {
    "riskIndicator": "Scam",
    "appliesTo": "from",
    "riskLevel": "critical"
  },
  {
    "riskIndicator": "Blocked",
    "appliesTo": "to",
    "riskLevel": "high"
  }
]
```

**Interaction Risk Details (JSON) example:**

```json
[
  {
    "riskIndicator": "No KYC Exchange",
    "direction": "incoming",
    "minHop": 1,
    "exposureValue": 0.02,
    "exposurePercentage": 0.0008,
    "riskLevel": "medium"
  }
]
```

## Transaction Details Page

<figure><img src="https://1419887533-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPfx6yOSRmp0GCnHv5rhy%2Fuploads%2Fgit-blob-81a41c4b9b3e6c1fd443a70551162824d6073c5a%2Fimage.png?alt=media" alt="Transaction details page overview"><figcaption></figcaption></figure>

Clicking a transaction in the **Transaction List** opens its **Details Page**.

### Basic Information

The **Basic Information** panel on the right displays the assets involved, transaction time, customer, block, transaction fee, and note.

### Screening Results

The screening results display the risk analysis from the most recent screening, organized into the following sections:

#### Risk Summary

A quick overview of all detected risks, divided into three categories: **Entity Risk**, **Interaction Risk**, and **Behavior Risk**. Each category has a link to its detailed view.

#### Entity Risk

Displays the risk attributes of all participating addresses in the transaction, grouped by address. Each address group displays:

* The address (with its label, if available) and its role in the transaction (for example, "Transfer No.1 · Sender" or "Transfer No.2 · Receiver").
* All risk attributes of the address—such as sanctions designations, known involvement in attacks, or blacklist/whitelist membership—including risk indicators, details, and triggered rules.

Address groups are sorted by risk level, with the highest risk first.

<figure><img src="https://1419887533-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPfx6yOSRmp0GCnHv5rhy%2Fuploads%2Fgit-blob-0c64b79f888391f9348197d512cf712bf392b982%2Ftx-entity-risk.png?alt=media" alt="Transaction Entity Risk showing a sanctioned participating address, Transfer No.1, sanctions source, and Triggered Rule link"><figcaption></figcaption></figure>

#### Interaction Risk

Shows how the transaction's participating addresses interacted with risky counterparties through fund flows. This section includes the same three subsections as the address details page:

* **Indicator Breakdown** — A bar chart comparing incoming and outgoing exposure for each risk indicator, distinguishing between direct and indirect exposure.
* **Risk Addresses** — A table containing counterparty addresses that triggered risk indicators. You can export the list as a CSV file.
* **Fund Flow** — A visualization of fund flows. Click **"View Detailed Fund Flow"** to open the complete analysis in MetaSleuth.

{% hint style="info" %}
**Triggered vs. Not Triggered**: An indicator is "Triggered" when its exposure reaches the threshold of a rule in your active risk engine, generating an alert. "Not Triggered" means exposure was detected but did not reach any threshold—it is provided for reference only.
{% endhint %}

#### Behavior Risk

Lists suspicious patterns detected in the transaction. Transaction-level behavior types include:

* **Large Transfer** — A transfer with a high USD value. Displays the transfer number, maximum value, and triggered rule.
* **Rapid Transit** — Funds received and sent out within a short period. Displays the value and time window.

<figure><img src="https://1419887533-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPfx6yOSRmp0GCnHv5rhy%2Fuploads%2Fgit-blob-204e7d243af0b1fe377918ff951e1ae8d59f212d%2Ftx-behavior-risk.png?alt=media" alt="Transaction Behavior Risk showing Rapid Transit and Large Transfer findings with transfer number, value, time window, and Triggered Rule links"><figcaption><p>A separate transaction example showing detected behavioral risks. The transaction in the overview above has no suspicious behavior detected.</p></figcaption></figure>

### Token Transfers

Displays all transfers in the transaction in two formats: a **fund flow chart** and a detailed list. Each transfer displays its associated alerts. Unscreened transfers are also listed, allowing you to initiate screening directly.

### Transfer Overview

Provides a quick-reference list of all transfers in the transaction, with shortcuts to navigate to the details of each transfer.

### Alerts, Audit Logs, and Comments

* **Alerts** — All alerts triggered by this transaction. Filter by status and click through to the Alert Center for details.
* **Audit Logs** — System-generated records of screening events, risk level changes, and other activities.
* **Comments** — Team members can leave notes and collaborate on investigations.

### Available Actions

* **Re-screen** — Re-screen the entire transaction or a specific transfer. A direction can be specified for each re-screening. Previous results remain visible while re-screening is in progress.
* **Share & Export** — Access sharing and report export actions, including a shareable screening result link and a **KYT Report**. Recipients can view the shared report without logging in.
* **STR Report** — Export data in a format that meets suspicious transaction reporting requirements. Select the reporting jurisdiction and ensure that the transfer direction was specified during screening. A separate STR report is generated for each transfer.
* **Delete** — Delete the transaction and all its associated transfers.

## Deleting Transactions

To delete a transaction and all its associated transfers:

Click the delete button on the transaction details page or in the transaction list.
