Do all OFAC programs automatically block transactions?

No, not all OFAC programs automatically require the blocking of transactions. OFAC regulations are tailored to the objectives of each sanctions program. In some cases, the president determines the need for comprehensive asset freezes, while in others, more limited measures are applied, such as import or export bans. Some OFAC programs only require the rejection of transactions without asset blocking. For example, a payment between two foreign companies involving Iran would be rejected by a U.S. bank but not blocked. It is important to study the specific requirements of each sanctions program on the OFAC website.

Rejecting differs from blocking by stopping a transaction, rather than seizing property. When a transaction is rejected, the institution simply refuses to process it and returns the funds to the originator — no property is seized, and no OFAC blocking report is required, though the rejection itself must still be reported to OFAC within 10 business days under most programs. When a transaction is blocked, the institution takes control of the funds or property, places them in a segregated blocked account, and cannot return them to anyone without OFAC authorization. The key distinction: rejection sends the money back where it came from; blocking keeps the money in place, frozen, indefinitely.

The answer depends entirely on the underlying sanctions program and the parties involved, not on the institution’s own judgment. As a general framework:

Because the correct action varies by program — Cuba, Iran, and Russia sanctions, for instance, each have different blocking and rejection triggers — compliance teams cross-reference OFAC’s program-specific regulations (31 CFR Chapter V) rather than applying a single universal rule.

Some payment processors and buy-now-pay-later platforms display a message referencing an “OFAC reject” when a transaction is automatically declined by their sanctions screening system — typically because a name, address, or other detail in the transaction matched (or closely resembled) an entry on an OFAC list. This is usually an automated screening decision made by the platform’s compliance system, not a formal OFAC enforcement action against the individual. In many cases it reflects a false-positive name match rather than an actual sanctions issue. If this happens, the platform’s own customer support is generally the first point of contact to clarify the reason for the decline.

Separately from transaction blocking, some websites and online services restrict access based on the visitor’s IP address if it originates from a comprehensively sanctioned country (such as Cuba, Iran, North Korea, or Syria) or a sanctioned region. This is a risk-avoidance measure taken by the business itself — often broader than what OFAC strictly requires — to avoid inadvertently providing services, software, or content to a sanctioned jurisdiction. It is distinct from the blocking or rejecting of a financial transaction and applies to access to digital products and services rather than to funds.

Prohibited transactions generally fall into a few categories, though the specifics vary by program:

Because prohibitions differ by program, the same activity can be entirely lawful under one sanctions regime and prohibited under another.