BlockTravel
Compliant by construction.
For VASPs, exchanges and custodians moving stablecoins and other digital assets. Every party on every leg of the payment is screened before it moves, not after, and to the same standard regulated fiat payments are held to.
Compliance that arrives after the money has already moved.
Stablecoin and digital asset payments settle in seconds, often through several counterparties before they reach their destination. Most compliance controls run after that. Sanctions screening, Travel Rule messaging and policy checks are applied as a separate step once value has already moved, and often only at the edges where a regulator is watching most closely.
Every hop and every counterparty in a payment’s path is a fresh point of exposure. A single weak link, a counterparty that screens late, screens loosely, or doesn’t screen at all, becomes the paying institution’s exposure, not just the counterparty’s.
For exchanges and regulated institutions moving stablecoins across borders, that exposure compounds with every additional hop. Compliance that runs after a transaction is compliance that arrives too late to prevent the exposure it exists to catch.
Compliance built into the payment, to the standard regulated finance already expects.
01 · Identity Compliance
BlockID
Know who you are dealing with.
02 · Transaction Compliance
BlockTravel
Clear every payment before it moves.
BlockTravel coordinates compliance for every party on a payment, on every leg. Not just the sender, and not just the first hop. A multi-hop, cross-border payment touching several counterparties is screened at each point it passes through, so a gap at one counterparty doesn’t become a gap in the whole payment.
Screening is carried out by Agentic Compliance, an agentic workflow that runs sanctions screening, checks on-chain data and applies the rules your institution defines, all before a payment is authorised to move. The gate is structural: the framework will not settle a transfer that has not cleared, so compliance is a condition of the payment itself, not a check performed on it afterwards.
Because the screening is agentic, every payment receives the same depth of review. The full rulebook is applied consistently and at payment speed, rather than a manual review queue or a static rules engine deciding what gets looked at. That is what makes compliance native to the payment, not bolted on from outside.
The bar is the one regulated fiat finance already sets. Sanctions screening, counterparty due diligence and Travel Rule messaging are held to the standard a bank’s compliance function would recognise, with an audit trail to match, so a digital asset service provider can evidence to its supervisor, and to its banking partners, that every payment was cleared before it moved.
Compliance coordinated across every leg, before the payment moves.
Agentic Compliance
An agentic workflow performs sanctions screening, checks on-chain data and applies your institution’s own rules before a payment is authorised, not after it has moved. Every payment gets the same depth of review, at payment speed.
Every leg, every counterparty
Compliance runs for every party on the payment path, not just the sender. A multi-hop, cross-border transfer is screened at each counterparty it touches, so no leg is the weak link.
Structurally gated settlement
Settlement is gated on compliance by the framework itself. Screening completes before a transaction executes, and a payment that has not cleared cannot move. That is a structural property of how BlockTravel settles, not a policy, a workflow step or an after-the-fact remediation.
Travel Rule, built in
Travel Rule messaging is part of the compliance layer and is protocol-agnostic. OpenVASP TRP and TRISA run today, as both sender and receiver, and the same adapter model extends to Sygna, Notabene, VerifyVASP, CODE and Veriscope counterparties. Originator and beneficiary information moves with the payment whichever protocol the counterparty uses.
API-first integration
REST and event-driven APIs. Drop into existing custody, exchange or treasury pipelines without re-architecture.
What BlockTravel is built on.
- FATF Travel Rule
- MiCA
- FCA
- MAS
- GDPR
- IVMS 101
- OpenVASP TRP
- TRISA
- OpenAPI 3.0
- OAuth2
- mTLS
The standards above are not aspiration. They define what BlockTravel supports today. IVMS 101 is the common data format every Travel Rule protocol carries, so a message can be translated between protocols without losing fields. OpenVASP TRP and TRISA are the protocols we operate today, on both the sending and receiving side. The Travel Rule market runs several others, including Sygna Bridge, Notabene, VerifyVASP, CODE and Veriscope, and BlockTravel is built to speak to each of them through the same API rather than asking counterparties to adopt a proprietary protocol of ours.
One API. Compliance coordinated across the payment lifecycle.
BlockTravel exposes a REST API and an event subscription layer across the payment lifecycle: counterparty discovery, compliance screening, Travel Rule message exchange, decision and execution. Webhook events fire on each state transition, on compliance exceptions, and on counterparty response timeouts.
The sandbox environment supports synthetic payments across the supported Travel Rule protocols and a reference set of counterparty VASPs.
Where BlockTravel does the load-bearing work.
Also from Block Infrastructure.
Make every digital asset payment compliant by construction.
Design partners get early access to BlockTravel, a direct line to the build team, a say in what gets built next, and preferential commercial terms once 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.