Missing or incomplete Travel Rule data
How to handle gaps in incoming or outgoing Travel Rule information.
Missing or partial Travel Rule data can delay investigations and create audit risk. This page describes common scenarios and the operational steps teams typically take to resolve them for outgoing and incoming transactions.
Use it alongside your risk-based procedures and escalation playbooks.
What you'll learn
- Typical scenarios that lead to missing or incomplete data
- Operational options for resolving gaps
- How to document actions for audit readiness
Outgoing transactions
Common scenarios
- The destination wallet is unknown to CryptoSwift. The wallet might belong to a VASP that is not reachable from our network automatically based on the wallet only, or the wallet might be a new wallet that has just appeared on the blockchain.
- The destination wallet, even though marked as custodial, is actually a self-hosted wallet and there is no VASP behind the wallet address.
Operational responses
Provide the beneficiary VASP name
If the outgoing message is updated with the beneficiary VASP name, CryptoSwift can deliver the message even if the wallet is unknown.
Mark the wallet as self-hosted
If the message is updated to include the wallet type as self-hosted (NON_CUSTODIAL), the message will be marked as delivered and we will not retry to detect a VASP behind the address.
Incoming transactions
Common scenarios
- The originator VASP sends a message without required identity fields.
- There is no Travel Rule message available for an incoming crypto transaction.
Operational responses
Backfill missing data
Collect missing fields from internal KYC systems, customer onboarding records, or transaction monitoring tools. Attach the recovered data to the transaction record so your audit trail remains complete.
Ask the customer for clarification
Request additional information directly from the customer. This is often the fastest way to resolve missing VASP names or self-hosted wallet declarations. An example implementation could look like this:
Submit a claim for missing data
Claims allow you to flag a blockchain transfer that lacks Travel Rule data. The purpose is traceability and evidence collection, not real-time settlement. CryptoSwift uses claims to contact counterparties or search for matching payloads and then forwards any recovered information back to you.