Skip to content

Get Started ​

KMaker is an anti-money-laundering (AML) compliance platform for financial institutions. It covers watchlist and sanctions screening, alert triage and continuous screening, case management, and regulatory reporting to the Financial Intelligence Unit.

This documentation describes how to operate the platform and how to integrate with it programmatically.

Platform areas ​

The platform is organised around a small number of record types. Understanding them is the fastest route to understanding the product:

  • Screening — checking a person or organisation against watchlists, sanctions lists, and politically exposed person (PEP) data. Run on demand from Manual Screening, or continuously against a monitored population.
  • Alerts — records raised when screening or transaction monitoring produces a potential match or a rule breach that a reviewer must assess.
  • Compliance cases — escalation containers. An alert that cannot be resolved at first review is escalated into a case, where it carries a checklist, narrative, evidence, and an assigned reviewer.
  • Decisions — the recorded outcome of a review, produced by the decision rules configured for your institution.
  • FIU reports — suspicious transaction reports (STR) and cash transaction reports (CTR), together with their amendments and submission groups, for reporting to the regulator.

How to use these docs ​

  • Products — feature-level guides for operating the platform, starting with Manual Screening.
  • API — the integration surface: webhook events, and the REST endpoints.
  • Webhooks — the events KMaker emits, with a per-event payload schema.

Integration path ​

If you are integrating rather than operating the platform, start with the webhooks overview. Webhook events are the recommended integration point for AML workflows, because every state change a downstream system cares about emits an event with a versioned payload schema.

The Events reference lists every event type currently emitted, grouped by entity, with the JSON Schema for its payload and an example payload.