> ## Documentation Index
> Fetch the complete documentation index at: https://agenticbanking.backbase.io/llms.txt
> Use this file to discover all available pages before exploring further.

# Overview

> Streamline AML screening and monitoring with the ComplyAdvantage Connector

export const VendorApiVersionTag = ({versions, label = "Supports"}) => {
  useEffect(() => {
    if (!versions || versions.length === 0) {
      return undefined;
    }
    const findAndSegmentStart = (reference, target) => {
      let i = 0;
      while (i < reference.length && i < target.length && reference[i] === target[i]) {
        i += 1;
      }
      let start = i;
      while (start > 0 && (/[0-9.vR]/).test(target[start - 1])) {
        start -= 1;
      }
      return start;
    };
    const formatText = () => {
      const suffix = " operations";
      if (versions.length === 1) {
        return `${label} ${versions[0]}${suffix}`;
      }
      const [first, ...rest] = versions;
      const last = rest[rest.length - 1];
      const andStart = findAndSegmentStart(first, last);
      const lead = first.slice(0, andStart);
      if (versions.length === 2) {
        return `${label} ${first} and ${last.slice(andStart)}${suffix}`;
      }
      const stems = versions.map(version => version.slice(andStart));
      return `${label} ${lead}${stems.slice(0, -1).join(", ")}, and ${stems[stems.length - 1]}${suffix}`;
    };
    const text = formatText();
    const mountCallout = () => {
      const titleRow = document.querySelector("#page-title")?.parentElement;
      if (!titleRow) {
        return null;
      }
      let callout = titleRow.querySelector("[data-vendor-api-version-callout='true']");
      if (!callout) {
        callout = document.createElement("div");
        callout.dataset.vendorApiVersionCallout = "true";
        callout.className = "vendor-api-version-callout vendor-api-version-callout--in-title";
        titleRow.appendChild(callout);
      }
      callout.replaceChildren();
      const textEl = document.createElement("span");
      textEl.className = "vendor-api-version-text";
      textEl.textContent = text;
      callout.appendChild(textEl);
      return callout;
    };
    let callout = mountCallout();
    if (callout) {
      return () => {
        callout?.remove();
      };
    }
    const observer = new MutationObserver(() => {
      callout = mountCallout();
      if (callout) {
        observer.disconnect();
      }
    });
    observer.observe(document.body, {
      childList: true,
      subtree: true
    });
    return () => {
      observer.disconnect();
      callout?.remove();
    };
  }, [versions, label]);
  return null;
};

export const vendorApiVersions = ["ComplyAdvantage Mesh API v2.0"];

<VendorApiVersionTag versions={vendorApiVersions} />

The ComplyAdvantage Connector integrates with [ComplyAdvantage](https://complyadvantage.com/) 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

<CardGroup cols={2}>
  <Card title="Real-time verification" icon="shield-check">
    Instant screening against watchlists, including sanctions, AML, and PEP registries, with match confidence scoring and hydrated match profiles.
  </Card>

  <Card title="Continuous monitoring" icon="alarm-exclamation">
    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.
  </Card>

  <Card title="Remediation from your app" icon="user-check">
    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.
  </Card>

  <Card title="Mute false positives" icon="volume-xmark">
    Suppress recurring alerts for profiles remediated as false positives so coincidental matches do not re-surface during ongoing monitoring.
  </Card>

  <Card title="Detailed risk profiles" icon="magnifying-glass">
    Screening results include vendor-specific AML data such as risk categories, PEP positions, sanction list entries, adverse media, and watchlist matches.
  </Card>
</CardGroup>

***

## Supported operations

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

| Operation                               | Endpoint                                                                        |
| :-------------------------------------- | :------------------------------------------------------------------------------ |
| Screen customers                        | `POST {partyLifecycleBaseURL}/screens/customer`                                 |
| Configure party monitoring              | `POST {partyLifecycleBaseURL}/customer-screening/config-monitoring`             |
| Record screening disposition            | `POST {partyLifecycleBaseURL}/screening-assessment/match-profiles/dispositions` |
| Suppress screening match profile (mute) | `POST {partyLifecycleBaseURL}/screening-assessment/match-profiles/suppression`  |

### 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](/connectors/kyc-kyb/complyadvantage/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.

| `data.eventType`          | When emitted                                          |
| :------------------------ | :---------------------------------------------------- |
| `CASE_CREATED`            | Mesh opens a customer monitoring case                 |
| `CASE_ALERT_LIST_UPDATED` | The alert list on an existing monitoring case changes |

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.

<Info>
  For how Sync Hub distributes events to multiple consumers, see [Sync Hub overview](/platform/sync-hub/overview).
</Info>

<Info>
  For Party Lifecycle Unified API operations, events, and error mappings, see [Reference](/connectors/kyc-kyb/complyadvantage/reference).
</Info>

***