Elliptic screens transactions for blockchain risk, using Fireblocks' Anti-Money Laundering (AML) Transaction Screening Policy (Trigger) and AML Post-Screening Policy (Outcome) to decide which transactions get sent for screening and what happens based on the result. See Building a Compliance Policy for how Trigger and Outcome work in general.
This is a premium feature that requires an additional purchase. Contact your Customer Success manager if you do not already have an agreement with an AML provider.
How it works
Fireblocks sends transaction details, including the output address, transaction hash, and Customer Reference ID, to Elliptic for Know Your Transaction (KYT) screening. Elliptic returns a numeric risk score, rather than the categorical levels some other providers use.
You can view screened transactions on the Transaction History page, the Audit Log, or via the API. Transaction rejection information is available only from Fireblocks, not from Elliptic directly. Elliptic can also send you severity alerts for indirect risk exposure through its own UI.
Setup
Before you begin, complete the general setup of your compliance integrations.
- Create an API key and secret in Elliptic. Elliptic documents this in the AML API introduction. If you cannot create the keys yourself, contact your Elliptic account manager or Elliptic support.
-
Activate the integration in the Fireblocks Console:
- Go to Policies > Compliance > AML > Policy > Connect.
- Select Elliptic.
- Enter your API key and secret key.
Default Screening and Post-Screening policies apply automatically until you create your own.
To switch to new keys later, submit a ticket to Fireblocks Support with the new API key and secret key.
Processing
The subsections below describe how processing works.
Testing transaction rejection
You can test that rejection rules work before relying on them in production:
- Incoming: add a rule that accepts transactions above a small threshold (for example, $0.0568) and a final rule that rejects everything else, then send test transactions above and below that threshold.
- Outgoing: add a rule that rejects transactions Elliptic identifies as high-risk, then mark one of your own destination addresses as high-risk in Elliptic to trigger it.
Transactions that receive an "Unknown" result are not affected by these test rules, and both only apply within your configured blocking-timeout window.
Supported assets
Elliptic supports blockchains broadly, including cross-chain activity like bridges and swaps; newly deployed tokens are typically supported automatically.
Testnet assets are not currently supported.
FAQ
The questions below are the ones readers ask most often.
Can I see why a transaction was rejected?
Yes, through Fireblocks. Elliptic provides the risk result; Fireblocks provides the rejection details.
Does Elliptic support testnet transactions?
No. Testnet assets are not currently supported for Elliptic.
Developer portal
See AML policies for how Fireblocks screens transactions with Elliptic.