EN
Appearance

To remember this theme on future pages, allow saved preferences. Cookie preferences

Could not save. Check that your browser allows cookies and try again.

Talk to sales
MenuClose
Talk to sales

Preferences

LanguageEnglish
AppearanceSystem
Appearance

To remember this theme on future pages, allow saved preferences. Cookie preferences

Could not save. Check that your browser allows cookies and try again.

Validation

Test before you sign

Your compliance team will have to tell the auditor how it tested its screening tool, and your correspondent bank will ask when. With dembli, the test runs on your own book, every match shows its work and every answer can be proved years later.

01 · Your sample

Measure it on your book. Not on a demo we picked.

Bring a sample of your customers with the outcome you expect on each line. dembli tells you, line by line, what it found and what it did not, and your team has its answer to when and how it tested the tool, as the Wolfsberg questionnaire asks.

  • Up to 10,000 subjects a batch

    A file through the API or the console, one person or company a line. Each line can say whom you expect to find, or that you expect no one.

  • Five outcomes per line

    Found, withheld by the profile, missed, false alert or cleared. You see the tool's hits and its errors, not just a percentage.

  • Tune and run again

    The analyst changes the profile's lists and thresholds in the console and runs the same batch, until the profile answers as your policy requires.

  • Versioned profiles

    Every profile change is a new version, and every screening records the version that produced it. The auditor sees which configuration held on each date.

02 · Explanation

Every match shows its work. Nobody has to trust a black box.

An analyst decides better when they see why a name was flagged, and the regulator expects the institution to be able to explain the tool it uses.

  • Signals with weight and effect

    Name, date, country and document, each with its weight, its effect and a sentence that explains it. Contradictions are shown, not hidden.

  • Why the list names the party

    The reason for the designation in the publisher's words and the address of the official list, beside every match.

  • The listed party's full facts

    The dates of birth, nationalities and documents the publisher printed, whole, to compare with what your customer gave you.

  • What was left out, and why

    Every candidate assessed and not reported is named, with the reason: below the threshold, contradicted, outside the filtered lists or with its designation withdrawn.

03 · Audit

Prove what you checked, years later. With the answer given that day.

In an inspection, the question is not what the list says today. It is what it said when the customer was onboarded, and what your team did about it.

  • Replay as of any date

    Pick a date and the screening is replayed with that day's lists, including designations withdrawn since.

  • A signed receipt you verify yourself

    Every screening produces a receipt you can download digitally signed at any time. Your team or the auditor verifies it outside the platform, with dembli's public key.

  • Every fact back to the official file

    Each publication's file is kept and sealed with a fingerprint before it is read, and every fact in the answer points to the record, the publication and the source file.

  • Decisions with author and history

    Every analyst decision on a match keeps its note, author and time. A new decision does not erase the earlier one.

04 · Changes

The matcher never changes in the dark. Every version is measured before it ships.

  • The version on the receipt

    The receipt records the versions of the matcher and of the lists that produced the answer, so a change never rewrites the past.

  • Measured before it ships

    A new matcher configuration ships only with a reference baseline measured under it. The evaluation fails a version that loses more than a percentage point of accuracy or brings 5% more candidates who are not the person sought.

  • Same query, same answer

    Candidate retrieval is deterministic: the same index and the same query bring the same candidates, in the same order.

  • Changes announced

    The API contract is versioned, and its changelog is written in Portuguese, Spanish and English.

05 · Transparency

Performance in plain sight. On a public page, no password.

The status page shows the last thirty days' availability, the p50, p95 and p99 latency of requests, each source's last update and the matcher baseline in use. Your vendor oversight does not depend on asking for a report.

dembli delivers facts with their source, explained matches and proof of what was checked. Accepting, declining or reporting stays your institution's decision.

Bring your sample

Talk to sales and bring a sample of your book with the outcome you expect on each line: we run the test with your team.

Talk to sales