> 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/integrations/fireblocks.md).

# Fireblocks

This guide explains how to use Phalcon Compliance with [Fireblocks](https://www.fireblocks.com/) to screen outbound and inbound transactions for AML/CFT risks. By combining the two platforms, you can screen outbound transactions before execution and monitor inbound transactions when they are detected by Fireblocks.

## Prerequisites

**Required for basic setup:**

* An active Phalcon Compliance account with an API key (see [API Keys](https://docs.compliance.phalcon.blocksec.com/manual/account/api-keys.md))
* A Fireblocks workspace with webhook or API access

**Required for advanced setup only:**

* **API Co-Signer** for automatically screening outbound transactions through a callback handler (see [Fireblocks Co-Signer Overview](https://developers.fireblocks.com/docs/use-cosigners-for-signing-automation))
* **Manual Screening Verdicts** for the manual inbound verdict workflow (contact your Fireblocks Customer Success Manager to enable this feature)

## Screen Outbound Transactions

When your organization sends funds through Fireblocks, you can use Phalcon Compliance to screen the destination address **before** the transaction is signed and broadcast. There are two methods:

### Option 1: Pre-Screening via the Phalcon API

Before submitting a transaction to Fireblocks, use the Phalcon Compliance API to screen the destination address. Based on the risk assessment, your team decides whether to proceed.

**How it works:**

1. Your team submits the destination address to Phalcon Compliance through the [Screen a Single Address](https://docs.compliance.phalcon.blocksec.com/api-documentation/address-screening/screen-a-single-address.md) API or the Phalcon dashboard.
2. Phalcon Compliance returns a risk assessment, including the risk level, risk indicators, and exposure details.
3. Your team reviews the results and makes a decision based on your internal compliance policies:
   * **Unacceptable risk** — Reject the transaction. Do not submit it to Fireblocks.
   * **Acceptable risk** — Proceed with creating the transaction in Fireblocks.
4. If accepted, submit the transaction to Fireblocks through the Fireblocks API or console.

<figure><img src="https://1419887533-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPfx6yOSRmp0GCnHv5rhy%2Fuploads%2Fgit-blob-510225c099a70cfdc6aa2f3c3295359e4fd524d6%2Ffireblocks-outgoing-option1-pre-screening.png?alt=media" alt="Outgoing transaction pre-screening flow: You screen the address through Phalcon Compliance before submitting the transaction to Fireblocks"><figcaption><p>Pre-screening flow: screen the destination address through Phalcon before submitting the transaction to Fireblocks.</p></figcaption></figure>

**Key points:**

* No additional infrastructure is required. You only need your Phalcon API key.
* You can configure Phalcon's [Notification Channels](https://docs.compliance.phalcon.blocksec.com/manual/configure/notification-channels.md) to alert stakeholders when a high-risk address is detected.

### Option 2: Automated Screening Using a Callback Handler

This method uses an [API Co-Signer Callback Handler](https://developers.fireblocks.com/docs/create-api-co-signer-callback-handler) to integrate Phalcon Compliance directly into the Fireblocks transaction signing workflow. Every outbound transaction is automatically screened before the Co-Signer signs it.

**How it works:**

1. Initiate a transaction through the Fireblocks API.
2. The transaction passes through the Fireblocks Transaction Authorization Policy (TAP).
3. The API Co-Signer running in your environment receives the transaction details from the Co-Signer Gateway.
4. The Co-Signer forwards the transaction details to your **callback handler**, a custom HTTPS server that you deploy.
5. Your callback handler calls the [Phalcon Compliance API](https://docs.compliance.phalcon.blocksec.com/api-documentation/address-screening/screen-a-single-address.md) to screen the destination address.
6. Based on Phalcon's risk assessment, your callback handler returns a decision:
   * **Approve** — The Co-Signer signs the transaction and sends the signature to the Co-Signer Gateway.
   * **Reject** — The Co-Signer cancels the transaction.

<figure><img src="https://1419887533-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPfx6yOSRmp0GCnHv5rhy%2Fuploads%2Fgit-blob-38672a87ea0db3d283458130f5e2478f84893be7%2Ffireblocks-outgoing-option2-callback-handler.png?alt=media" alt="Automated outgoing transaction screening flow: Callback Handler integrates Phalcon Compliance into the Fireblocks Co-Signer signing process"><figcaption><p>Automated screening flow: the Callback Handler screens transactions through Phalcon Compliance before the Co-Signer signs.</p></figcaption></figure>

**Key points:**

* The API Co-Signer expects a response from the callback handler within **30 seconds**.
* You have full control over the risk threshold logic in the callback handler.
* For details on configuring the Co-Signer, see the [Fireblocks Callback Handler Documentation](https://developers.fireblocks.com/docs/create-api-co-signer-callback-handler).

## Screen Inbound Transactions

When your Fireblocks workspace receives funds, you can use Phalcon Compliance to screen the sender address and assess its risk. There are two methods:

### Option 1: Automated Screening via Webhook

Connect a Fireblocks webhook to Phalcon Compliance to automatically screen inbound transaction events. You can use the webhook endpoint provided by Phalcon or deploy your own webhook server that calls the [Phalcon Compliance API](https://docs.compliance.phalcon.blocksec.com/api-documentation/address-screening/screen-a-single-address.md).

**How it works:**

1. Set up a webhook endpoint to receive Fireblocks transaction events. You can use the webhook URL provided by Phalcon Compliance or deploy your own server that calls the [Phalcon Compliance API](https://docs.compliance.phalcon.blocksec.com/api-documentation/address-screening/screen-a-single-address.md).
2. Register the webhook URL in your Fireblocks workspace (see the [Fireblocks Webhooks Documentation](https://developers.fireblocks.com/reference/webhooks-overview)).
3. When an inbound transaction is detected, Fireblocks sends the event to the webhook endpoint.
4. The event is parsed, and the relevant sender address is screened by Phalcon Compliance.
5. Based on the risk assessment:
   * **Risk detected** — An alert is created in Phalcon Compliance for your team to review.
   * **No risk detected** — The screening result is recorded. No further action is required.

<figure><img src="https://1419887533-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPfx6yOSRmp0GCnHv5rhy%2Fuploads%2Fgit-blob-946b6cf09c4c4be65219e737bd51a2b129fbb426%2Ffireblocks-incoming-option1-webhook.png?alt=media" alt="Automated incoming transaction screening flow: Fireblocks sends events to Phalcon Compliance via webhook for screening"><figcaption><p>Automated incoming screening: Fireblocks sends transaction events to Phalcon Compliance for screening.</p></figcaption></figure>

**Key points:**

* Screening is based on the risk engine and thresholds configured in Phalcon Compliance.
* Configure [Notification Channels](https://docs.compliance.phalcon.blocksec.com/manual/configure/notification-channels.md) to alert your compliance team when risk is detected.
* If you need help setting up the webhook integration, contact us at ***<phalcon_support@blocksec.com>***.

### Advanced: Manual Screening Verdicts

> For compliance teams that require manual review and explicit approval of every incoming transaction.

{% hint style="warning" %}
This feature has limited availability in Fireblocks. Contact your Fireblocks Customer Success Manager to enable Manual Screening Verdicts for your workspace.
{% endhint %}

When Manual Screening Verdicts are enabled, inbound transactions remain in the `PENDING_SCREENING` status until your compliance team submits a verdict. Your team uses Phalcon Compliance to assess the risk and then submits a verdict to Fireblocks.

**How it works:**

1. An inbound transaction arrives in your Fireblocks workspace and is placed in the `PENDING_SCREENING` status.
2. Your compliance team is notified of the pending transaction.
3. Your team screens the sender address in Phalcon Compliance and reviews the risk assessment.
4. Based on the review, your team submits a verdict to the Fireblocks API (`POST /aml/verdict/manual`):
   * **Accept** — The transaction is released for processing.
   * **Reject** — The transaction is flagged and frozen in Fireblocks.
5. If no verdict is submitted within **one hour**, Fireblocks automatically rejects and freezes the transaction.

<figure><img src="https://1419887533-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPfx6yOSRmp0GCnHv5rhy%2Fuploads%2Fgit-blob-ff841d6e61f27e4c54e709879510fda256561c60%2Ffireblocks-incoming-option2-manual-verdict.png?alt=media" alt="Manual incoming transaction screening flow: Compliance team reviews in Phalcon Compliance and submits a verdict to Fireblocks"><figcaption><p>Manual screening: your compliance team reviews the risk in Phalcon Compliance and submits a verdict to Fireblocks.</p></figcaption></figure>

**Key points:**

* Manual Screening Verdicts apply only to inbound transactions. Outbound transactions are unaffected.
* The webhook method (Option 1) and Manual Screening Verdicts **cannot be used simultaneously** — you must choose one method for screening inbound transactions.
* The one-hour timeout provides a safety net, but your team should aim to review and respond promptly.

## Next Steps

* [Risk Engine](https://docs.compliance.phalcon.blocksec.com/manual/configure/risk-engines.md): Customize risk thresholds and indicators for your compliance policies.
* [Notification Channels](https://docs.compliance.phalcon.blocksec.com/manual/configure/notification-channels.md): Set up alerts when high-risk activity is detected.
* [API Keys](https://docs.compliance.phalcon.blocksec.com/manual/account/api-keys.md): Generate credentials for the Phalcon Compliance API.
* [API Documentation](https://docs.compliance.phalcon.blocksec.com/api-documentation/introduction.md): Endpoint details and request/response examples.
