Two records
never reconciled
The wallet is clean, the person is designated, and nobody joined them up.
By industry
Screening the person and the wallet
Chain analytics answers what an address has touched. Name screening answers who is behind it. A licence needs both on one case.
What you switch on
What a VASP switches on first
Both sides of the counterparty, from the first transaction.
Why this matters here
Two tools, two answers, one licence on the line.
Wallet exposure and name screening are usually bought separately and reviewed separately. The audit asks about one customer, and the answer has to be assembled from two systems that never agreed on who that customer was.
Travel Rule
three jurisdictions, three duties
One transfer, divergent thresholds, and data you have to trust on arrival.
MiCA
the licence was the cheap part
Ongoing conduct and reporting obligations landed on a team sized for the application.
2
Records per counterparty
1
Case that holds both
15 min
Rescreening interval
30+
Chains covered
Journey · Layer by layer
Scroll to advance
A customer through your funnel
-
Step 01
A counterparty appears
Wallet address and claimed identity resolve into one entity before either is assessed.
-
Step 02
Both sides screened
Chain exposure and name screening run against the same entity and land on the same record.
-
Step 03
Travel Rule data exchanged
Originator and beneficiary information per jurisdiction, with what arrives treated as a claim rather than a fact.
-
Step 04
One case, both trails
The investigator reads chain and identity evidence in one place, and the export contains both.
complead / entities / vasp
- Counterparties84,210
- Wallets linked112,908
- Resolved98.1%
complead / screening / dual
- Chain exposuremixer 2 hops
- Name matchPEP tier 2
- Combinedreview
complead / travel-rule
- Transfers today9,412
- Counterparty VASPs284
- Unverified claims17
complead / cases / #7719
- Evidence items14
- Chain hops recorded6
- EscalatedMLRO
Resolve
Screen
Transfer
Case
What you answer to
MiCA, the Travel Rule and what follows
Licensing was visible and finite. The ongoing obligations are neither, and they are what the supervisor comes back for.
Read the compliance guides
MiCA (EU)
Ongoing conduct and reporting obligations
Continuous
FATF R.15
Travel Rule data on transfers
Per transfer
National regulator
VASP registration and fitness
On licensing
FIU
Suspicious transaction reporting
On detection
Case study · Crypto
Read the case study
An exchange unified wallet exposure and name screening
Two vendors produced two verdicts on the same counterparty. Moving both onto one entity record meant the investigator stopped reconciling and started deciding.
2 → 1
Systems per case
4 weeks
To live
100%
Cases with both trails
Cross-family links
Where teams like yours go next
FAQ
Before you ask us
Do you replace our chain analytics vendor?
You can keep it. The point is that its output lands on the same entity record as the name screening, not that it comes from us.
How is Travel Rule data handled?
Sent per jurisdictional threshold, and what arrives is stored as a counterparty claim with its own confidence, not as verified identity.
Which chains are covered?
Thirty-plus, with exposure attributed to mixers, sanctioned services and darknet markets.
What does MiCA actually add?
Continuous conduct and reporting duties. The platform is built so those are exports rather than projects.
Put a wallet and a name on the same case
Bring one counterparty you have investigated twice. We will show you what it looks like as one record.
3,000+
Data sources checked
220+
Countries covered
15 min
Always real-time data