Transfer details sent straight to your Travel Rule provider
Qualifying transfers identified with the thresholds you set per jurisdiction. Details delivered to your provider and kept for your retention period.
A module of Transaction Monitoring and Audit Evidence.
From transfer to provider
Travel Rule Data Integration is a feed of transfer details to the Travel Rule provider you work with. Qualifying transfers are identified with the thresholds your compliance team sets per jurisdiction, tracked and kept for your retention period. Originator and beneficiary data stays with you and your provider.
- Thresholds
- Set per jurisdiction by your team
- Delivered to
- The Travel Rule provider you use
- Identity data
- Stays with you and your provider
- Records
- Kept for your retention period
Thresholds set per jurisdiction
Your compliance team decides the amount for each jurisdiction. Transfers on your addresses are checked against it as blocks are indexed.
Onchain details sent to your provider
Hash, asset, amount and addresses for each qualifying transfer go to your provider, which handles the identity exchange with the counterparty.
Delivery status per transfer
Status and source transaction stay with each delivery for the retention period you define, ready when compliance asks.
What's included
Applicability and thresholds depend on your jurisdictions. Originator and beneficiary data does not come from the ledger and stays with you and your provider.
- The right transfers, by your rules
- Failed deliveries visible per transfer
- A traceable record for each transfer
Built on Streams.
Backed by agreed service levels
Uptime, response times and escalation paths are set in your agreement.
Slack, Telegram or email, with hours that match your operations.
Alerts reach our team before problems reach yours.
What teams usually ask us
Does Routescan exchange Travel Rule identity data?
No. Originator and beneficiary data stays with you and your provider. We supply the onchain transfer details.
Who sets the Travel Rule thresholds?
Your compliance team, per jurisdiction. We apply them to your transfers and record which rule qualified each one.
Which Travel Rule providers can you feed?
We confirm the integration with your provider's interface during scoping, before any work starts.
Which networks can Travel Rule Data Integration support?
Any EVM network: L1s, L2s, appchains and custom chains, from private testnet to mainnet. Our public multichain explorer indexes 24 mainnet networks today, and we onboard new ones as part of setup.
Which screening and Travel Rule providers can we use with Routescan?
The screening and Travel Rule providers you already use or choose. We connect them to your workflow, we do not replace them.
Who makes the risk decision in a Routescan compliance workflow?
Your team. We bring together activity, provider results and your rules. The decision and its rationale stay with your reviewers.
How are unknown screening results shown?
The result is marked unknown, with its source and date. Missing coverage is never reported as a clear result.
Where are our compliance records stored?
Where your agreement says, with access limited to your organization. Retention is agreed with your compliance team.
How long does it take to set up Travel Rule Data Integration?
It depends on the scope. We review the requirements and integrations, then agree a written plan, schedule and responsibilities.
Do we need to build anything to use Travel Rule Data Integration?
We handle setup and operations within the agreed scope. Before work starts, we define any integration tasks your team needs to complete.
How is Travel Rule Data Integration priced?
The price depends on what we build, the integrations and the ongoing work. Your proposal lists deliverables, timeline and support. Data usage and services from other providers are listed separately where they apply.
Connect your Travel Rule provider
Name your provider, jurisdictions and thresholds. We scope the feed, the delivery checks and the retention around your systems.