Introducing Complead. One AI-native platform for financial crime compliance. Read the story
New Ready Integrations available Check the new integrations
Platform · Integration

Integrate with Everything

One REST API, webhooks and pre-built connectors, so screening, monitoring and case decisions reach your core banking, onboarding and payment systems without a rebuild.

15 min Sandbox to first live call
REST One API across products
Webhooks Every risk event
Idempotent Safe to retry
Why this matters

Compliance that does not reach the core system does not run

The best screening engine is inert if it cannot sit inside onboarding, hold a payment or update a customer record. Too many compliance tools are a separate screen an analyst logs into, disconnected from where the work happens. Complead is built to be embedded: one API, webhooks for every event, and connectors for the systems you already run.

A separate screen

Compliance lives in a tool nobody’s core system talks to.

Custom integrations

Each connection is bespoke, slow to build and slow to change.

No event model

Decisions do not flow back to the systems that need them.

How it works

Four steps, from sandbox to embedded

Scroll to advance
  1. Step 01 Get a sandbox key

    A sandbox key gives a full environment with test data, no procurement call needed.

  2. Step 02 Call the API

    One REST API covers screening, monitoring, cases and data, with idempotent calls.

  3. Step 03 Subscribe to events

    Webhooks push every risk event to your systems: alerts, escalations, decisions.

  4. Step 04 Connect your systems

    Pre-built connectors link core banking, onboarding and payment platforms.

complead / sandbox
  • sandboxactive
  • test dataloaded
  • keysissued
complead / call
  • POST/screening/search
  • OK200
  • ms148
  • idempotent
complead / subscribe
  • events subscribed6
  • alert, escalation,decision
  • delivered99.98%
complead / connect
  • core bankingconnected
  • onboardinglive
  • paymentsmapped
Sandbox
Call
Subscribe
Connect
Capabilities

What the product actually does

01

One REST API

Screening, monitoring, cases and data through one interface.

02

Webhooks

Every risk event pushed as it happens.

03

Idempotent calls

Safe to retry, no duplicate actions.

04

Pre-built connectors

Core banking, onboarding and payment platforms.

05

Sandbox

A full test environment in minutes.

06

Delivery logs

Every call and event logged, replayable.

Find your stack

Six categories, one ingestion layer. Filter by the part of your stack you need to connect, or search for a system by name.

CRM and business systems HubSpot

The screening results and case outcomes for the contact record.

CRM and business systems Salesforce

When accounts are synchronized in, the risk status is written back to your objects.

CRM and business systems SAP

Master data for the vendor and the counterparty are checked when the SAP process is carried out.

Data and watchlists LexisNexis

According to one of its match records, LexisNexis gives information regarding sanctions, PEPs, and adverse media.

Data and watchlists Dow Jones

The Dow Jones Risk and Compliance list is updated on the same schedule as the rest of them.

Data and watchlists LSEG Refinitiv

LSEG Refinitiv's World-Check data, deduplicated compared with those from your other providers.

Data and watchlists Moody's

Moody's contains the information about the entity and ownership of KYB and that concerning beneficial ownership.

Core banking Fimple

Includes native connection data relating to the customer, account and transactions.

Core banking Temenos

The core side has retained the mappings for Transact without making any changes.

Core banking Finastra

The account and payment data is handled either in batches or on an event-by-event basis.

Core banking Mambu

An API-based connection designed for cloud-native banks and lenders.

Core banking Thought Machine

The events which are recorded in the vault ledger are transmitted exactly as they are posted.

Core banking Oracle FLEXCUBE

Oracle FLEXCUBE makes it possible to read the tables either directly or by means of a scheduled extract.

Core banking Intertech

A connector intended for use with the Turkish banking system.

Warehouse and ingestion Snowflake

As far as Snowflake is concerned, look at the tables that you are already maintaining. Do not make a copy of them.

Warehouse and ingestion Google BigQuery

Scheduled reads using partition-aware incremental loads.

Warehouse and ingestion Databricks

Databricks offers curated tables from the lakehouse.

Warehouse and ingestion Amazon S3

Using Amazon S3, files can be uploaded to a bucket regardless of whether they are in a delimited or fixed width format.

Warehouse and ingestion Apache Kafka

The transaction events relating to Apache Kafka are taken from a topic for near-real-time monitoring.

Warehouse and ingestion PostgreSQL

This provides a read-only connection to an operational replica.

Warehouse and ingestion SQL Server

The read-only path is the same one in which SQL Server functions as the operational store.

KYC and identity Sumsub

The risk profile of the customer is updated on the basis of the verification results supplied by Sumsub.

KYC and identity Veriff

The identity check results from Veriff have been included in the record screening runs.

KYC and identity Onfido

Onfido's document and biometric verification procedure during the onboarding decision.

KYC and identity Persona

The results of the inquiry and the attributes that have been verified regarding risk scoring.

KYC and identity Socure

Identity fraud signals appear next to screening results.

KYC and identity Jumio

The verification data for Jumio has been matched to the customer profile.

KYC and identity iDenfy

For markets in which iDenfy is currently the leading company.

Workflow and comms Dynamics 365

With Dynamics 365, records are entered and compliance status is displayed.

Workflow and comms Zendesk

For the ticket, the compliance context is available and there is no need to carry out a hand-off.

Workflow and comms Slack

In the channel that the team actually monitors, there are high risk alerts.

Workflow and comms Microsoft Teams

Alert notifications and case handoffs for Microsoft Teams.

Workflow and comms Jira

In Jira, create a ticket when the remediation is the responsibility of another team.

Product tour

Three screens your team lives in

Access, managed

Keys per environment and scope, so production and sandbox stay separate.

  • Keys by environment
  • Scope per key
  • Rotate without downtime
complead / api-keys
  • prodkey
  • sandboxkey
  • scopes screening,cases

Events, delivered

Subscribed events, delivery status and a replay for anything missed.

  • Events subscribed
  • Delivery rate shown
  • Replay failed deliveries
complead / webhooks
  • events6
  • delivered99.98%
  • replayed2

Your systems, linked

Pre-built connectors with their status and field mapping.

  • Connectors and status
  • Field mapping per connector
  • Test before going live
complead / connectors
  • core bankinglive
  • onboardinglive
  • paymentsmapped
  • warehousetest

Four ways in

Most customers use two at once: a real-time API for onboarding decisions and a batch feed for everything historical.

REST API Onboarding checks, single screening calls, decisions inside the customer journey real time
Webhooks Alerts, case status and screening outcomes pushed back into your systems event driven
Batch file Portfolio rescreening, historical loads, legacy cores. Any delimited or fixed-width format scheduled
Direct connection Warehouses and databases where a copy is already maintained scheduled · streaming
What connects

Which systems connect, and how

Connectors and the API reach core banking, onboarding, payment and data platforms, over REST and webhooks.

Connector and API reference
Systems Core banking, onboarding, payments, data warehouse
Methods REST API and webhooks
Connectors Pre-built for common platforms
Delivery Logged and replayable
Runs on Fusion

One integration, every product

Because every product runs on Fusion, one integration reaches all of them. Add a module and it arrives through the same API and the same events, with no new integration to build.

This product Integrate with Everything REST API, webhooks, connectors
Connects Fusion engine Every product through one interface
You get One integration Add modules without re-integrating
Integration

One key, one API, events for the rest

Authenticate once, call any product, and subscribe to the events your systems need.

ISO 27001 SOC 2 Type II GDPR / KVKK EU UK TR regions
// one API across products
POST /v1/screening/search "name": "Aleksandr Volkov"
200 OK · idempotency-key respected
// subscribe to any risk event
PUT /v1/webhooks "events": ["alert.raised","case.escalated","payment.held"], "url": "https://you.example/risk-events"
Case study · Digital bank

A digital bank embedded compliance in onboarding in a week

Compliance had been a separate portal. Using one API and webhooks, screening ran inside the signup call and decisions flowed to the core system, with the first live call the same day as the sandbox key.

15 min Sandbox to first call
1 week To production
99.98% Event delivery
Read the case study
Compared with

What changes versus a bolt-on tool

Bolt-on tool Complead
Access Separate portal Embedded via API
Integration Bespoke per system One API, connectors
Events Polling or none Webhooks per event
Adding a module New integration Same interface
Time to first call Weeks 15 minutes
FAQ

Before you ask us

Is there one API or one per product?

One REST API covers screening, monitoring, cases and data. Adding a module uses the same interface.

How do decisions reach our systems?

Through webhooks. Every risk event, from an alert to a payment hold, is pushed as it happens.

Are calls safe to retry?

Yes. Calls are idempotent, so a retry does not create a duplicate action.

Do you have pre-built connectors?

Yes, for common core banking, onboarding and payment platforms, with field mapping.

How fast can we start?

A sandbox key gives a full environment in minutes, with the first live call typically the same day.

Where is our data stored?

You choose the region: EU, UK or Türkiye.

Testimonials

What compliance teams say

All case studies
We went from checking customers one by one to a single platform that screens more than 3,000 of them around the clock, so our analysts can finally focus on real risk.
Ulviyya Akhundzada Head of Compliance & Monitoring · Ateshgah Life
We moved from screening customers one by one to a unified platform where our analysts can focus on what actually matters.
Mariana Alexei Non Banking Financial Expert · Moldcell
We focus on real risks, not false positives, meeting our AML obligations and our customers' expectations.
Arda Akay Head of Compliance, Risk & Internal Control · BPN

Integrate against your own stack

Bring your systems. In 30 minutes you will make a live call from a sandbox and see an event reach your endpoint.

3,000+ Data sources checked
220+ Countries covered
15 min Always real-time data

Connects to the tools you already run