Login
VAAS · AML & Crypto

From wallet to settlement, exposure surfaces.

Transaction monitoring for AML/CFT, watchlists, adverse media, and KYT on wallets. Coverage across 25+ blockchains, OFAC, mixers, and sanctions exposure, with an auditable workflow.

The problem

Crypto risk does not stop at onboarding.

Three fronts where traditional AML falls short of on-chain activity.

On-chain

A clean wallet today turns dirty in two hops.

Screening only at registration misses exposure that arrives later. Funds routed through a mixer or touching a sanctioned address contaminate a wallet within a few hops, and without continuous KYT the exposure only shows up at audit time.

25+
blockchains need coverage for origin tracing to mean anything
False positive

Watchlists without context flood the alert queue.

Matching names against a list without disambiguation generates too many alerts and too little confidence. The AML team spends the day discarding noise and misses the typed alert that actually supports a SAR.

SAR
the queue must arrive typed and prioritized, not as a raw match pile
Travel Rule

VASP without counterparty data blocks settlement.

The Travel Rule requires originator and beneficiary on transfers between VASPs. Without collecting and validating that data in the flow, the transaction stays pending or settles out of compliance, creating regulatory exposure.

FATF
Travel Rule is mandatory, and counterparty data must be captured at transfer time
What we cross-check

Everything in a single call.

Public and private sources queried in parallel, normalized and weighted by the use-case matrix.

Transaction monitoringKYT on wallets25+ blockchainsOFAC and mixersPEP and adverse mediaTravel Rule
Regulations covered
COAF · ReportingCirc. BCB 3.978Lei 9.613OFAC SDNFATF
Decision anatomy

One wallet. Two hops to a sanction.

The engine traces fund origin on-chain, identifies mixer and OFAC exposure, cross-checks the customer against watchlists and media, verifies the Travel Rule, and opens the SAR with an auditable workflow.

DECISION · AML-2026·Q2 · 09/jun 14:22
Wallet 0x71a...d4 · VASP transfer · high risk
block · SAR opened
On-chain tracing
Coverage25+ blockchains
OFAC exposure · 2 hops0.34 BTC
Mixer (Tornado Cash)Detected
KYT · wallet scoreHigh
Cross-checked signals
!Exposure to sanctioned address
!Mixer transit
PEP / sanctions (customer)
Adverse media (customer)
!Travel Rule · originator
!Transaction typology
!Alert history
!Risk geography
Score · AML risk
Sanctions exposureDirect · 2 hops
Origin risk (KYT)High
Travel RuleIncomplete
Global score0.87/1.00 · red
AI-generated summary

Recommendation: Block and report. Wallet with OFAC address exposure at 2 hops (0.34 BTC) and confirmed mixer transit. Customer clean on PEP and media, but Travel Rule incomplete on the VASP side. Transaction stopped; SAR pre-filled and opened for COAF with the on-chain trail attached.

1
Continuous KYT across 25+ blockchains

Wallet risk is re-evaluated per event, not just at registration. Mixer and sanctioned-address exposure is traced to fund origin, a few hops back.

2
Typed alert, prioritized queue

Watchlist screening comes with disambiguation and typing. The AML team sees what supports a SAR at the top, not a raw match pile to discard.

3
Travel Rule and SAR in the same flow

Counterparty data is collected and validated at transfer time. When it hits, the transaction stops and the SAR exits pre-filled for COAF with the auditable trail.

Regulatory

The crypto AML the regulation already requires.

Transaction monitoring, sanctions, and Travel Rule are ongoing duties for virtual asset operators. Five instruments back the controls.

Res. 36
COAF · Resolution

Suspicious transaction reporting

Atypical transactions involving virtual assets must be reported. The typed alert and on-chain trail support the SAR.

3.978
BCB · Circular

AML/CFT and monitoring

Requires continuous transaction monitoring and suspicion identification. KYT is part of crypto activity monitoring.

OFAC
List · SDN

International sanctions

Exposure to sanctioned addresses and entities requires blocking and reporting. On-chain tracing measures direct and hop-based exposure.

FATF
Travel Rule

Counterparty data between VASPs

Transfers between virtual asset service providers require originator and beneficiary. Data is collected and validated in the flow.

Rollout

From kickoff to go-live in 4 weeks.

Multi-tenant architecture. What changes per client: connected chains and lists, KYT thresholds, and SAR policy.

01
Week 1

Discovery & scope

Map relevant chains, watchlists, transaction typologies, and Travel Rule flow.

02
Week 2

Calibration

Tune KYT thresholds, alert typing rules, and sanctions matrix. Validate false positive rate.

03
Week 3

Directed pilot

Monitor a slice of the base in parallel. First typed alerts for AML team validation.

04
Week 4

Go-live

KYT in production. SAR queue with auditable workflow active. Travel Rule in the flow. Team trained.

Ready?

Decide in seconds.
Start with a meeting.

In 15 minutes we show how VAAS works in your scenario, with your rules, your data, your volume.

Explore the platform