Sanctions screening for crypto businesses: identity and wallet controls

On this page

Name the subject of the control

A customer identity, a company, a wallet address, and an on-chain transaction are different objects. Decide which control your workflow needs before choosing a screening endpoint. A person-name check does not analyze a wallet’s transaction history.

SanctionsKit screens supported submitted subjects against selected sources. It does not provide blockchain tracing, wallet exposure scoring, transaction-pattern monitoring, or a complete virtual-asset compliance program.

Establish the customer identity through a separate process

Use the reliable identifying information your onboarding process has established. Screen relevant legal entities and identified related parties according to policy. A display name or exchange username may not be the person or organization responsible for the relationship.

Keep the identity-verification outcome separate from the sanctions result. Collecting an image or accepting a user declaration does not itself prove that either process has succeeded.

Select and preserve source scope

Choose the authority lists applicable to the relationship and supported by the current service. Preserve the sources and versions in the result. A label such as global screening is not evidence that every relevant list or address source was checked.

Where a workflow depends on specialized address screening or blockchain analysis, record the separate provider, coverage, and conclusion. Do not infer that a name no-match also clears an address or transaction.

Investigate candidates without collapsing the decisions

Synthetic example: a fictional corporate customer’s director has a common-name candidate. The analyst uses known dates, identifiers, and source details to assess identity. The company’s ownership structure remains a separate investigation even after the director’s candidate is resolved.

A confirmed identity requires the appropriate sanctions and activity assessment. A mismatch cannot establish that a wallet, counterparty, or transaction is permissible under other controls.

Keep monitoring aligned with identity changes

Monitor selected continuing customer subjects with defined coverage and a responsible reviewer. New reliable customer details may require updating the subject and conducting a new comparison. A static onboarding name is not a permanently complete customer profile.

SanctionsKit monitoring uses scheduled and qualified source-triggered rescreening. It is not continuous surveillance of wallet activity. Plan the usage allowance and operational handling of unavailable coverage or failed rescreens.

Maintain a joined but distinct evidence record

The cryptocurrency solution supports the identity-screening part of the workflow. Preserve links to other controls rather than presenting all results as one unexplained risk score.

Record the customer identity and the separate wallet or transaction references.
State the source coverage behind each control.
Retain source candidates, identity decisions, and business actions independently.
Identify missing or failed checks before making a downstream decision.
Keep secrets and sensitive identity evidence out of routine application logs.