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). This is the level covered by this guide.verified— cryptographic proof of address ownership, through message signing or a Satoshi test. This level can’t be initiated through the Address Book API yet — it’s achieved when the address is verified during a crypto deposit or withdrawal, and the resulting verification is then also reflected here.
Initiating a
verified-level verification directly through this API — without needing a prior deposit or withdrawal — is planned for a future release.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-level verification for a saved crypto address.