Which Travel Rule protocols does WIDTH support?
IVMS101 as the payload standard, exchanged over the major Travel Rule networks — TRP, Sygna Bridge, Notabene, Veriscope, OpenVASP, and direct VASP-to-VASP. Protocol selection is handled per-counterparty with fallback to the next available transport.
How does WIDTH discover and verify counterparty VASPs?
VASP discovery uses a federated directory backed by GLEIF, regulator-published licensee registries (MAS, HKSFC, FCA, FINMA, JFSA), and cross-network lookups. Each counterparty VASP is verified via cryptographic key pinning + LEI before any PII payload is exchanged.
Which jurisdictions are covered?
85+ jurisdictions with Travel Rule rules in force, including all FATF members and major emerging frameworks: Singapore (MAS PS-N02), Hong Kong (HKSFC VASP), EU (TFR / MiCA), UK (FCA), US (FinCEN), Japan (JFSA), South Korea (FIU), Switzerland (FINMA), UAE (VARA), Australia (AUSTRAC).
How are unhosted (self-custody) wallets handled?
Unhosted wallet flows follow the jurisdiction-specific rule: self-declaration + proof-of-ownership (Satoshi test / signature) where required, with risk-based screening. The same KYT decision token captures the wallet-attribution intelligence on the unhosted side.
What's the IVMS101 fields coverage?
Full IVMS101 v1.1 originator + beneficiary blocks, including natural person and legal person variants, geographic address structures, national identifier, and customer-identification reference. Country-specific fields (e.g., Japanese kanji name lines) are supported.
Is the message exchange encrypted end-to-end?
Yes. Each Travel Rule envelope is end-to-end encrypted to the counterparty VASP's pinned key. PII never sits in plaintext on shared infrastructure, and the WIDTH backend stores only the encrypted envelope + integrity hash for audit replay.
