BlockTravel
Enable compliant movement.
For VASPs and digital asset operations under FATF Travel Rule, sanctions and transfer-policy obligations.
Travel Rule compliance, fragmented across the market.
The FATF Travel Rule requires Virtual Asset Service Providers to share originator and beneficiary information on transfers above defined thresholds — and to ensure that information is accurate, timely and protected. The mechanism is settled. The market’s implementation of it is not.
Travel Rule message protocols are fragmented across competing standards. Sanctions screening on chain addresses is operationally heavy and inconsistent. Counterparty policy posture varies across every VASP an institution transacts with — some have it, some don’t, some have a version that doesn’t reconcile to yours. Each transfer carries the cost of that fragmentation.
VASPs and regulated institutions operating across MiCA, FATF, FCA and equivalent regimes feel this most acutely — different jurisdictions require different evidence, different thresholds, different message formats. Fragmented Travel Rule compliance is a structural cost of fragmented digital asset infrastructure, not a vendor problem.
The digital asset transfer compliance layer of the Block Infrastructure architecture.
01 — Identity Trust
BlockID
Verify the participant.
02 — Payment Control
BlockPay
Govern the transaction.
03 — Digital Asset Transfer Compliance
BlockTravel
Enable compliant movement.
04 — Settlement Certainty
BlockSettle
Settle with confidence.
BlockTravel is the digital asset transfer compliance layer of the Block Infrastructure architecture — the point where movement obligations apply. It depends on BlockID for verified originator and beneficiary context, runs alongside BlockPay where fiat and digital flows interact, and feeds compliance state into BlockSettle for settlement-conditional digital asset flows. Travel Rule, sanctions screening and policy enforcement are coordinated, not bolted together.
Travel Rule, sanctions and policy — coordinated, not bolted.
Travel Rule messaging
Originator and beneficiary information exchange with counterparty VASPs. Multi-protocol support so transfers complete regardless of which standard each side runs.
Sanctions and policy pre-screening
Chain address pre-screening, sanctions list checking and policy rule application before transfer initiates. Consistent posture across every transfer, every counterparty, every chain.
Counterparty discovery
Identification of counterparty VASPs and their compliance posture before submitting Travel Rule data. No data sent to unrecognised endpoints.
Multi-jurisdiction policy
Configuration per jurisdiction — MiCA, FATF, FCA, MAS — so transfers carry the framework they are regulated under. One transfer, multiple regulatory contexts handled at the same time.
API-first integration
REST and event-driven APIs. Drop into existing custody, exchange or compliance pipelines without re-architecture.
What BlockTravel is built on.
- FATF Travel Rule
- MiCA
- FCA
- MAS
- GDPR
- IVMS 101
- TRP
- TRUST
- OpenAPI 3.0
- OAuth2
- mTLS
The standards above are not aspiration — they define how BlockTravel is built and how it must operate. IVMS 101 is the canonical interVASP message standard; TRP and TRUST are the market-leading Travel Rule protocols. We support what counterparties are running, not just what we’d prefer them to run.
Five lifecycle states across multiple Travel Rule protocols.
BlockTravel exposes a REST API and an event subscription layer for the transfer lifecycle: counterparty discovery, pre-screening, Travel Rule message exchange, decision and settlement. Webhook events fire on each state transition, on pre-screening exceptions, and on counterparty response timeouts.
The sandbox environment supports synthetic transfers across the supported message protocols and a reference set of counterparty VASPs.
Working diagram — bespoke version to ship with final assets.
Where BlockTravel does the load-bearing work.
Network Compliance Oracle
Real-time, network-wide compliance signals attached to verified participants and digital asset movement.
Fraud Prevention
Pre-execution participant verification, transaction governance and movement compliance — coordinated.
Zero Market Exposure
Transfer compliance and settlement certainty coordinated — no market exposure window between movement and finality.
BlockTravel does not work alone.
BlockID
Reusable identity verification. BlockTravel references BlockID for both originator and beneficiary verification on every transfer.
BlockPay
Pre-execution compliance and orchestration for fiat payment flows. BlockTravel’s fiat counterpart where flows cross between rails and chains.
BlockSettle
Atomic and conditional settlement. BlockTravel’s compliance state can drive BlockSettle’s settlement conditions for digital asset flows.
Make digital asset movement institutionally governable.
Design partners get early access to BlockTravel, a direct line to the build team, influence on the V1 roadmap, and preferential commercial terms when BlockTravel moves out of design partner stage. We ask for genuine integration intent, a structured feedback loop with named technical and compliance counterparts, and a mutual non-disclosure agreement.