Blocked Person

Overview

Blocked Person is a person or entity whose property and interests in property must be frozen or blocked under an applicable sanctions authority. Its operational purpose is to prevent prohibited dealings and preserve affected property pending authorization, delisting, or other lawful resolution. It should be considered alongside Sanctions Match. The relevant distinction is a person merely appearing in an alert or possible sanctions match, because blocking obligations depend on applicable law, ownership rules, jurisdiction, and confirmed identity.

A typical workflow is as follows: A sanctions control identifies a potential relationship or transaction, compares identity and ownership data, determines jurisdictional applicability, and escalates the case. Once confirmed, the organization stops prohibited activity and follows blocking, reporting, and recordkeeping requirements.

Core controls include current sanctions data, ownership analysis, geographic and product scoping, legal review, immediate restriction capabilities, reporting procedures, and controlled unblocking.

In payment and crypto operations, A blocked person may be a customer, beneficiary, originator, wallet owner, counterparty, or an entity owned at or above an applicable threshold by other blocked persons.

Evidence should include identity attributes, list record, ownership chain, program authority, jurisdictional nexus, transaction details, decision time, blocked assets, reports, licenses, and later status changes. Failure to recognize indirect ownership or program-specific rules can cause prohibited processing even when the entity is not separately named on a list.

It is used to prevent prohibited dealings and preserve affected property pending authorization, delisting, or other lawful resolution. It differs from a person merely appearing in an alert or possible sanctions match, because blocking obligations depend on applicable law, ownership rules, jurisdiction, and confirmed identity.