Travel Rule exchange is coming to ChainAnalyzer — screening and transmission in one flow

ChainAnalyzer is building a VASP-to-VASP information exchange (transmission) capability for the FATF Travel Rule, offered to Enterprise customers. It integrates the transmission itself with the on-chain risk assessment ChainAnalyzer already provides (recipient screening, sanctions matching, attribution), so that pre-transfer risk decisions and Travel Rule notification complete in a single flow. The core method is patent pending.

A two-stage risk gate: check again after approval

In the standard Travel Rule exchange (TRP: Travel Rule Protocol), the deposit address is disclosed only when the beneficiary VASP approves. Verifying that just-disclosed address has traditionally been left to manual operations.

• Stage 1 — before any exchange starts, the destination and counterparty VASP are screened. If risky, no inquiry is sent at all.
• Stage 2 — the deposit address disclosed on approval is screened again before on-chain execution. If risk is found, the transfer is automatically voided even though it was approved, with the grounds recorded in the audit trail.

Placing procedural "approval" and on-chain "safety" as two independent gates in series structurally removes the blind spot that appears when screening and transmission run as separate services.

Personal data on a separated foundation

Originator and beneficiary personal data handled in transmission is encrypted and managed on a physically separated foundation from the detection engine. Queries toward the detection engine are mechanically restricted to wallet addresses, chain identifiers, and legal entity names — keeping the screening engine verifiably out of contact with personal data.

Jurisdictional differences absorbed by policy

Notification duties, required data fields, and the treatment of self-hosted wallets differ sharply by jurisdiction (Japan exempts transfers to self-hosted wallets from notification; Peru prohibits the transfer itself when the information cannot be collected). A single engine handles such opposite requirements through per-jurisdiction policy configuration alone.

Availability

In preparation as an Enterprise add-on, built on TRP (an open standard with interoperability bridges). If you are looking to combine Travel Rule compliance and on-chain AML in one place, please reach out via our contact form.

* This capability is under development; availability and specifications are subject to change.