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.

dembli for fintechs and payment institutions

A fintech onboards customers inside its own app, in seconds, and answers to the same rules as a bank. dembli fits in as an API: every call returns sourced facts and an explanation your team can review.

What dembli solves

  1. Screening at onboarding, inside your flow

    One call per customer compares name, date of birth, countries and documents with sanctions, debarment and politically exposed person lists, and returns the classification, the signals and a receipt.

    Products used: Screening PEP

  2. Business customers: registration, partners and control

    The company's official registration, its partners and administrators, the ownership chain and the derived beneficial owners, each link with its source.

    Products used: KYB Ownership

  3. The whole book, not only new customers

    Batches of up to 10,000 subjects per file for the existing book, then continuous monitoring, with each material change reported once by webhook.

    Products used: Screening Monitoring

  4. Review under rules your team writes

    A review queue with configurable four-eyes and deterministic rules, written by your team, to dismiss known false positives. No rule ever confirms a match, and a person can revisit what a rule decided.

    Products used: Review

  5. Proof of what was checked

    Every screening produces a receipt with the versions and publications it read, signed and verifiable outside the platform.

    Products used: Evidence

Rules that call for these steps

dembli delivers facts and proof for these steps; complying with the rule remains the institution's responsibility.

  • FATF Recommendations (Rec. 10) · Circular BCB nº 3.978/2020, art. 16

    Customer identification at onboarding

    Require verifying and validating the customer's identification against public and independent databases; dembli supplies official registrations, the worldwide LEI base and lists with each fact's source.

    Official text
  • FATF Recommendations (Rec. 12) · Circular BCB nº 3.978/2020, art. 19

    Politically exposed persons

    Require checking whether the customer is a politically exposed person, family member or close associate; dembli shows each public position with the official register that publishes it and the jurisdiction's exposure window.

    Official text
  • FATF Recommendations (Rec. 10) · Lei nº 9.613/1998, art. 10, I

    Up-to-date customer records and ongoing monitoring

    Require identifying customers and keeping their records up to date throughout the relationship; dembli alerts by webhook when a monitored customer's official registration, tax debt, LEI or list status changes.

    Official text
  • FATF Recommendations (Rec. 6) · Lei nº 13.810/2019, arts. 2º, V, and 9º

    Asset freezes without delay

    Require asset freezes ordered by the UN Security Council to be applied without delay; dembli checks the Council's list and major international sanctions lists every five minutes.

    Official text
  • FATF Recommendations (Rec. 15) · OFAC, EU and UK lists

    Virtual assets and sanctioned wallets

    Require screening parties and virtual-asset wallet addresses against official designations; dembli matches wallet addresses published by OFAC, the EU and the UK exactly.

    Official text

The workflow

  1. Integrate in the sandbox

    A test key reads only invented data, including a subject for every match classification and simulated failures, so you can build the handling of each case.

  2. Check at onboarding

    Screening and, for business customers, the registration and ownership chain, called from your backend with idempotency keys.

  3. Review

    Matches go to your team's queue, under the rules and approvals your policy sets.

  4. Monitor

    Each accepted customer enters monitoring; changes arrive through signed webhooks, with retries.

Through the dembli API, with a public OpenAPI contract, and the console for the review team. Accepting or declining a customer is always the fintech's decision.

Talk to sales

Integrate against the sandbox of invented data and test the screening profile on your book before you go live.

Talk to sales