Understand your customers and the connections around them. Monitor activity in context and spot emerging risks.
Used by financial institutions including
source: Address Document
Checks
Evidence
Passport
№EXAMPLE-482JPNExtracted Fields
Full Name
Haruka Tanaka
Date Of Birth
1985-06-12
source step: identification_document
Face match
Match
ID document face
Liveness frame
Liveness (selfie)
Pass| Field | Claimed | Document | Match |
|---|---|---|---|
| Full Name | Haruka Tanaka | Haruka Tanaka | Match |
| Date Of Birth | 1985-06-12 | 1985-06-12 | Match |
Verification contract v1.0 · provider Dossiers · session ref KYC-00482 · completed 2026-01-14 09:08 UTC
Bring KYC and AML screening into the same customer review. Retain the evidence as the relationship develops.
Collect the right evidence, configure the stages, and route the results into your customer review.
Sanctions, watchlists, politically exposed persons, and adverse media. Review potential matches with the customer’s identity and source evidence in view.
A payment tells you what happened. The customer, device, account, and counterparty help you understand why it matters.
Five unrelated customers pay the same new endpoint from one device fingerprint. Each payment sits below the configured threshold. The shared connections give the reviewer a reason to look closer.
To IBAN CY·· 8841
Day 1 · 11:10
To IBAN CY·· 8841
Day 2 · 11:17
To IBAN CY·· 8841
Day 3 · 11:24
To IBAN CY·· 8841
Day 4 · 11:31
To IBAN CY·· 8841
Day 5 · 11:38
Bring transaction monitoring, device monitoring, and payment channel monitoring together. Assess payments alongside customer history, device activity, and the channels involved.
Explore monitoringFollow the records behind an alert. Bring together the contributing activity, source evidence, and review history before deciding what happens next.
Explore investigationsTurn a risk scenario into an explicit rule. Configure the conditions and see how they evaluate against a sample payment before reviewing the response.
Large payment after a security change
Outbound payment close to the balance shortly after a password change.
Transaction> Created
Read the AI-assisted assessment alongside the customer, account, counterparty, and business records behind it. Keep the evidence in view as your team decides what happens next.
Current stage
No active watchlist matches.
No high-risk matches found
Bring customer records, payment activity, and verification evidence from the systems you already use.
Integrations and data flowUse the rule builder to define detection conditions and test changes. Set review responsibilities and access around your institution’s requirements.
Explore the rule builderWork through hosting, network boundaries, data handling, and operational responsibilities with our team.
Security and deploymentYes. Bring customer information and verification results through the API, and connect a supported screening provider. We’ll review the required data, provider connection, and responsibilities with your team.
No. Existing customer records can provide the starting point for screening or monitoring. We’ll help you identify the workflow and integration scope that fit your requirements.
Access depends on the configured tools and permissions. Dossiers Agents can read selected customer, entity, account, and counterparty records. Additional workflows depend on the integrations you configure, with approval controls for connected write tools.
For a pending transaction, a configured rule can return a blocked outcome in Dossiers OS. Your payment system must use that outcome to enforce a hold or rejection. We’ll walk through that integration during the demo.
We’ll explore the customer or activity workflow that matters to your institution, show the relevant capabilities, and discuss your data, review process, and deployment requirements.
Bring your workflow. Explore how Dossiers OS connects the customers, activity, and evidence your team relies on.