Skip to main content
Elliptic is an AML/KYT provider. It is a premium add-on that Fireblocks Support enables on Mainnet workspaces, and you connect it in the Console; there is no API for connecting. Through the API you read its policy and results the same way as for any AML/KYT provider; see AML/KYT Overview.

​
What is sent and returned

Fireblocks sends transaction hash (incoming) or destination address (outgoing), asset and blockchain, and the Customer Reference ID. Elliptic returns a numeric risk score. In GET /screening/transaction/{txId}, the risk field usually carries the score but can also carry categorical values such as noRiskDetected, so do not assume it is always numeric. Outcome (Post-Screening Policy) actions: Accept, Reject, Alert.

​
Connect

You need an Elliptic API key and secret; if you can’t create them, contact your Elliptic account manager. Enter both in the Console; default Trigger (Screening Policy) and Outcome rules apply until you create your own. To switch to new credentials, submit a ticket to Fireblocks Support.

​
Timeouts

If no result arrives in time, bypassScreeningDuringServiceOutages decides what happens; see Outage and delay settings.

​
Supported assets

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

​
Limitations

  • Mainnet only; Testnet assets are not supported, so you cannot test Elliptic screening on a Testnet workspace.
  • Rejection details are available only from Fireblocks, not from Elliptic.
  • Only Elliptic’s total risk score is used; source and destination sub-scores are not rule conditions. A null score is recorded as noRiskDetected.

​
On the Help Center

To connect Elliptic or test your rules in the Console, see Elliptic.