Platform · Risk engine
A weighted scoring model and visual rule builder that turn your risk appetite into versioned, testable, explainable logic, the same engine behind every KYC, KYB, AML, KYT, and Travel Rule decision.
Inside the engine
Rules read every signal the journey produced and write a decision, a band, or a branch, never a bare score.
Each factor contributes a transparent weight to a 0–100 score, and the breakdown is shown on the decision, never an unexplained number.
Compliance staff build and edit rules without engineering tickets, using the same primitives the API exposes.
Every rule set is versioned with an author and effective date, so a two-year-old decision can be replayed against the logic that produced it.
Run a candidate rule set against historical traffic to see what would have changed before it touches a live customer.
Retail, corporate, and high-value journeys can carry different thresholds while sharing one policy library.
Each decision returns the triggered rules, factor contributions, and the threshold it crossed, in the API and in the case record.
Draft to production
Edit, simulate against past sessions, approve, publish, with the version pinned to every decision.
Load a UAE regulator journey preset, then adjust it instead of writing a policy from an empty page.
Set factor weights and score bands for clear, review, and blocked per journey.
Replay historical verifications to see the change in clear rate, review load, and block rate before publishing.
Publish as a new version, then watch decision distribution and review volume for drift.
rule "high_risk_jurisdiction_edd" {
when {
customer.residency in policy.high_risk_countries
or entity.jurisdiction in policy.high_risk_countries
}
then {
score += 25
require "enhanced_due_diligence"
route_to "mlro_queue"
}
}
# version 14 · effective 2026-08-01 · author m.othman
# jurisdiction risk list source: set per tenant in consoleChain of custody
Illustrative sample data. A decision always names the rule version that produced it.
Named modules
Case work, reporting, and evidence export live on the case management page.
The two modules that decide which checks run, in what order, and what their results mean.
journey_builderComposes modules into an ordered journey with branching: run this check only if that one flags, escalate to enhanced due diligence on a risk band, skip a step for a low-risk segment.
risk_engineWeighted, explainable scoring across every signal produced in the journey. Each score shows the contributing factors and the policy version that produced it.
See the full module catalog , every KYC, KYB, AML, KYT, and platform module with its inputs and outputs.
Evidence retained
Questions
Continue
Most regulated journeys combine several of these. Each page covers one in the same detail.
A 30-minute walkthrough with a compliance engineer, or a request for sandbox access.