Investigation handled, ready to review
Start from an alert, a wallet or a customer. The Investigation Agent reads Chainalysis, TRM and Sumsub in place, follows the funds and hands your analyst a cited case file in minutes.
What's in the case file
The agent gathers what your analyst would have gathered, into one file, with every item traced to the source it came from.
Counterparty in context
Who controls the wallet and who stands behind them: attribution, registration and licensing status, sanctions exposure, each with its source attached.
The corridor's rules, applied
Thresholds and data requirements for both jurisdictions the transfer touches. Where they differ, the stricter standard applies and the file says which.
Originator
Beneficiary
- Travel RuleLegislated
- Sanctions screenMatched
- Originator dataMatched
- Beneficiary VASPMatched
Risk, factor by factor
A composite risk read broken into its factors: counterparty, corridor, threshold, sanctions. Every factor traced to the data that produced it.
- Registration0
- Licensing0
- Sanctions0
- Compliance history0
A recommendation with its reasoning
Approve, escalate or report, with the reasoning behind each factor. Your analyst accepts it, changes it or overrides it. The file records which.
One case, worked end to end
The agent starts the moment a case opens in your case tool and works it to a recommendation. Your analyst opens it and finds the evidence gathered.
The case opens
A monitoring alert trips a threshold, or an analyst opens a wallet, a transfer or a customer. Either way the agent starts from what's there, in the case tool you already run.
Transfer received · 0.85 BTC
Threshold rule matched — SGD 20k
Corridor identified — SG → AU
Counterparty resolved via VASP Track
Onchain flow traced (3 hops)
Sanctions and PEP screened
Case file assembled
The evidence is gathered
Attribution from Chainalysis or TRM, the customer's record in Sumsub, screening results, transfer history and the corridor's rules, read in place. The funds are followed across hops to where they stop.
VASP Track
Counterparty registry · VASP Track profiles
Jurisdiction DB
Live AUSTRAC / MAS / FCA rules
Transfer history
Customer prior cases · 48 months
Sanctions screening
OFAC, EU, UK, AU lists · refreshed regularly
Blockchain analytics
Chainalysis + TRM attribution
VASP Track
Counterparty registry · VASP Track profiles
Jurisdiction DB
Live AUSTRAC / MAS / FCA rules
Transfer history
Customer prior cases · 48 months
Sanctions screening
OFAC, EU, UK, AU lists · refreshed regularly
Blockchain analytics
Chainalysis + TRM attribution
Case file
TRV-0847 · Risk Medium
Your analyst decides
The file arrives with a recommendation and the reasoning behind each factor, so the disposition is never a black box. The decision is logged with the full file attached.
Escalate to senior analyst
ReadyCounterparty
SatoshiX (SG)
Corridor
SG → AU
Risk
Medium (72/100)
Findings
Mixer hop · velocity 3.2× peer
Export
Every line, traced to its source
Each item in the case file links back to where it came from: the Chainalysis attribution, the Sumsub record, the screening result, the regulator's published threshold. Select any field and see its origin. When a regulator asks how you knew, your MLRO can show them.
Counterparty resolved
Customer wallet matched to SatoshiX (SG) via Chainalysis attribution.
Chainalysis KYT
Jurisdiction loaded
MAS PSN02 thresholds + FATF Rec 16 obligations applied.
Jurisdiction DB
Sanctions cross-checked
OFAC, UK, EU, AU sanctions lists checked at 14:32:01.
World-Check + ComplyAdvantage
Risk score computed
Composite 72/100 — Medium. Driver: counterparty history.
Risk Engine v3.2
Brief assembled
Six source artefacts attached, evidence ledger sealed.
Investigation Agent