Set Policy Rules on Screening Results

Screening results are a first-class input to the Fordefi policy engine. A policy rule can use a Transaction Screening condition to act on what a screening provider found, so that a flagged transaction is blocked or an approved transaction is allowed.

The Transaction Screening condition is part of the regular transaction policy, alongside the other rule conditions. It is not part of the AML policy.

A Transaction Screening condition selects a provider and one or more of that provider's results. The result field is multi-select, so a single condition can cover several severities for the same provider:

To match on both providers, add a Transaction Screening condition for each one, or write a separate rule per provider.

The Transaction Screening condition depends on the providers your organization has activated:

• If your organization has no credentials for a given provider, that provider is greyed out in the condition and cannot be selected.
• If your organization has no credentials for any provider, the Transaction Screening condition is greyed out in the conditions list and cannot be added to a rule.

You also cannot deactivate a provider while a policy rule still uses a Transaction Screening condition for it. Remove or edit those rules first.

Follow the instructions in Create a policy rule. When adding a condition, select Transaction Screening from the condition categories.

• Hard block on a denied transaction: A rule whose only condition is for the provider Hypernative and value Deny, and whose action is Block, stops any transaction that Hypernative denies.
• Stronger approvals for flagged transactions above a threshold: A rule with the condition on the provider Blockaid and value Warning and a transaction amount over USD 100,000, and an action of Require Approval with an admin quorum, lets small flagged transactions through the normal flow while escalating large ones.
• Escalate anything either provider flags: Two rules, one per provider, each selecting both of that provider's results and requiring approval.
• Allow verified transactions: A rule with a condition on the provider Hypernative and the values Approve and Autoapprove, or on the provider Blockaid with the value Benign, and an action of Allow, will allow every transaction the provider deemed safe.

A transaction with no usable screening result is still evaluated against your policy. What a Transaction Screening condition does then depends on why the result is missing:

• Unsupported chain: The Transaction Screening condition does not match, and policy evaluation continues to the next rule.
• Timeout, or provider error: The result is indeterminate, and Fordefi falls back to the default policy rule, as it does when simulation data is missing.

Because an unavailable provider falls back to the default rule, a permissive default rule weakens every screening rule above it. We recommend setting a strict default rule.

Learn more:

• Rule Conditions and Actions
• Create a policy rule
• View transaction screening results