By · · last updated 2026-07-28
Travel rule shares counterparty data between VASPs; sanctions screening checks who you may deal with. They are different obligations — and both belong in the stack.
Teams integrating compliance often discover two overlapping-sounding requirements: travel rule and sanctions screening. They are different obligations that get conflated.
Travel rule is the information-sharing obligation: VASPs must share beneficiary-owner and counterparty data for transfers above thresholds. Sanctions screening is the prohibition check: may you deal with this party at all? One moves data between regulated firms; the other blocks prohibited transactions.
A 1-page compliance audit for your payment agent. Check your setup against the 7-point framework. Enter your email — we send it instantly.
Travel rule is VASP-to-VASP messaging (Notabene is the category leader). Screening is a per-transaction list check against the SDN list — 947 wallets, 19,218 names, 16 jurisdictions. A payment can be fully travel-rule compliant and still hit a sanctioned wallet.
Regulated VASPs typically need both: a travel-rule network for messaging, and a screening API on the payment path. They are complements, not substitutes — and for agents, the screen is the layer that runs before every payment.
Free tier, 5 checks/day. Add compliance before money moves.
Try the free checker See pricing