A payment stop can mean several different things
A delayed payment does not establish that its sender is sanctioned. A screening system can flag a similar name, a geographic reference, an intermediary bank or an ownership relationship. Each raises a different factual question. OFAC’s name-matching guidance begins by identifying the actual list or sanctions program involved and then examining the quality of the match. A commercial screening product may combine OFAC material with other agencies’ lists and the bank’s own restrictions. Those categories do not share one legal consequence. [1]
The distinction matters economically. A temporary review can delay a supplier’s working capital, while a legal blocking requirement can immobilize funds for an indefinite period. A commercial decision to decline a payment is different again. Treating all three as an OFAC freeze obscures who made the decision, what evidence supports it and what could change the outcome. This article describes the decision structure, rather than determining the legality of a particular payment.
Identity comes before disposition
A name is only one identifier. Date of birth, addresses, nationality, aliases and identifying numbers can help distinguish people; corporate registration information can help distinguish entities. Missing information creates uncertainty rather than proof of a match. Transliteration and common surnames make this particularly important across languages. OFAC’s guidance explicitly recognizes and the need to compare available identifiers. [1]
Analysis: two customers can share the same name while having different birth dates and residences. Conversely, a company can change its trading name while retaining the same registration and owners. A process that treats the first coincidence as conclusive and the second name change as clearance would make opposite errors. Matching quality concerns the evidence connecting the transaction participant to the target, not simply the number of letters that a search engine highlights.
Nationality alone is not a general test for blocked status. Program rules, territorial restrictions and government definitions can matter, but they need to be identified specifically. A person’s heritage is not a substitute for that analysis. Nor does the absence of a direct list match settle the question, because some entities are blocked through ownership or other program provisions without a separate listed entry.
The ownership rule reaches beyond the named entity
OFAC’s 50 Percent Rule treats an entity as blocked when blocked persons own 50% or more in aggregate, directly or indirectly as the rule defines that relationship. Ownership interests of blocked persons can aggregate even when those persons are blocked under different programs. Control below that ownership threshold does not automatically block the entity under this rule, although separate sanctions or dealings involving the blocked controller may still prohibit a transaction. [2]
A hypothetical company has two blocked shareholders owning 30% and 25%. Their interests total 55%; neither individually has a majority. This illustration assumes accurate ownership evidence and no authorization. It concerns no real company.
OFAC’s examples show that a blocked owner’s 50% stake in a first company blocks it; that company’s 50% stake in a second can then block the second. Multiplying 50% by 50% to obtain 25% misses the treatment of the intermediate entity. [2]
Blocking preserves property while restricting its use
Blocking freezes property; it does not itself transfer ownership to the United States. The owner retains title, but transfers and other dealings are restricted unless authorized. OFAC describes property broadly, including money, securities and other tangible or intangible interests. The relevant jurisdictional connection is essential: the blocking obligation concerns property within the United States or in the possession or control of a U.S. person under the applicable authority. [3]
Analysis: a blocked balance is therefore not ordinary revenue for the bank holding it. It is also not a fine paid by the customer. These descriptions would confuse custody, ownership and enforcement. A financial institution can hold a balance that it cannot disburse, and the customer can remain its owner without being free to spend it. That unusual combination explains why records linking the property to its owner and blocking basis remain important long after the initial payment review.
For blocked funds, OFAC’s guidance describes interest-bearing blocked accounts and records sufficient to trace specific amounts. Authorized debits depend on the applicable rules or permission; an ordinary return to the sender is not a substitute for blocking. [4] Operationally, the bank needs to distinguish a ledger entry acknowledging the customer’s claim from a permission to honor the customer’s withdrawal request.
Rejection is a different legal outcome
Some transactions are prohibited without involving an interest that must be blocked. OFAC distinguishes rejection, where the transaction is not processed and is returned, from retention of blocked property. It also emphasizes that not every sanctions program imposes comprehensive blocking. Restrictions can instead concern particular activities or kinds of dealings. [4]
A hypothetical payment might therefore follow two different paths. In the first, a blocked person has an interest in funds received by a U.S. bank and no authorization applies; the funds remain blocked. In the second, the service itself is prohibited under a particular program but there is no blockable interest; rejection may be the applicable disposition. The same dollar amount and payment rail do not establish which path is correct. The program, participants and property interests do.
This is why the phrase stopped for sanctions is incomplete. It can describe an unresolved alert, a rejected transaction or blocked property. A record that identifies the stage and legal basis conveys substantially more than a generic status label. That distinction also prevents an institution from mistakenly treating a rejected payment as an asset it must continue to hold.
Authorization is scoped, not universal
An OFAC general license authorizes a category of otherwise prohibited transactions subject to its conditions; a specific license provides written permission for a particular transaction or activity. OFAC’s licensing explanation distinguishes these mechanisms. [5] Neither means that every transaction involving the same customer becomes permissible. Dates, parties, purpose and excluded activities can determine whether an authorization fits.
Analysis: a permission covering payment for one category of goods does not logically establish permission to repay an unrelated loan. Likewise, a license that has expired cannot support a later transaction merely because an earlier payment succeeded. An operational record needs a connection between the authorization and the activity being processed. A license application and an issued license are different events; the filing of a request does not itself demonstrate that permission exists.
Reporting and customer communication are separate questions
OFAC’s reporting guidance identifies a ten-business-day deadline for initial blocking and rejection reports. [6] Reporting is distinct from disposition: a filed report does not make a prohibited payment permissible or turn a mistaken match into a valid one. This article does not reproduce every reporting field, exception or delivery procedure, which can change independently of the underlying sanctions program.
OFAC also permits institutions to notify customers that funds have been blocked and explains that an application for release may be available. [4] This differs from treating all compliance-related information as categorically secret. Clear descriptions of what happened can help customers distinguish a legal restriction from missing transfer details, without promising a release that the institution cannot authorize.
The enduring lesson is that accurate sanctions decisions require both legal specificity and sound facts. Underblocking can permit prohibited activity; overblocking can impose real costs on people who are not targets. Sources checked October 4, 2026 describe the general framework. Lists, program restrictions and licenses can change quickly, so the examples intentionally make no claim about the current status of a named country, business or individual.
Sources
- OFAC FAQ 5, assessing name matchesOfficial sourceBack to text: ↑1↑2
- OFAC FAQs 398–402, entities owned by blocked personsOfficial sourceBack to text: ↑1↑2
- OFAC FAQ 9, meaning of blocked propertyOfficial sourceBack to text: ↑
- OFAC blocking and rejecting transactions FAQsOfficial sourceBack to text: ↑1↑2↑3↑4
- OFAC FAQ 74, general and specific licensesOfficial sourceBack to text: ↑
- OFAC reporting FAQs, including FAQ 49Official sourceBack to text: ↑