Risk cleared
Nothing about the counterparty or the transfer itself raised a concern. The transaction proceeds as normal.
Crypto Blockchain Analysis
Crypto Blockchain Analysis
Every crypto deposit and withdrawal is checked against blockchain risk data, before the transfer settles and again once it’s confirmed on-chain, powered by SumSub’s Crypto Monitoring integration.
Wallet screeningCounterparty
Risk scoreLow
ExposureNone found
ProviderSumSub
Continue
Every screen, a clear outcome
Four outcomes, never a silent one
A screening request doesn’t just return a score. It resolves to an action, and that action is what actually happens to the transfer.
Flagged for a closer look
A risk signal crossed a configured threshold, so the transfer pauses for review rather than proceeding automatically.
Blocked before it moves
Exposure to a sanctioned entity, mixer, or other high-risk source stops the transfer before funds settle.
The provider hasn’t caught up
Blockchain data has a short indexing lag. The request retries automatically rather than failing outright.
Every outcome is attached to the transaction itself, with the specific rule that fired, so a hold or a rejection is never a mystery to whoever reviews it.
Worth knowing
A few things shape how screening actually runs
Not the customer’s own wallet
Screening a customer’s own wallet, at onboarding for example, is a separate, related capability.
Transaction screening runs after broadcast
Full transfer-level risk requires the on-chain transaction hash, so it only runs once a transfer is confirmed.
Not locked to a single source
Results are available per configured provider, so the review experience stays consistent either way.
A paid capability, enabled deliberately
Rules are installed and tuned to a tenant’s own risk appetite before it goes live in production.
Some providers need one
For bring-your-own-key providers, screening requests fail until a valid key is added.
Timing matters for freshly confirmed transfers
Submitting a minute or two after on-chain confirmation gives the provider time to index it properly.
How it actually works
One submission, screened, evaluated, and recorded
A transaction is submitted with the counterparty wallet, the asset, and the amount, and the transaction hash where one exists. The provider returns risk data, rules evaluate it, and the outcome sits on the transaction from then on.
Configuration example
Screening modesWallet, Transaction
Possible outcomesContinue, On hold, Rejected
Recommended screening delay1 to 2 minutes
Feature statusPaid, off by default
Two modes, one decision point
Before it moves, and once it’s confirmed
Wallet screening
Before the transfer takes place
Assesses the counterparty address itself, using blockchain analytics and entity attribution alone, so a decision can be made before funds move.
→
Transaction screening
Once it’s confirmed on-chain
Analyzes the actual transfer, using its transaction hash, for exposure to sanctioned entities, mixers, darknet markets, and stolen funds.
Provider risk panel
Counterparty wallet
Risk scoreLow
Risk level1 of 5
ExposureNone found
AttributionExchange wallet
Reviewing a result
The same detail a compliance team would want to see
Whichever provider is configured, the risk score, risk level, exposure breakdown, and counterparty attribution show up in one place, alongside the transaction it belongs to.
- The rule that actually firedNot just a pass or fail label.
- A full provider panelScore, level, signals, and exposure together.
- A downloadable reportThe same detail, as PDF or CSV.
Working with Travel Rule
One submission, not two compliance checks
Creating a Travel Rule transaction already triggers blockchain screening in the same pass, so a high-risk counterparty is caught before the originator and beneficiary exchange even completes.
- Wallet screening runs automaticallyAs part of creating the Travel Rule transaction.
- Transaction screening joins in once there’s a hashSame submission, same evaluation pass.
- One decision pointCovers blockchain risk and Travel Rule together.
High risk · transaction placed on hold
Wallet screening flagged the counterparty before the transfer settled. Travel Rule data exchange is paused pending compliance review.
Reject
Review details
Related FinHost modules
Part of the same crypto and compliance experience
Get started
Screen the wallet, then the transfer, before risk becomes exposure
Blockchain analytics and Travel Rule, evaluated together, with results reviewable in the Dashboard, the API, or a downloadable report.
ResultContinue
ModeWallet + Transaction
ExposureNone found
Frequently Asked Questions
What’s the difference between wallet screening and transaction screening?
Wallet screening assesses the counterparty address before a transfer takes place, using blockchain analytics and entity attribution alone. Transaction screening analyzes the confirmed on-chain transfer itself, using its transaction hash, for exposure such as sanctioned entities, mixers, or stolen funds.
Does this screen a customer’s own wallet, or just the counterparty?
Just the counterparty: the sender of an incoming deposit, or the receiver of an outgoing withdrawal. Screening a customer’s own wallet, at onboarding for example, is a separate, related service.
What happens if the provider hasn’t indexed the transfer yet?
Blockchain analytics providers index on-chain activity with a short lag that varies by network, so screening submitted immediately after confirmation can come back with no result. Failed requests retry automatically, and submitting with a short delay, typically one to two minutes, gives the provider time to catch up.
Is this the same as Travel Rule screening?
No, but the two run together. A single transaction submission triggers both: wallet and transaction screening for blockchain risk, and the originator and beneficiary data exchange Travel Rule requires, evaluated in the same pass.
Which blockchain analytics providers are supported?
Several leading providers, configured per tenant. Results are available per provider, so switching or comparing providers doesn’t change how the outcome is reviewed.
Is Crypto Blockchain Analysis switched on by default?
No. It’s a paid capability, off until it’s enabled and its rules are installed and tuned to your policy.
How are screening results reviewed?
Four ways: the specific rule that fired on the transaction, a detailed provider panel with risk score and exposure breakdown, structured data via the API, and a downloadable transaction report.