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.
The Post-Screening Policies interface
To access this feature:
- Log in to Cobo Portal
- Click
to open Cobo Portal Apps - Find and open Screening
- Click Post-Screening Policies
The Post-Screening Policies interface enables you to manage your post-screening policies through the following sections:
Policy list fields
| Field | Description |
|---|---|
| Policy No. | Unique identifier for the policy |
| Direction | Transaction direction: Inbound/Outbound |
| Risk Level | Risk level: Low/Medium/High |
| Min USD | Minimum transaction amount in USD (inclusive) |
| Max USD | Maximum transaction amount in USD (exclusive) |
| Decision | Action to take when policy matches: • Approve • Approve with Alert • Reject Coming soon: • Manual Review |
| Updated Time | When the policy was last modified |
Available filters
| Filter | Options |
|---|---|
| Direction | Inbound/Outbound |
| Risk Level | Low/Medium/High |
| USD Amount | Filter by amount (positive numbers only) |
| Decision | • Approve • Approve with Alert • Reject Coming soon: • Manual Review |
| Updated Time | Filter by when policy was last modified |
Post-screening policies
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.
Policy criteria
| Policy criteria | Options | Description |
|---|---|---|
| Direction | • Inbound • Outbound | Transaction flow direction |
| Risk Level | • Low • Medium • High | Risk classification from CipherOwl |
| 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 |
| Manual Review (Coming soon) | • Enable transactions to be reviewed by your team before being approved or rejected. |
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, and amount range match the policy’s criteria
- When a match is found, Screening executes that policy’s action
Creating, editing, and deleting policies
Creating policies
To create a new policy:
- Go to the Post-Screening Policies interface
- Click Create Policy
- Define policy criteria and action (see Policy criteria and Policy actions)
- Click Submit to enable the policy
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
- Overlapping amount range
For example:
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 guidance on risk assessment and policy creation, refer to CipherOwl’s Address Risk Score documentation or consult with their compliance experts via CipherOwl’s website.
Editing policies
- Go to the Post-Screening Policies interface
- Click
next to the policy you want to edit - On the Edit Post-Screening Policy dialog, make the necessary changes to the policy criteria and action (see Policy criteria and Policy actions)
- Click Submit
Deleting policies
- Go to the Post-Screening Policies interface
- Click
next to the policy you want to delete - On the Delete Policy dialog, click Yes to confirm deletion
Was this page helpful?