Watchlist

The Watchlist module checks customer identities against global sanctions lists, Politically Exposed Persons (PEPs), and other compliance watchlists during the onboarding and identity verification process.

---

Where it fits in the flow

The Watchlist module is typically performed after customer information has been collected and identity data is available for screening. It is positioned before onboarding completion or account approval to ensure the user is checked against sanctions lists, Politically Exposed Persons (PEPs), and other compliance watchlists as part of the risk evaluation process..

---

User Flow

The Watchlist experience guides users through an automated compliance screening process that checks customer identities against sanctions lists, Politically Exposed Persons (PEPs), and other global watchlists before returning a final verification result..

---

Full Flow Map

---

Happy Path (Light & Dark)

The ideal user journey occurs when the customer screening process completes successfully without interruptions, delays, or potential watchlist matches requiring additional review.

The happy path represents the smoothest version of the experience: the user submits their information, the system performs automated screening against sanctions lists, Politically Exposed Persons (PEPs), and compliance watchlists, and the verification completes successfully.

The user proceeds to the next step without encountering validation issues, manual review requirements, or blocking compliance matches. Light and dark mode previews are included to help teams validate visual consistency, accessibility, and contrast across themes and platforms.

---

Best Practices

Recommended guidelines for designing and implementing the Watchlist

✅ Do

• Clearly communicate that screening is in progress by displaying loading states and processing indicators during verification.
• Provide immediate visual feedback during watchlist screening to reassure users that the verification process is active.
• Use concise and user-friendly messaging to explain screening outcomes without exposing sensitive compliance logic.

❌ Don't

• Don’t allow users to interrupt or resubmit the screening process while verification is still in progress.
• Don’t expose internal compliance logic, risk rules, or watchlist matching criteria to end users.