Manage post-screening policies

Create custom crypto compliance rules in Screening based on risk levels, transaction directions, and amount thresholds. Automate AML/CFT policy enforcement.

Post-screening policies automatically handle transactions based on their screening results. Each policy defines when it should apply (criteria) and what action to take when it matches.

Post-Screening Policies interface

To access this feature:

1. Log in to Cobo Portal
2. Click to open Cobo Portal Apps
3. Find and open Screening
4. Click Post-Screening Policies

The Post-Screening Policies interface enables you to manage your post-screening policies.

• Post-Screening Policies when using CipherOwl as the AML provider:

  

• Post-Screening Policies when using Elliptic as the AML provider:

  

You can filter the policies by Direction, Risk, USD Amount, Decision, AML Provider (CipherOwl or Elliptic), and Updated Time.

Create, edit, and delete policies

Select and configure your preferred AML provider in Settings first.

Create policies

1. Go to the Post-Screening Policies interface.
2. Click Create Policy.

• Create Post-Screening Policy dialog when using CipherOwl:

• Create Post-Screening Policy dialog when using Elliptic:

3. Define policy criteria and action.

Policy criteria

Policy Criteria	Options	Description
Direction	• Inbound • Outbound	Transaction flow direction
Risk	When using CipherOwl: • Low • Medium • High When using Elliptic: • NA • Numerical score from 0.0 to 10.0 (in 0.1 increments)	CipherOwl: Risk classification from CipherOwl Elliptic: Numerical risk score with higher values indicating higher risk (see Elliptic’s Risk Score documentation)
Amount Range	• Min Amount • Max Amount	Transaction value range (in USD)

Policy actions

Decision	Effect on transaction
Approve	• Inbound: Release funds • Outbound: Allow to proceed
Approve with Alert	• Inbound: Release funds + notification • Outbound: Allow + notification
Reject	• Inbound:   • Flag transactions and freeze funds     • Note: If you are using the auto token sweeping feature of MPC Wallets, frozen funds will not be included in the sweep operation. • Outbound: Block transaction • Risk notification is always sent

4. Click Submit to enable the policy.

When Screening has the scan results:

• Due to overlap prevention rules, at most one policy will match any given transaction
• A policy matches when the transaction’s direction, risk level (CipherOwl) or risk score (Elliptic), and amount range match the policy’s criteria
• When a match is found, Screening executes that policy’s action

If no policy matches, the transaction is automatically approved. To ensure proper risk management, make sure to set up appropriate policies that cover all your transaction scenarios before using Screening.

Overlap prevention rules

The system prevents creation of overlapping policies. A policy cannot be created if it has all of the following in common with an existing active policy:

• Same direction (Inbound/Outbound)
• Same risk level/score range
• Overlapping amount range

For example:

Policy 1: Inbound + Medium risk + ≥ 500 + < 1000 USD (Valid)
Policy 2: Inbound + Medium risk + ≥ 400 + < 7000 USD (Invalid - amount range overlaps with Policy 1)
Policy 2: Inbound + Medium risk + ≥ 600 + < 700 USD (Invalid - amount range overlaps with Policy 1)
Policy 2: Inbound + Medium risk + ≥ 1000 + < 7000 USD (Valid - amount range does not overlap)
Policy 3: Outbound + Medium risk + ≥ 1000 + < 7000 USD (Valid - different direction)

The policy examples above are for illustration purposes only. Your actual policies should be tailored to your organization’s specific compliance requirements and risk management strategy.

For CipherOwl, refer to CipherOwl’s Address Risk Score documentation or consult with their compliance experts via CipherOwl’s website. For Elliptic, refer to their Interpreting Risk Scores and Configuring Your Risk Rules documentation.

Edit policies

1. Go to the Post-Screening Policies interface.
2. Click next to the policy you want to edit.
3. On the Edit Post-Screening Policy dialog, make the necessary changes to the policy criteria and action (see Policy criteria and Policy actions).
4. Click Submit.

The same overlap prevention rules apply when editing policies.

Delete policies

1. Go to the Post-Screening Policies interface.
2. Click next to the policy you want to delete.
3. On the Delete Policy dialog, click Yes to confirm deletion.

Feel free to share your feedback to improve our documentation!