> ## Documentation Index
> Fetch the complete documentation index at: https://developers.circle.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Transaction screening

Transaction Screening is a real-time tool that automatically checks blockchain
transactions and associated addresses for risks related to sanctioned entities,
terrorist financing, or other suspicious behaviors. This is a core component of
the [Compliance Engine](/wallets/compliance-engine) and it allows you to
configure screening rules to meet the specific compliance requirements of your
jurisdiction or industry.

You can trigger screening evaluations using two methods:

* Embedded: screening occurs implicitly during regular programmable wallet
  transaction flow.
* Standalone: screening is triggered explicitly through the Compliance API.

<Note>
  Compliance Engine on both testnet and mainnet is only available for eligible
  customers. Contact Circle through the
  [Compliance Engine request form](https://www.circle.com/wallets/compliance-engine/#get-in-touch)
  to get access.
</Note>

## Features

* **Custom rules**: Tailor your own screening rules to match your specific use
  and regulatory requirements.
* **Blocklist/Allowlist**: You can specify blocklisted or allowlisted addresses,
  enhancing control over transactions and minimizing the chance of interacting
  with known bad actors.
* **Real-time alerts**: The system provides immediate notifications when a
  transaction violates pre-set screening rules. Alerts can trigger actions such
  as blocking a transaction, freezing a wallet, or sending it for further manual
  review.
* **Detailed logs and API integration**: You can access detailed logs and
  results of screened transactions, enabling easier auditing and review. The
  system also offers a robust API for integrating screening capabilities into
  existing workflows.

## Embedded screening

For Wallets using embedded screening, the existing
[Get a transaction](/api-reference/wallets/developer-controlled-wallets/get-transaction)
API endpoint includes a response field, `transactionScreeningEvaluation`, for
transaction screening result, detailing:

* **Rule** found during screening
* **Actions** taken for the decision
* **Reasons** for the decision, related risk signals found during the screening:
  source, risk score, risk category, etc.

## Standalone screening

If you are using Wallets with standalone screening, Compliance Engine exposes a
new
[Screen a blockchain address](/api-reference/wallets/compliance/screen-address)
API endpoint, enabling you to screen a specific blockchain address on a given
[supported blockchain](/wallets/supported-blockchains) independently of any
transaction flow. The endpoint response returns the following:

* **Screening result**: High level of the screening result, either `APPROVED` or
  `DENIED`.
* **Screening decision**: Same information as the
  `transactionScreeningEvaluation` field above.
* **Detailed vendor response**: Findings from vendors to provide a deeper
  understanding of the screening results and their source. Note: values will
  only be available on testnet for the test cases provided on the
  [Testing guide](/wallets/compliance-engine/tx-screening-testing).

## Workflow

Compliance Engine is available for eligible users. Reach out to Circle through
the
[Compliance Engine request form](https://www.circle.com/wallets/compliance-engine/#get-in-touch)
to get access. Once approved, you can:

1. Customize your screening rules via the console to match your own risk and
   compliance requirements:\
   a. Check the
   [Compliance Engine whitepaper](https://6778953.fs1.hubspotusercontent-na1.net/hubfs/6778953/PDFs/Whitepapers/ComplianceEngine_whitepaper.pdf)
   (Part 3) for some helpful questions to consider when establishing your
   requirements.\
   b. Check the
   [Rule management](/wallets/compliance-engine/tx-screening-rule-management)
   guide for possible configurations.
2. Trigger a screening evaluation:\
   a. Through the
   [Screen a blockchain address](/api-reference/wallets/compliance/screen-address)
   API endpoint.\
   b. Through generating an onchain transaction via the
   [Transactions API](/api-reference/wallets/developer-controlled-wallets/list-transactions).

You can review detailed results for all rule matches and alerts on the
[Circle Console](https://console.circle.com/).