Sanctions screening

Learn how sanctions screening works, which lists are used, and how it can affect onboarding, payments, and crypto transfers.

Sanctions screening is the process of comparing customers, counterparties, suppliers, and transactions against official sanctions lists issued by governments and international bodies. Its purpose is to ensure that a business does not deal with individuals, entities, or jurisdictions that are prohibited or restricted from participating in financial activity.

For regulated financial institutions and crypto services, sanctions screening is a core part of AML/CFT compliance. It helps prevent asset freezes, financial prohibitions, trade bans, and other sanctions breaches that can lead to fines, criminal liability, and reputational damage.

Why sanctions screening is required

Sanctions are legal and economic restrictions imposed by governments or international organisations. They can include:

  • Asset freezes and financial prohibitions.
  • Trade restrictions and embargoes.
  • Travel bans and visa restrictions.
  • Restrictions on specific sectors, goods, or services.

Financial institutions and other obliged entities are generally required to:

  • Screen customers and transactions against relevant sanctions lists.
  • Block or reject transactions involving sanctioned parties where required.
  • Report potential matches or breaches to relevant authorities.
  • Maintain records and demonstrate compliance to regulators.

Failure to comply can result in significant penalties, loss of licences, and restrictions on access to the global financial system.

Key sanctions lists

There is no single global sanctions list. Organisations typically screen against multiple lists depending on their operations, customers, currencies, and jurisdictions.

Commonly used lists include:

OFAC SDN List (United States)

  • Issued by the U.S. Treasury’s Office of Foreign Assets Control (OFAC).
  • Covers individuals, entities, vessels, and other parties subject to U.S. sanctions.
  • Applies to U.S. persons worldwide and to transactions with a U.S. nexus (for example, U.S. dollars, U.S.-based systems, or U.S. persons involved).
  • Updated frequently, often multiple times per week.
  • Includes the “50 percent rule”: entities owned 50% or more, directly or indirectly, by one or more sanctioned persons are treated as blocked, even if not explicitly listed.

UN Security Council Consolidated List

  • Issued by the United Nations Security Council.
  • Binding on all UN member states, implemented through domestic law.
  • Covers individuals and entities associated with terrorism, proliferation, and other threats to international peace and security.
  • Updated periodically as resolutions change.

EU Consolidated List

  • Issued by the European Union (Council).
  • Applies to EU member states, EU citizens, and entities within EU jurisdiction.
  • Includes asset freezes and economic restrictions related to various regimes (for example, Russia, Belarus, certain countries and entities linked to terrorism or human-rights abuses).
  • Updated periodically as EU regulations change.

UK Sanctions List (OFSI)

  • Issued by the UK’s Office of Financial Sanctions Implementation (OFSI).
  • Applies to UK persons and entities and activities within UK jurisdiction.
  • Covers a range of regimes, including financial, trade, and travel sanctions.
  • Updated as UK regulations and designations change.

Other national and regional lists

Depending on the business, additional lists may be relevant, such as:

  • National sanctions lists in other jurisdictions (for example, Canada, Australia, Switzerland, Singapore).
  • Sectoral or targeted sanctions related to specific countries, industries, or activities.

A practical rule for cross-border business is often to screen against OFAC, UN, EU, and relevant local lists, but the exact scope depends on the firm’s footprint and legal advice.

When sanctions screening happens

Sanctions screening is typically performed at several points in the customer lifecycle.

At onboarding

Before opening an account or establishing a business relationship, the provider screens:

  • The customer (individual or entity).
  • Beneficial owners and key controllers for corporate customers.
  • Relevant connected parties where required (for example, authorised signatories, major counterparties).

This helps ensure the firm does not onboard a sanctioned party or an entity owned or controlled by sanctioned persons.

At transaction time

For payments, transfers, and crypto transactions, screening may include:

  • The sender and beneficiary.
  • Intermediary banks, payment-service providers, or crypto exchanges involved.
  • In some cases, goods, vessels, or other elements of the transaction.

Real-time screening helps block or reject prohibited transactions before funds move.

Continuous and event-driven screening

Sanctions lists change frequently. Providers therefore:

  • Re-screen existing customers and counterparties when lists are updated.
  • Perform additional screening when risk indicators change (for example, new beneficial owners, change of jurisdiction, adverse news).
  • Monitor for new connections to sanctioned parties that emerge over time.

This ongoing process helps catch designations that occur after onboarding.

How sanctions screening works

While implementations vary, most programmes follow a similar pattern.

1. Data collection

The system collects relevant data for each subject, such as:

  • Full name and any known aliases.
  • Date of birth or incorporation date.
  • Nationality, country of residence, or place of registration.
  • Address and contact details.
  • For corporates: ownership structure, beneficial owners, directors, and key controllers.
  • For crypto: wallet addresses and, where available, entity information behind those addresses.

2. List matching

The system compares this data against enabled sanctions lists using:

  • Exact-name matching.
  • Fuzzy matching to capture spelling variations, transliterations, and minor differences.
  • Rules for known aliases, former names, and alternative spellings.
  • Ownership and control logic (for example, applying the 50% rule for OFAC).

Matches are flagged as alerts for review.

3. Alert review and investigation

Compliance analysts review alerts to determine whether they are:

  • True matches – the customer or counterparty is the same as the sanctioned party.
  • False positives – the names are similar but refer to different individuals or entities.
  • Potential matches requiring more information – additional documentation or clarification is needed.

Analysts may use:

  • Additional identity documents.
  • Corporate registries and ownership charts.
  • Adverse-media and open-source information.
  • Internal knowledge of the customer’s business and activity.

4. Decision and action

Based on the investigation:

  • If there is no match, the alert is closed as a false positive and the transaction or relationship can proceed.
  • If there is a match or strong suspicion, the firm may:
    • Block or reject the transaction.
    • Freeze assets where required.
    • Restrict or terminate the relationship.
    • File a report or notification with the relevant authority, as required by law.

All decisions and rationale are typically documented for audit and regulatory purposes.

Sanctions screening in crypto services

Crypto service providers face similar obligations but must also consider blockchain-specific risks.

Wallet and address screening

Providers may screen:

  • Customer wallet addresses at onboarding.
  • Deposit and withdrawal addresses for each transaction.
  • Counterparty addresses involved in transfers.

Screening tools compare addresses against risk data to detect exposure to:

  • Sanctioned entities or individuals.
  • Known scam operations, darknet markets, mixers, or stolen funds.
  • High-risk services or jurisdictions.

On-chain tracing and clustering

Advanced tools can:

  • Trace fund flows across multiple transactions and chains.
  • Identify clusters of addresses likely controlled by the same entity.
  • Detect patterns associated with sanctions evasion, such as frequent address changes, use of intermediaries, or layering through multiple services.

This helps providers assess whether a wallet or transaction has indirect exposure to sanctioned parties.

Regulatory expectations

Regulators in several jurisdictions have clarified that crypto service providers must:

  • Screen customers and counterparties against relevant sanctions lists.
  • Implement controls to detect and prevent sanctions evasion via crypto.
  • Maintain records and report suspicious or prohibited activity where required.

How sanctions screening affects users

From a user’s perspective, sanctions screening may be visible in several ways.

Onboarding delays or additional requests

A user may be asked for:

  • Additional identity or corporate documentation.
  • Clarification about ownership, controllers, or business activities.
  • Information about source of funds or intended use of the service.

This can happen if the user’s name is similar to a sanctioned party, if they are based in a higher-risk jurisdiction, or if their profile triggers additional checks. It does not necessarily mean they are sanctioned.

Transaction blocks or rejections

Some payments or crypto transfers may be:

  • Blocked or rejected automatically if a party matches a sanctions list.
  • Held for manual review while compliance investigates.
  • Declined where required by law or internal policy.

In such cases, the provider may be legally restricted from sharing detailed reasons with the user.

Account restrictions or closures

In more serious cases, a provider may:

  • Restrict certain products, jurisdictions, or transaction types.
  • Freeze assets where required by sanctions rules.
  • Terminate the relationship and, where required, report to authorities.

These measures are driven by legal obligations and risk management, not by a judgement about the user’s character.

Good practices for users

Users can help avoid unnecessary friction by:

  • Providing accurate and complete information at onboarding.
  • Keeping identity, address, and corporate details up to date.
  • Using official channels only for communications and document submission.
  • Being prepared to explain large or unusual transactions if asked through official channels.
  • Understanding that certain jurisdictions, counterparties, or wallet addresses may be treated as higher risk by compliance systems.

Users should never attempt to obscure their identity, use another person’s details, or route transactions through intermediaries to avoid screening. Such behaviour can itself be treated as a serious red flag.

Spend your
crypto.
Don’t sell it
Join the members who figured it out.