Skip to main content
The ComplyAdvantage Connector integrates with ComplyAdvantage to help you streamline anti-money laundering screening and monitoring for KYC. Financial institutions can use this connector to fulfill their compliance obligations in accordance with FATF and 6AMLD regulations. This connector supports KYC customer screening only; it does not support KYB business screening.

​
Key capabilities

Real-time verification

Instant screening against watchlists, including sanctions, AML, and PEP registries, with match confidence scoring and hydrated match profiles.

Continuous monitoring

Receive proactive notifications through Sync Hub when a monitoring case is created or alert lists change. Enable or disable ongoing monitoring for a party you already screened.

Remediation from your app

Record risk decisions (for example, FALSE_POSITIVE, TRUE_POSITIVE) from your consuming app and sync them to ComplyAdvantage Mesh without opening the ComplyAdvantage Mesh dashboard.

Mute false positives

Suppress recurring alerts for profiles remediated as false positives so coincidental matches do not re-surface during ongoing monitoring.

Detailed risk profiles

Screening results include vendor-specific AML data such as risk categories, PEP positions, sanction list entries, adverse media, and watchlist matches.

​
Supported operations

The ComplyAdvantage Connector supports the following operations from the Grand Central Party Lifecycle Unified API:

​
Screening response

The screening response includes status, case references, screening case reference, hydrated screening alerts, match scores when the vendor provides them, and vendor-specific AML data. For field-level detail, see Reference.

​
Monitoring events (Sync Hub)

When ComplyAdvantage Mesh raises a monitoring event, the inbound connector hydrates alert detail where required and publishes unified monitoring events to Sync Hub. Downstream consumers subscribe to Sync Hub to receive updates. You do not need to poll ComplyAdvantage Mesh directly. Published events use the standard Grand Central envelope. The data payload aligns with the customer-screening-response schema where fields overlap. CASE_CREATED events may not include hydrated screeningAlerts. CASE_ALERT_LIST_UPDATED events include enriched alert and risk profile detail.
For how Sync Hub distributes events to multiple consumers, see Sync Hub overview.
For Party Lifecycle Unified API operations, events, and error mappings, see Reference.