Deposit Monitoring & Confirmations

Every chain you accept, one deposit flow

Deposits on the chains and tokens you accept arrive in one stream, as soon as each block is indexed. Reorganizations, non-standard tokens and contract deposits are handled.

Review your deposit flowA first conversation, with no commitment.

A module of Stablecoin Issuers, Digital Asset Reconciliation and Wallet & Portfolio Data.

Capabilities

From block to credit decision

Deposit Monitoring & Confirmations is a deposit stream for teams that credit incoming crypto. Deposits to your addresses on the chains and tokens you accept arrive in one format as soon as each block is indexed. Events are updated or reverted after a reorganization, non-standard tokens and contract deposits are detected, and your confirmation policy decides when to credit.

Networks
The chains and tokens you accept
Detection
As soon as the block is indexed
Reorgs
Events updated or reverted
Confirmations
Your policy, per network and asset
Networks

All networks, one stream

The same stream for every chain and token in scope. One event format, so adding a network needs no new code.

Detection

Reported as the block lands

Transfers to your deposit addresses are reported as soon as their block is indexed. Each event carries the asset, the amount and the source transaction.

Reorgs

Reorganizations, handled

When a block is replaced, affected deposits are updated or reverted and your system receives a new event.

Tokens

Non-standard tokens, read correctly

Fee-on-transfer and other non-standard tokens are reported at the amount your address actually received, not the amount sent.

Contracts

Deposits through contracts, caught

Smart wallets, multisigs and batch contracts often deposit through internal transfers. These are detected too, like any direct deposit.

Confirmations

Your policy decides the credit

Each deposit is tracked against your threshold per network and asset. After a missed delivery, replay events from any block you choose.

Outcome

What's included

We report arrivals, confirmation status and reorganizations on the addresses in scope. The decision to credit, and when, stays with your system.

  • No new code per network
  • Deposits seen as blocks are indexed
  • Reverted deposits updated in your system
  • Credit at the amount actually received
  • Internal transfers counted as deposits
  • Missed deliveries recovered by replay

Built on Data API and Streams.

Support

Backed by agreed service levels

Service levels in writing

Uptime, response times and escalation paths are set in your agreement.

Support on your channels

Slack, Telegram or email, with hours that match your operations.

Monitored by engineers

Alerts reach our team before problems reach yours.

Questions

What teams usually ask us

Which networks and tokens does Deposit Monitoring cover?

The chains and tokens you accept, across the L1s, L2s, appchains and custom chains we index. The list is confirmed during scoping.

How fast does Deposit Monitoring report a deposit?

As soon as the block that contains them is indexed. Your confirmation policy then sets when a deposit is ready to credit.

Does Deposit Monitoring handle non-standard tokens?

Yes. Fee-on-transfer tokens are reported at the amount your address received. Deposits through smart wallets, multisigs and batch contracts are detected too.

Do we need our own nodes for deposit monitoring?

No. We run the nodes and the indexing. You receive the events.

Which networks can Deposit Monitoring & Confirmations 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 Deposit Monitoring & Confirmations?

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 Deposit Monitoring & Confirmations?

We handle setup and operations within the agreed scope. Before work starts, we define any integration tasks your team needs to complete.

How is Deposit Monitoring & Confirmations 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.