Connect identity screening to onboarding
Submit known person or organization details from your server and retain the result reference. Keep the user journey explicit when a check is incomplete.
Sanctions screening for crypto businesses
Keep customer-name screening separate from on-chain analysis.
Screen selected crypto customers and business counterparties against supported sources, with a clear review path and ongoing monitoring of retained identities.
API and compliance dashboard included in every plan.
SanctionsKitIllustrative workflow
Customer onboarding
Known identity
Selected lists
Review path
Completed screeningContinue your policy workflow
Potential matchInvestigate in the dashboard
Identity verification and transaction monitoring remain separate.
Built around your work
A wallet string is not the whole customer identity.
Customer onboarding, institutional relationships, and on-chain transfers raise different questions. A name-screening result should not be presented as blockchain tracing, wallet ownership verification, or a complete transaction-risk decision.
Investigate candidates with source evidence
Compare the customer identity with the actual source record. A score or a shared name does not establish that the customer controls a listed wallet.
Rescreen selected relationships
Maintain relevant customer and partner identities under monitoring. Update the retained subject when reliable identity facts change and assign new evidence for review.
A practical use case
Keep customer-name screening separate from on-chain analysis.
Screen selected crypto customers and business counterparties against supported sources, with a clear review path and ongoing monitoring of retained identities.
The review challenge
Customer onboarding, institutional relationships, and on-chain transfers raise different questions. A name-screening result should not be presented as blockchain tracing, wallet ownership verification, or a complete transaction-risk decision.
How SanctionsKit helps
Submit known person or organization details from your server and retain the result reference. Keep the user journey explicit when a check is incomplete. Compare the customer identity with the actual source record. A score or a shared name does not establish that the customer controls a listed wallet.
- 01
Separate the control types
Map customer screening, wallet analytics, transaction behavior, and other required checks to the systems that actually perform them.
- 02
Handle identity outcomes
Route potential matches, completed no matches, and errors to distinct paths. Keep candidate evidence available to the authorized analyst.
- 03
Maintain the relationship record
Connect retained results, review notes, and monitoring to the internal customer reference. Preserve separate on-chain and legal analyses with their scope.
Evaluate the fit
Screening questions for cryptocurrency.
Does SanctionsKit trace cryptocurrency transactions?
No. It does not provide blockchain analytics, wallet clustering, or on-chain transaction monitoring.
Does a no-match name check approve a wallet transfer?
No. It only describes the selected-source identity check. Wallet, activity, jurisdiction, and authorization questions remain separate.
Can organizations and individual users be screened?
Yes, with the correct supported entity type and selected coverage. Use reliable identity details and do not infer wallet ownership from a name.
Does this implement Travel Rule compliance?
No. Required Travel Rule or other digital-asset compliance workflows need separate evaluation and implementation.
See SanctionsKit in action
Explore screening and review for cryptocurrency.
Try the interactive demo with synthetic examples. Compare plans for your team’s screening volume.