Skip to main content

AML, PEP and ECDD

Assayra separates a candidate match from a confirmed identity and a policy outcome.

Screening​

Identity and business subjects can be screened against official sanctions plus tenant-entitled PEP/RCA, adverse-media and company/UBO sources. Every result records source provenance, dataset hash/version, match features and score.

An AML candidate blocks zero-touch approval when the workflow requires a clear result. A qualified analyst must disposition possible matches rather than treating fuzzy-name similarity as a confirmed hit.

Candidate disposition​

Common outcomes include:

  • false positive;
  • confirmed match;
  • insufficient information / evidence required; and
  • accepted risk under the tenant’s documented policy.

Record a rationale and evidence reference. Disposition does not delete the original candidate or source version.

Enhanced due diligence​

ECDD can collect structured:

  • purpose and expected account/product use;
  • employment, business and counterparties;
  • source of funds;
  • source of wealth;
  • jurisdictions and transaction expectations;
  • supporting evidence; and
  • reviewer assessment, approval, hold and expiry.

ECDD evidence follows the same tenant isolation, encryption, legal-hold and retention controls as identity evidence.

Ongoing screening​

Approved subjects can be enrolled with a tenant-defined cadence. The worker leases due checks, applies bounded retries, records source freshness and creates an attention case when a new candidate or material change occurs.

Use webhook events to wake downstream review. Do not repeatedly create new onboarding applications as a substitute for ongoing screening.

Data responsibility​

The API and provenance machinery can be complete before a specific licensed dataset is activated. Your production Country Assurance Pack must identify which sources and freshness rules are required for the market and customer type.