Fordefi lets you screen outgoing transactions for risk with external screening providers, alongside Fordefi's own risk engine. Screening runs before the transaction is signed, so the risks that a provider finds are shown to the initiator and to every approver while the transaction can still be cancelled.
The supported providers are Blockaid and Hypernative. Screening is opt-in per organization and self-serve: an organization admin activates a provider by saving valid credentials for it. Until credentials are saved, nothing changes in your transaction flow.
Once a provider is active:
- Risks are shown with the transaction. Provider risks appear next to Fordefi's own risks in the transaction preview, in the transaction details, and in the transaction history, each attributed to the provider that found it. See View transaction screening results.
- Risks become a policy condition. You can write policy rules on the screening result, for example to block a transaction that Hypernative denies, or to require an admin quorum for a transaction that Blockaid flags as a warning. See Set policy rules on screening results.
Screening results are informational on their own. As with Fordefi's own risk engine, the presence of a risk does not block a transaction unless a policy rule acts on it.
You obtain credentials directly from the provider, under your own contract with them. Fordefi does not resell either provider and does not verify your commercial relationship — it validates and stores the credentials you supply, and calls the provider's API with them. Any quota or rate limit consumed by screening is consumed against your own account with the provider.
| Provider | Credentials required |
|---|---|
| Blockaid | API key |
| Hypernative | Client ID and client secret |
| Chain type | Networks | What is screened |
|---|---|---|
| EVM | Mainnets only, varies by provider | Transactions and messages |
| Solana | Mainnet only | Transactions |
| Bitcoin | Mainnet only | Transfers and PSBTs |
Coverage within each chain type also depends on the provider. If a provider does not support the chain of a given transaction, Fordefi shows the transaction as not screened rather than as an error. See Unsupported chains, errors, and timeouts.
Transactions on testnets and on chain types not listed above are not screened.
- Organization admins: Can activate a provider by saving valid credentials, edit those credentials, test the connection, and deactivate a provider.
- Traders: Can see screening results in transaction and swap previews, and in transaction details and history.
- Viewers: Can see screening results in transaction details and history. Viewers do not create transactions, so previews do not apply to them.
Learn more: