Skip to content
Platform

One record, from offer to handover.

When someone asks to see the file, the answer is an export, the same day, without anyone rebuilding it. Every regulated transaction has the same spine: establish the party, establish where the money came from, score the risk, evidence the decision. Built once, shaped per sector.

The record is the product

Every other feature is a way of adding to it or reading from it.

The claim is not screening, onboarding or document storage — each of those is a commodity. It is that the deal and the diligence share one object, so the file is never assembled retrospectively.

How it works

Compliance and payments, on one record

Compliance

Onboarding and CDD evidence captured against the transaction rather than into a folder. Screening results returned by your provider, recorded with the reviewer decision alongside. Your own risk matrix, applied and explained line by line. Report content assembled in the structure goAML requires.

OnboardingScreeningRisk scoringgoAML-ready file
Compliance →

Payments Orchestration

The evidence pack that source-of-funds work actually consists of, mapped to what each counterparty demands. The firm's payment instruction and the documents attached to it. What the file expected against what the firm recorded as received, with the gap flagged before completion rather than at audit.

Evidence packCounterparty mappingInstruction recordReconciliation
Payments Orchestration →
Three layers

One core, thin verticals

Layer 03 · Expansion The pattern, repeated

Each a thin vertical on a core that already exists.

Corporate servicesWealthLegal and immigrationVASPs
Layer 02 · Vertical Real estate

The first wrapper, and the proof the core is real.

TransactHandoverPortfolio
Layer 01 · Core Compliance primitives

Sector-agnostic by construction, UAE-native by configuration.

IdentityProvenanceScreeningRiskRecordConnect
The core

What switches on

01

Identity

Document and corporate identity evidence captured against the transaction.

02

Provenance

Source of funds and source of wealth, with the documentary chain attached.

03

Screening

Results returned by your provider, recorded with the reviewer decision alongside.

04

Risk

Your matrix, applied and explained line by line.

05

Record

Immutable history, and an export in a form an auditor or bank accepts.

06

Connect

The providers you already hold relationships with.

Product

What the platform does

Modules 8
Capabilities 3
Record One file per client
Ref Feature Part of What it does Output
F-01 Identity and KYC orchestration Core Runs the identity check inside the firm's own flow and captures the documents and their sources against the client file. Documents
F-02 AML risk scoring Core Scores the client factor by factor against a nine-category matrix calibrated to the DNFBP taxonomy. Score
F-03 PEP and sanctions screening Core Passes the client to the firm's screening provider and brings the result back into the file with the list and the date. Screening result
F-04 Source of wealth and source of funds Core Captures the declaration and the evidence it has to be matched against, structured at onboarding rather than assembled at closing. Evidence file
F-05 Case console and audit log Core One place for the MLRO to review, approve, escalate or decline, with every action recorded under a named person and a timestamp. Decision
F-06 Provider routing and milestone tracking Payments orchestration Passes the request to the provider the firm has contracted and records the milestones that come back against the deal. Milestones
F-07 API, webhooks and firm branding Shared architecture Embeds the flow in the firm's own front end, in the firm's branding, and returns events and a file reference by callback. Events
F-08 Blockchain analytics Provider-supplied Where funds start as digital assets, brings the wallet-to-fiat analysis into the same file as the rest of the evidence. Wallet pathway
The interface

Compliance, as the officer sees it

A click-through of the product: the decision queue, the file list, and a single file from offer to handover with its screening, documents and audit trail on it.

Proposed interface, shown with sample data. Every name, reference and figure in it is fictional.

Integration

Three ways a firm can connect

Each mode reads and writes the same record and the same audit log. The mode changes where the investor sees the form, not what is kept.

Tell us which one fits your front end and we will scope it with you.

01

Embedded

A widget inside the firm's own investor flow, in the firm's branding. The lowest integration effort for a firm that already has a web front end.

02

Hosted handoff

The investor is handed to a firm-branded page and returned by callback, with the decision the firm recorded and the file reference.

03

Direct API

The firm's own front end calls the API and receives webhooks. Suited to platforms, lenders and funds with engineering teams.

Tell us about a deal that stalled

Walk us through one cross-border purchase — where it got stuck, what was asked for, and what it took to answer. We will show you what that transaction looks like as a single record, with the gaps marked and each one named.