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

# Elliptic

> How Fireblocks screens transactions with Elliptic for AML/KYT: what is sent, the risk result you get back, timeouts, supported assets, and the API endpoints you work with.

Elliptic screens your incoming and outgoing transactions for blockchain risk. Your AML/KYT Trigger (Screening Policy) decides which transactions are sent to Elliptic, and your Outcome (Post-Screening Policy) decides what happens with the result. See [AML/KYT Overview](/docs/aml-kyt-overview) for how AML/KYT fits into screening.

Elliptic is a premium add-on. Fireblocks Support enables it on your workspace, and you connect it in the Console. It's available on Mainnet workspaces only.

## How it works

Fireblocks sends Elliptic the transaction details, including the output address, the transaction hash, and the [Customer Reference ID](/docs/customer-reference-id). Elliptic returns a numeric risk score, and can also return categorical values such as `noRiskDetected` in the `risk` field.

Rejection details are available only from Fireblocks, not from Elliptic. Elliptic can also alert you to indirect risk exposure in its own platform.

## Connect Elliptic

You need an Elliptic API key and secret. If you can't create them yourself, contact your Elliptic account manager or Elliptic support. Enter both in the Console to connect. Default Trigger (Screening Policy) and Outcome (Post-Screening Policy) rules apply until you create your own. There is no API to connect to a provider. To switch to new credentials later, submit a ticket to Fireblocks Support.

See [Elliptic](https://support.fireblocks.io/hc/en-us/articles/30614362937372-Elliptic) on the Help Center for the Console steps.

## Timeouts

Fireblocks waits up to 10 minutes for a result on incoming transactions, which Elliptic resolves by transaction hash after a number of blockchain confirmations, and up to 1 minute on outgoing transactions, which it resolves by address. If no result arrives in time, `bypassScreeningDuringServiceOutages` decides what happens. See [Compliance Policies](/docs/compliance-policies#configure-outage-and-delay-behavior).

## Work with results through the API

| Task | Endpoint |
| - | - |
| Read the AML/KYT Trigger (Screening Policy) and Outcome (Post-Screening Policy) | [`GET /screening/aml/screening_policy`](/api-reference/compliance/aml--view-screening-policy), [`GET /screening/aml/post_screening_policy`](/api-reference/compliance/aml--view-post-screening-policy) |
| Read a transaction's result | [`GET /screening/transaction/{txId}`](/api-reference/compliance/provides-all-the-compliance-details-for-the-given-screened-transaction), in the `aml` and `amlList` fields |
| Configure outage and delay behavior | [`PUT /screening/aml/policy_configuration`](/api-reference/compliance/update-aml-configuration) |

See [Compliance Policies](/docs/compliance-policies) and [Transaction Screening Operations](/docs/transaction-screening-operations) for details.

## Supported assets

* Elliptic supports blockchains broadly, including cross-chain activity such as bridges and swaps. Newly deployed tokens are usually supported automatically.
* Testnet assets are not supported.

## On the Help Center

To connect Elliptic or test your rules in the Console, see [Elliptic](https://support.fireblocks.io/hc/en-us/articles/30614362937372-Elliptic).