Fireblocks sits between your wallets and the blockchain: every transaction you send or receive passes through Fireblocks before it settles. Screening through Fireblocks means compliance results are applied at that same point, directly in the transaction's path, rather than generated separately and enforced by systems you build yourself.
This matters because of where the decision gets made. If you screen a transaction outside Fireblocks, you get a risk result, but you are still responsible for connecting that result to the transaction and deciding whether to stop, allow, or flag it yourself.
Screening through Fireblocks removes that middle step: the same platform that holds and moves your assets also applies the outcome, so a blocked transaction is blocked before it leaves your workspace, not after the fact.
Beyond applying the outcome directly, Fireblocks maintains the infrastructure on which this depends. Provider connections are updated as vendors change their APIs, and as Fireblocks adds support for new blockchains and assets, the screening integrations are extended to cover them as well.
If a check does not run or gets stuck, it is visible directly in your transaction history, rather than something you would need to build your own monitoring to detect. See Transaction Screening Operations for what that looks like.
What this looks like in practice
Once your policy is set up, you do not need to take any additional action per transaction: Fireblocks applies it automatically to every matching transaction.
Scope and limitations
This applies to transactions and counterparties within Fireblocks. It does not extend to activity that happens entirely outside your Fireblocks workspace.
Screening through Fireblocks applies the outcome you have configured. It does not replace your compliance program, your obligation to investigate flagged activity, or your own regulatory judgment. Fireblocks enforces the result; deciding what your policy should do with that result is still yours.
To start setting this up, see Building a Compliance Policy.
FAQ
The questions below are the ones readers ask most often.
If I have already run screening outside Fireblocks, do I have to switch?
No. Bring Your Own Screening lets you pause a transaction for your own verdict, based on whatever review process or provider you already use, and still have Fireblocks apply the outcome automatically. See About Bring Your Own Screening.
Is my screening data shared with other Fireblocks customers?
No. Screening data and policy configuration are specific to your workspace and are not shared with other customers.