One record, from offer to handover.
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.
Three capabilities 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.
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.
Provider Network
Firms hold their own provider relationships. The software organises one file, maps it to each provider's requirements, tracks what was sent and when, and records the outcome against the transaction.
One core, thin verticals
Each a thin vertical on a core that already exists.
The first wrapper, and the proof the core is real.
Sector-agnostic by construction, UAE-native by configuration.
What switches on
Identity
Document and corporate identity evidence captured against the transaction.
Provenance
Source of funds and source of wealth, with the documentary chain attached.
Screening
Results returned by your provider, recorded with the reviewer decision alongside.
Risk
Your matrix, applied and explained line by line.
Record
Immutable history, and an export in a form an auditor or bank accepts.
Connect
The providers you already hold relationships with.
Six stages, one submission
The investor submits once. The firm reuses that file on the firm's later transactions.
The obligation does not move: the firm's compliance function decides, against thresholds the firm sets. The software records the work and evidences it.
The investor engages the firm. The firm keeps the client, the brand and the deal record throughout.
Identity checks run in the firm's own flow, in the firm's branding.
Results returned by the firm's screening provider are brought into the firm's console, with a risk score alongside.
The firm approves, escalates or declines. The decision is recorded against a named person and a timestamp.
The investor instructs their own bank. Funds move from the investor's own account to a regulated provider.
The outcome is written back to the deal record, and the file is exportable.
What the platform does
| 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 |
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.
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.
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.
Direct API
The firm's own front end calls the API and receives webhooks. Suited to platforms, lenders and funds with engineering teams.
Talk to us about implementing Wasila
Compliance, payments orchestration, or both. A member of the team will take you through the integration modes and what each would mean for your firm.