Skip to main content
A crypto external account — an address saved in the Address Book — can carry a Travel Rule verification of its address. Verifying it up front means the address is already compliant by the time the user deposits to or withdraws from it. A verification is tracked as one entry per level:
  • declared — a self-declaration questionnaire about the address (e.g. whether it belongs to a VASP or a self-hosted wallet).
  • verified — cryptographic proof of address ownership, through message signing or a Satoshi test. It can be initiated directly through the Address Book API, without needing a prior deposit or withdrawal, and requires the user to have the crypto-deposits capability.
Both levels are backed by the same mechanism: a request for information (RFI), whose proofOptions field lists which proof mechanisms are available, and whose proof field holds what was submitted once resolved. See Proof types for details on self-declaration, message signing, and satoshi-test.

​
Relation to external accounts

Verifications are managed through the External accounts endpoints — Set up, Get, and List verification. This guide walks through using them end to end.

​
Start building

Verify via API

Set up and resolve a declared- or verified-level verification for a saved crypto address.