AML, KYC & fraud screening
as a simple API.

You send

first_name, last_name, date_of_birth, plus optional email, id_number and country.

You get back

A verified / review / rejected status with a 0–100 confidence score and the result of every individual check (age validity, email format, required fields, ID presence).

When to use it

Use at account opening to catch incomplete or implausible identities before you spend money on deeper checks.

You send

first_name, last_name, date_of_birth, optional email, country and id_number. The customer is automatically saved to your workspace.

You get back

A single approve / review / reject decision plus the underlying identity result, AML screening reference with match count, and a persisted risk score. Also returns a customer_reference you can reuse in every later call.

When to use it

Use as your one-call onboarding endpoint — it runs the whole compliance chain and gives you a decision your signup flow can act on directly.

You send

name, plus optional date_of_birth, country, list_types to narrow the search, and persist_customer to save the subject.

You get back

Status (clear / potential_match), 0–100 risk score, match count, a per-list breakdown, and the full evidence for every hit: matched name, similarity %, list, source and program.

When to use it

Use for periodic re-screening of your customer base or as a broader alternative to a sanctions-only check.

You send

name, plus optional date_of_birth and country for corroboration.

You get back

An is_pep boolean, match details with the political role (e.g. Cabinet Minister, Central Bank Governor), similarity score and risk score.

When to use it

Use when regulation requires enhanced due diligence for public officials and their associates.

You send

name, plus optional date_of_birth (nudges the score up or down when it corroborates or contradicts) and country.

You get back

Clear or potential_match status with every matching sanctions entry: source list, program (e.g. RUSSIA-EO14024), similarity % and derived risk level.

When to use it

Use before any payment, payout or onboarding where dealing with a sanctioned party would be a breach.

You send

amount and currency, plus optional counterparty name/country/account, direction, channel and a customer_reference to build velocity history.

You get back

A pass / review recommendation with the exact rules triggered — large_amount, possible_structuring, high_risk_country, velocity_count, velocity_amount — plus a risk score. Flagged transactions are stored for your case team.

When to use it

Wire into your payment flow to catch smurfing, unusual volumes and high-risk corridors in real time.

You send

Any of: email, ip_address, ip_country, billing_country, device_id, amount, recent_attempts.

You get back

A fraud score 0–100, the list of signals fired (disposable_email, geo_mismatch, high_risk_geo, velocity…) and a decision: accept, review or decline.

When to use it

Use at checkout or signup to stop obvious fraud patterns before they cost you a chargeback.

You send

Boolean/numeric factors: sanctions_hit, pep_hit, adverse_media, country, document_failed, identity_failed, flagged_transactions, inherent_risk. Pass a customer_reference to persist the score.

You get back

A 0–100 score, a low/medium/high/critical band, and the exact points contributed by each factor — fully explainable to auditors.

When to use it

Use to combine results from the other endpoints into one number that drives your risk-based approach.

You send

type (passport, national_id, drivers_license…), document_number, country and expiry_date.

You get back

A verified / review / rejected status, an authenticity score, and per-check results including expiry and near-expiry warnings. Linked to the customer record when a reference is supplied.

When to use it

Use alongside identity verification to make sure the document backing an identity is valid and current.

You send

A customer_reference, optional monitored_types, a frequency (daily/weekly/monthly) and an optional webhook_url.

You get back

A subscription that automatically re-screens the customer on schedule. New matches fire a signed monitoring.match webhook to your server, and every run is visible in your dashboard. List, run-now and unenroll endpoints included.

When to use it

Use so that a customer who was clean at onboarding doesn’t stay unnoticed when they appear on a list next month.