address-screening-workflow-concepts
Installation
SKILL.md
Address screening workflow (concepts)
Educational reference only. Exact limits (row counts, credit rules, field names) vary by product and release—confirm in live documentation (phalcon-compliance-documentation for Phalcon Compliance). Pair with risk-exposure-screening-concepts and behavioral-risk-screening-concepts for what engines measure.
What is being screened?
Addresses usually mean wallets or contracts on specific chains. In a VASP or platform context, these are often customer or counterparty addresses that touch your service. Proactive screening is meant to surface high-risk entities early so teams can apply policy (review, block, escalate)—not to replace legal process or law-enforcement channels.
Tags vs markers
| Concept | Typical role |
|---|---|
| Tags | Human-readable labels to distinguish addresses in the UI. Often split into default tags (from the provider’s curated or verified dataset) and user-defined tags. User-defined values commonly override defaults when both exist. |
| Markers | Categories by attribute or behavior (for example deposit address, frozen, VIP, pending review). |
System markers (often immutable in the product):
- Sourced from the provider’s risk or reference database (for example sanctioned, mixer—per vendor taxonomy).
- May be non-editable in the UI.