Skip to main content

Integration profile

ComplyAdvantage AML

AutoKYC ingests ComplyAdvantage screening results to power dual-provider AML controls, reducing false positives through weighted scoring and analyst voting. Every escalation inherits immutable audit logs and evidence attachments for regulatory reporting.

SaaS + Managed Services Coverage: Global sanctions, watchlists, and PEP data with daily refresh Data residency: EU, UK, US
Discuss integration rollout View developer documentation

Why teams pair with ComplyAdvantage AML

  • Dual-run AML policies compare ComplyAdvantage matches against secondary providers before escalating.
  • Voting and escalation engine captures analyst decisions with supporting evidence.
  • Privacy-by-design analytics ensure screening telemetry only fires post consent.

Use cases

Onboarding sanctions guardrail

Run ComplyAdvantage as the primary sanctions provider during onboarding while AutoKYC cross-checks high-risk hits with a secondary source.

Ongoing watchlist monitoring

Automate daily reruns for active customers and flag deltas directly in AutoKYC’s case queues.

Managed escalation packs

Managed Services compile regulator-ready narratives referencing ComplyAdvantage evidence, voting history, and remediation actions.

Setup steps

  1. 1

    Generate ComplyAdvantage API tokens

    Create read/write API tokens with IP restrictions; AutoKYC handles rotation and secrets storage.

  2. 2

    Define screening templates

    Configure ComplyAdvantage search lists and PEP/sanctions permutations, then import them into AutoKYC policy templates.

  3. 3

    Map risk scoring rules

    Align ComplyAdvantage risk scores with AutoKYC’s rules engine thresholds for auto-clear, review, or escalation actions.

Implementation notes

  • Webhook retries are automatically captured; AutoKYC surfaces failures in provider health dashboards.
  • Supports bulk screening via CSV or API; AutoKYC wraps both in a single workflow.

Operational considerations

  • Adverse media relies on English-language sources for some regions; supplement with local feeds if required.
  • Historical data beyond seven years may incur additional vendor storage costs.
  • Screening of crypto wallet addresses is not covered; use Chainalysis for blockchain exposure.