SentinelMeridian Digital Exchange · Customer Portfolio · 48,213 customers
Crypto model48,213 / 100,000
Dashboard
Monitored Parties 16
Alerts 7
Model & Settings
Every customer is screened at onboarding, then monitored continuously — re-rated whenever a new sanctions, on-chain, jurisdiction or behavioural signal lands. This is the live shape of the book, not an onboarding snapshot.
Parties monitored
48,213
100% of active book
New alerts · 30d
7
↑ 2 vs prior 30d
Re-rated today
1,204
event-driven + scheduled
Drifted up · 30d
47
crossed to higher band
Suppressed
142
namesake / low-confidence
Party mix & risk concentrationby counterparty type · risk-weighted
Party type
Parties
% book
Risk mix
Avg
High+Sev
Alerts 90d
Counterparties are 1,033 parties (2.1% of the book) but hold a disproportionate share of severe risk and nearly all settlement exposure. One high-risk VASP outweighs a thousand clean retail accounts — which is why the same engine has to score them side by side.
Counterparty signalsentity-only · no individual equivalent
$142M
settlement & liquidity exposure to High / Severe counterparties
Geographic distributionparties by jurisdiction · risk-weighted
Jurisdiction
Parties
% book
Risk mix
Avg
Alerts 90d
Regime
By regionshare of book
Jurisdiction-integrity flags
23 parties declare residence in a supported market, but on-chain counterparties and login signals indicate access from a restricted or sanctioned jurisdiction. This declared-vs-inferred mismatch is the control gap behind the largest crypto AML enforcement actions to date — masked access from a banned market. Flagged for EDD and location re-confirmation.
Alerts by risk dimensionlast 30 days · vs prior
Sanctions / PEP
2
↑ 1
KYC / identity
1
↑ 1
Wallet / on-chain
1
↑ 1
Geographic
1
→ 0
Behavioural
2
→ 0
Risk band distribution
82%
13%
Low 39,540
Medium 6,265
High 2,168
Severe 240
Recent rating changesband moves · 30d
Top customers · alert countlast 90 days
Upcoming re-rating wavesscheduled floor · next 14 days
Severe-band customers240 · daily
High-band customers2,168 · in 2 days
Medium-band customers6,265 · in 9 days
Event-driven re-ratingcontinuous
Scope: one financial-crime engine (sanctions · PEP · AML · adverse media · on-chain) across every party — individuals, corporate customers, counterparty VASPs, market makers and vendors. Subject type is a configuration: a person is scored on KYC, an entity on Ownership & UBO. Entity depth (KYB, UBO resolution) is supplied by D7; commercial-risk lenses (financial, litigation) are an optional add-on for procurement buyers, not shown here.
Demo environment — all customers, ratings and figures are fictional.
One financial-crime engine across every party — individuals and entities, customers and counterparties. Select any party to see how its score is built, factor by factor. The dimension set adjusts by party type (a company is scored on Ownership & UBO where a person is scored on KYC), but the lens, the composite and the override are identical.
Sorted by risk score, highest first
Party
ID
Jurisdiction
Top risk driver
Score
Band
Next re-rate
Back to parties
Monitoring raises an alert only when something changes — a new match, a new on-chain exposure, a behavioural escalation since the last read. Every candidate passes suppression and confidence checks before it reaches you.
Sentinel surfaces and delivers; your team dispositions
Alerts are delivered to your case management system, where investigation and the final decision (including any regulatory filing) happen. This queue is the delivery record and audit trail.
142 candidate alerts auto-suppressed this period — namesake collisions (fuzzy < 0.85), stale-archive, and confidence < 0.70. T1/T2 always surface regardless of confidence.
Webhook delivery active
One engine, tuned per vertical. The risk model is a transparent weighted composite you configure and publish — no black box. Switch the preset to see the same engine reweight for a different segment.
Vertical preset
Crypto● active
Gaming●
Fintech●
Bank●
Active for this workspace. Others shown as preview.
Factor weightsCrypto model
Risk methodologyone engine · dimension set configured per party type
contribution = round( sub-score × weight ) · composite = Σ contributions · band: 0–24 Low · 25–49 Medium · 50–74 High · 75–100 Severe
The same engine scores every party; the dimension set and weights are a configuration of party type. Individuals carry KYC; entities carry Ownership & UBO instead; counterparty VASPs add Regulatory posture. Each dimension is either detected natively (Screening, KYC / Ownership, Geographic, Regulatory) or ingested from your on-chain / transaction-monitoring provider (Wallet, Behavioural) and fused into one composite.
Adverse media (scaled by severity of finding)30–75
False positive / no match0–15
Asks "is this person on a list or in the media?" — sanctions, PEP, watchlist, adverse media. Each hit is resolved through the L1–L4 adjudication layer (name → DOB/ID → source tier → prior decision) before it scores, and the fuzzy-match namesake filter (≥ 0.85) gates whether a hit counts at all. The sub-score is the single most severe resolved finding — a confirmed hit is never averaged away.
KYC / identityDOMINANT · gate-like
Failed re-verification / IDV revoked by client85–100
Synthetic- or duplicate-identity signal70–90
Data inconsistency detected post-onboarding50–70
Re-verification overdue / document expired40–60
Re-verification due soon20–40
Verified, current, no drift0–15
INDIVIDUALSAsks "is this person who they claim to be, and is that still true?" — a different question from screening. The client runs IDV at onboarding; Sentinel consumes the pass/fail result and then monitors for identity drift — document expiry, re-KYC falling due, data-consistency changes, and synthetic-identity signals emerging after the customer goes live. Gate-like: a hard fail caps the customer at high-risk regardless of a clean screen, because a name you can't confirm is real makes every other check unreliable.
ENTITIESThe entity equivalent of KYC — "who really controls this company?" D7 verifies the corporate structure and maps UBOs and directors; those individuals are then screened as natural persons and their sanctions/PEP/adverse-media findings flow up into this score. Gate-like, because a sanctioned person cannot hide behind a clean shell — which is exactly what the override enforces.
Direct darknet / ransomware / illicit-service exposure80–95
Indirect exposure — 1 hop75–90
Indirect exposure — 2 hops55–75
Indirect exposure — 3+ hops (tapering)30–55
High-risk / unregistered VASP counterparty40–65
Mainstream regulated exchange20–40
Clean0–20
Sentinel does not analyse the chain itself — it consumes your integrated on-chain analytics feed (bring-your-own: Chainalysis / TRM / Elliptic) and scores the returned exposure. Takes the single most severe exposure, not an average. Two modifiers: severity scales with the proportion of funds exposed, and exposure is time-weighted so recent activity outweighs a stale one-off.
GeographicDOMINANT · highest touchpoint
FATF blacklist jurisdiction90–100
Comprehensive-sanctions country70–90
FATF greylist jurisdiction60–80
Client enhanced-KYC jurisdiction40–60
Standard jurisdiction20–40
Strong-AML jurisdiction0–20
Evaluates every touchpoint — nationality, residence, funding origin, counterparty jurisdictions — and takes the highest-risk tier. A small additive bump applies when several high-risk touchpoints coincide; a low-risk residence partially mitigates but does not erase a high-risk nationality or funding origin.
BehaviouralADDITIVE · sum of patternsingested · provider
Structuring+35
Layering+30
Velocity anomaly (scaled by magnitude)+25
Profile inconsistency+25
Rapid pass-through+20
Dormancy-then-burst+15
Peer-group deviation+15
Baseline (never zero)15–20
Reads your transaction-monitoring alerts and sums points per distinct pattern, capped at 100 — because two independent suspicious behaviours are worse than one. This is the one additive dimension: the others take the worst single finding, behavioural takes the aggregate of conduct.
Regulatory postureDOMINANT · worst finding
Unlicensed in operating markets · enforcement action75–100
VASP COUNTERPARTIESA sixth dimension applied only when the party is another crypto business. Assesses whether the counterparty VASP is licensed, runs a credible AML programme, and can meet Travel Rule obligations — the crypto-specific question of "is this a compliant business to plug into?" Not applied to individuals or ordinary corporate customers.
Override layer — applied after the composite
Certain findings force the band regardless of the weighted arithmetic, so a high-consequence risk is never diluted by the average: a confirmed sanctions match on the party or a beneficial owner → Severe / block, and direct exposure to a sanctioned wallet → Severe / block. Because a sanctioned person cannot hide behind a clean shell, this is what makes Ownership & UBO gate-like. The composite is the base score; overrides are the non-negotiables on top. Mirrors D7's verdict-engine overrides.