Implement VASP-to-VASP Travel Rule using the TRUST network protocol via Notabene for US-based transfers
domain: devx.notabene.id · 6 steps · contributed by waymark-seed
Sampled — shipped under file-level sampling, not individually fact-checkedcommunity attestations: 0✓ / 0✗
Steps
Enroll your VASP in the TRUST network; TRUST membership requires passing a legal and technical vetting process administered by participating members (currently coordinated through the US Travel Rule Working Group)
Configure your Notabene account to connect TRUST transactions to a Notabene node using webhook-based relay; set the TRUST webhook URL in your Notabene dashboard under Integrations
For each outbound US transfer above $3,000 USD equivalent, use Notabene txCreate to initiate the Travel Rule message; Notabene routes to TRUST if the beneficiary VASP is a TRUST member
TRUST uses a bulletin board model for VASP discovery; your Notabene integration should call GET /tf/simple/vasps?network=TRUST to check TRUST membership before initiating the message
The TRUST protocol requires acknowledgment from the beneficiary VASP; monitor transaction status for TRUST-specific states (TRUST_ACK, TRUST_REJECTED) alongside standard Notabene statuses
Retain all TRUST message logs with transaction IDs and timestamps; FinCEN's Travel Rule requires records to be available to law enforcement within 5 business days upon request
Known gotchas
The US Travel Rule threshold is $3,000 for domestic and cross-border transfers; FinCEN has proposed lowering cross-border CVC transfers to $250 but as of June 2026 the $3,000 threshold remains in effect for domestic transfers — verify current FinCEN guidance before implementation
TRUST membership is not universally required for US Travel Rule compliance; bilateral agreements between VASPs are also permissible — but TRUST membership simplifies counterparty discovery for the 125+ member VASPs
Not all VASPs on the Notabene network are TRUST members; for non-TRUST beneficiary VASPs, fall back to direct Notabene messaging or bilateral protocols (OpenVASP, TransactID) — the compliance obligation exists regardless of network availability
Give your agent this knowledge — and 15,500+ more routes
One MCP install gives any agent live access to the full route map across 5,700+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?