UNIFINplatform

Solution

Unifin National AML/CFT

A national AML/CFT regime needs cooperation without uncontrolled disclosure.
A case opens by invitation with a visibility level and a declared projection.
Every exchange and disclosure is logged; the regime builds no common database.

  • Case registry with envelopes
  • Selective exposure by role
  • Ready for pilot
All solutions

Live screens from the product terminals

Red flags dashboard screen Red flags dashboard screen AML case registry screen AML case registry screen Case share wizard screen
Demo Unifin National AML/CFT
Case registry
Case registry: envelopes, parties and expiry dates
Case registry
Case registry: envelopes, parties and expiry dates

This is an interface demonstration: the real solution will differ in colours and content for a specific project.

Functions at a glance

Business functions at a glance

From the case registry to supervisory dashboards.

Case registry
Runs cases with subjects, operations and urgency
Duplicates surface before a case opens
Access envelopes
Declares parties, purpose and disclosure expiry
Data opens only under the declared rules
Share wizard
Shows the projection and confirms with second eyes
The counterpart gets exactly the declared scope
Red flag triggers
Activates triggers with thresholds via four eyes
Suspicion rises without manual hunting
Matches board
Pairs subjects on irreversible markers
Cross-organisation links become visible
Investigation workspace
Runs the timeline, links and decisions of a case
The team works in one place
Supervisory dashboards
Shows volumes, statuses and trigger statistics
The supervisor sees the picture without one database

What runs today

The national regime circuit, ready for pilot

A national regime without a common database: the live parts.

Intake

Cases enter the national regime by intake rules.

Envelopes

Access envelopes bound every disclosure.

Matches

Red flags and matches support the investigation.

Workspace

The investigation workspace keeps the case together.

Journal

The access journal logs every exchange.

Roadmap

The pilot rollout is the next step.

Solution description

Capabilities and overview

Key features

  • Case registry with subjects, operations and urgency
  • Access envelopes: parties, purpose and disclosure expiry
  • Share wizard with the projection and second-eyes confirmation
  • Red flag triggers with thresholds and four-eyes activation
  • Matches board on irreversible markers
  • Investigation workspace: timeline, links and decisions
  • Supervisory dashboards: volumes, statuses, trigger statistics
  • Access journal for every exchange and disclosure
  • Selective disclosure by role and declared purpose
  • The regime builds no common database between organisations
  • Reference data and roles prepared by configuration
  • Deployment: by configuration, within the UniFin platform

Product overview

Unifin National AML/CFT is the UniFin platform national information-sharing platform for the financial intelligence unit and reporting entities.

The platform runs cases, access envelopes, red flags, matches and investigation workspaces.

A case opens by invitation with a visibility level and a declared projection, and each party confirms steps with second eyes.

Every exchange and disclosure is recorded in the journal for review, while no common database is built between organisations.

The solution runs within the UniFin platform without changes to the systems of the participants.

What it delivers

What the solution delivers

Case registry

Cases are usually accepted by e-mail, and duplicates surface during an investigation. The solution runs a registry with a source, subjects, operations and urgency. With the solution duplicates are checked before opening, and a case is not run twice. In setup the case history and related filings are visible, and the types and priorities come as reference data.

Access envelopes

Disclosure usually goes unrecorded, and the scope of what was shared is reconstructed from memory. The solution declares the parties, the purpose and the envelope expiry before data moves. With the solution data is disclosed by the rules, and inspection questions are answered. In setup the envelope composition and the terms are visible, and the access levels are set in configuration.

Share wizard

Data is usually shared by letter, and the recipient sees more than needed. The solution shows the projection for the counterpart and confirms the step with second eyes. With the solution the scope of sharing is controlled, and excess disclosure is not argued about. In setup the sharing decisions and the invitation history are visible, and the sharing rules are configured per segment.

Red flag triggers

Suspicious patterns are usually hunted by hand and found late. The solution activates triggers with thresholds through four eyes and versions the library. With the solution it is visible what fires and how often, and the sensitivity is tuned. In setup the trigger history and threshold changes are visible, and the triggers come from the setup.

Matches board

Matches across organisations are usually hunted by letters, and time goes into comparing lists. The solution pairs cases and subjects on irreversible markers. With the solution cross-organisation links are visible without exposing the data. In setup the markers are visible, a subject opens only with disclosure rights, and the matching rules are part of the configuration.

Investigation workspace

An investigation usually lives in folders and e-mail, and the timeline is rebuilt by hand. The solution runs the timeline, subjects, links, decisions and attachments in one place. With the solution supervisory requests are answered without reassembling the case. In setup decisions and attachments for every case are visible, and the team roles are set in configuration.

Supervisory dashboards

Supervision usually receives statistics with a delay and cannot see the service levels of entities. The solution collects volumes, statuses, service levels and red flag statistics. With the solution the national picture is visible without one common database. In setup the breakdown by organisation and period is visible, and the dashboard composition comes as reference data.

Coverage

What it covers

The prototype covers entities, the FIU and the supervisor on one suite.

Case intake

A record with a source, subjects and urgency; duplicate check before opening.

Access envelopes

Declared parties, purpose and expiry; the platform enforces them on every read.

Sharing decisions

Invite, accept, decline with a reason: every step is recorded.

Red flags

Trigger library with thresholds and versioning; activation through four eyes.

Matches

Matching against cross-organisation cases and registers with marker preservation.

Investigation workspace

Timeline, subjects, links, decisions and attachments for the assigned team.

Supervisory dashboards

Volumes, statuses, agreements, red flag statistics and service levels.

Access journal

Every access to disclosed data with by whom, when and why.

Stand

Screens of the solution

The case registry, the share wizard and the red flags dashboard.

AML case registry screen
Case registry: envelopes, parties and expiry dates
Case share wizard screen
Share wizard: declared projection of data for the counterpart
Red flags dashboard screen
Red flags dashboard: triggers, thresholds and statistics

How it works

From a trigger to the supervisory picture in five steps

The path of the case: trigger, case, envelope, investigation and statistics.

  1. 1

    A red flag fires

    A signal passes the threshold; the alert reaches the operator.

  2. 2

    The case opens

    The entity records the case; the envelope declares who sees what.

  3. 3

    The case is shared

    The wizard shows the projection; confirmation publishes the case.

  4. 4

    The investigation runs

    Markers match; the subject opens only for the authorised role.

  5. 5

    The picture assembles

    Dashboards show volumes, statuses and red flag statistics.

Industries

Industries it serves

The suite serves the financial intelligence unit, banks, exchange houses and other reporting entities, and the supervisor of the national regime.

Regulator / supervisor

Surveillance evidence, market analytics and reporting built from live transaction data.

Architecture

Architecture and access

The platform connects organisations without merging their data stores: access envelopes carry the rights, journals carry the evidence.

Data stays with the owner

Each organisation keeps its store; the platform carries the case and the envelope.

Privacy by construction

Irreversible markers for matching, declared projections for sharing, expiry dates on disclosure.

Evidence for inspection

Access, disclosure and sharing journals are append-only with export under watermark.

Platform services

Identity, roles and documents come from the platform; the suite adds registry and matching.

AI layer

The AI layer drafts match explanations and links related filings; people approve every step.

Architecture scheme The same architecture as a standalone page. Open the diagram separately

Readiness

Ready today, next in line

The interactive prototype is complete; waves start after approval.

Ready today

  • Concept and end-to-end scenarios for the national regime
  • Interactive screen prototype: operation forms and scenarios
  • Implementation estimates and the pilot frame

Next in line

  • Wave W1: case registry, envelopes and sharing
  • Wave W2: red flags, matching and the investigation workspace
  • Wave W3: dashboards and the regulator channel

Releases

Release history

The suite is designed in 2026 for the national regime and joins the platform release waves with the first pilot.

2026 Q3

  • Concept, scenarios and the interactive screen prototype.

2026 Q4

  • Planned: wave W1 with the case registry and envelopes (plan).

Detailed description

Detailed description

The envelope model, the matching design and the delivery frame.

How the suite is assembled

Channels and clients
FIX 4.2 / 4.4 / 5.0, REST with mTLS, SFTP files, web portals
Edge and access
API gateway with 126 routes, Keycloak single sign-on, WAF and CSP
Platform core services
case services matching engine notification-ms regulator channel AI agentic layer Services of the suite on the shared platform core
Data and events
PostgreSQL 17 per service, Redis 7, RabbitMQ 3.13 quorum queues, transactional outbox
Results and reporting
Portals, reports, regulator and partner channels

Technology stack

Runtime and backend: Java 21 (LTS), Spring Boot 3.5.16, Spring Cloud 2025.0.3, Gradle, Flyway 10.15.

Data: PostgreSQL 17 per service, Redis 7 with Sentinel, RabbitMQ 3.13 quorum queues, transactional outbox and DLQ replay.

Portals: Next.js 16.3.3, React 19, TypeScript 5; OpenTelemetry 1.31 to Jaeger.

Delivery: Kubernetes and Helm, Vault secrets, Prometheus and Grafana, Docker Compose for pilots.

Visualisation: Apache Superset 4 and ECharts 5 for dashboards and charts, Grafana for operations panels, Mermaid for documentation schemes and the portal diagrams.

Envelope model

  • An access envelope declares the parties, the purpose and the expiry of every share.
  • Data classes: corporate facts, personal data, markers; the envelope opens them selectively.
  • The platform enforces the envelope on every read, not only at sharing time.
  • Expired envelopes close automatically; extensions require a new decision with a reason.

Matching design

  • Irreversible markers for subjects and accounts: matching works without raw identifiers.
  • Cross-organisation matches open as hints; the disclosed view needs rights and a basis.
  • Match quality reports: duplicates prevented, value of resolved matches.
  • The matching engine version is recorded with every match for later review.

Delivery frame

  • The interactive prototype is the acceptance baseline for the build waves.
  • Pilot onboarding: two entities, one case type, real data in a closed suite.
  • Regulator side included: packages, receipts and the supervisory dashboards.
  • Source code handover as an option with a separate fee, with the envelope and matching design documented.

Architecture

  • Built from the platform core: the case services, the matching engine, notification-ms and the regulator channel.
  • The suite works through platform contracts: one register of record, no shadow copies of the data.
  • Scaling adds nodes, not rewrites: stateful services grow with Patroni, RabbitMQ and Redis clusters.

Integrations and access

  • OpenAPI for every service: 978 documented endpoints behind 126 gateway routes, plus webhooks and SFTP where partners need files.
  • Single sign-on: Keycloak 26.1, OIDC and JWT, roles, MFA and API keys with quotas.
  • Evidence by default: the audit journal, idempotency keys on writes and a record for every disclosure.
Detailed description

Leave your contacts to open the detailed description and download the PDF with architecture, cases and delivery details.

Run the national regime on a pilot stand

Bring two organisations and one case: we will run the envelope, the sharing and the investigation on the prototype stand.