Bridge transfers, traced end to end
LayerZero, CCTP, ICTT, Hyperlane and more, decoded into one record per transfer. Source, bridge message and destination, with a status: pending, delivered or failed.
A module of Stablecoin Issuers, Digital Asset Reconciliation and Wallet & Portfolio Data.
One record per transfer
Cross-chain Transfer Tracking is one record per bridge transfer, for bridge teams, exchange and wallet support, compliance and foundations. It covers LayerZero, CCTP, ICTT, Hyperlane, OP Stack bridges, Taiko, Synapse, Omnibridge and more, linking the source transaction, the bridge message and the destination with a status: pending, delivered or failed.
- Protocols
- LayerZero, CCTP, ICTT, Hyperlane and more
- Format
- One record per transfer, every bridge
- Statuses
- Pending, delivered or failed
- Details
- Amounts, fees and timing per transfer
Major bridges, one view
LayerZero, CCTP, ICTT, Hyperlane, OP Stack bridges, Taiko, Synapse, Omnibridge and more, indexed and read the same way.
Source to destination, linked
The source transaction, the bridge message and the destination transaction are tied together in one record, whatever the protocol.
Pending, delivered or failed
Each transfer carries one status, updated as the destination is indexed. Failed and long-pending transfers stand out for review.
Amounts, fees and timing
Amount sent and received, bridge fee and delivery time on every record, in the same fields whatever the protocol.
One lookup for every ticket
Exchange and wallet support look up a transfer by hash or address and see where it stands, with no bridge explorers to switch between.
Capital flows across networks
Volumes by route, bridge and token, ready for operations reports, compliance reviews and foundation updates.
What's included
We observe and link transfers on the bridges agreed during scoping. Execution, settlement and refunds stay with the bridge and your systems.
- No code per bridge protocol
- Each transfer followed to its arrival
- Stuck transfers surfaced for review
- Fees and delivery times compared by bridge
- Customer tickets answered from one record
- Bridge volumes ready for reports
Built on Data API, Streams and Querybase. See cross-chain transfers in the explorer →
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
Can I track a CCTP or LayerZero transfer end to end?
Yes. Each record links the source transaction, the bridge message and the destination, with amounts, fees, timing and a status: pending, delivered or failed.
Which bridges does Cross-chain Transfer Tracking cover?
LayerZero, CCTP, ICTT, Hyperlane, OP Stack bridges, Taiko, Synapse, Omnibridge and more. The list for your networks is confirmed during scoping.
How is a failed bridge transfer shown?
Marked failed, with the source transaction and the bridge message, so your team can follow up with the bridge.
Can support look up a bridge transfer by hash?
Yes. A source or destination hash, or an address, returns the record with its current status.
Which networks can Cross-chain Transfer Tracking 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.
How are deposit and payment confirmations defined?
By your policy, per network and asset. We agree the thresholds with your team and report each transfer against them.
What happens to payment data after a chain reorganization or missed delivery?
We agree the handling during scoping. Affected events receive an updated status, and you can replay deliveries from a chosen point.
Which systems can receive Routescan payment and deposit data?
Webhooks, queues, databases, files or a dashboard. We agree the format with the team that owns the receiving system.
What stays in our own crediting system when Routescan monitors deposits?
The decision to credit and your customer records. We provide the data and its status. Your system applies your rules.
How long does it take to set up Cross-chain Transfer Tracking?
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 Cross-chain Transfer Tracking?
We handle setup and operations within the agreed scope. Before work starts, we define any integration tasks your team needs to complete.
How is Cross-chain Transfer Tracking 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.
Start with one transfer
Send us a transfer hash and the bridges you use. We trace it from source to destination and scope the rest from there.