Sanctions Exposure From Iran's Strait of Hormuz Toll Regime

The sharpest legal impact of the Strait of Hormuz closure and toll regime is not whether a ship can find a commercial way through. It is that, under the cited U.S. sanctions materials, there is no clean payment route into Iran’s “safe passage” system, and after OFAC’s May 29, 2026 expansion of FAQ 1249 the risk is no longer limited to sending money. Receiving services, safe-passage guarantees, or other benefits from the Government of Iran without payment can itself create sanctions exposure, as summarized in the May 29 FAQ update coverage and tied to the surrounding OFAC guidance.[1]

For owners, charterers, traders, banks, insurers, P&I clubs, and counsel, that moves the practical question from “how do we draft the sanctions clause?” to “can anyone involved in this voyage document, today, that the vessel, its ownership chain, its operator, its cargo links, and the proposed passage arrangement have cleared current primary-source screening?” This article is a compliance analysis of public sanctions materials, not legal advice.

The May 29 FAQ expansion closes the “free guarantee” gap

Before the May 29 expansion, many operational conversations would naturally have centered on the act of payment: who pays, in what currency, through which account, and under which party’s sanctions perimeter. The updated FAQ 1249 framing matters because it reaches the other side of the same transaction. If Iran, or an Iranian instrumentality, provides the safe-passage service or guarantee and the vessel receives the benefit without payment, that does not make the arrangement safe under the cited U.S. sanctions analysis.[1]

That point is operationally uncomfortable because maritime decisions are made under time pressure. A vessel may be approaching a chokepoint, a charterer may be asking whether performance is still possible, an insurer may be asked to confirm cover, and a bank may be waiting on a payment instruction. The legal control cannot be a promise to revisit sanctions risk after the transit. The relevant screening has to occur before the benefit is accepted.

Payment form does not solve the sanctions problem

OFAC’s May 1, 2026 alert is the starting point for payment analysis. It warned that sanctions risk attaches to any form of toll or facilitation payment connected to the Hormuz safe-passage regime, regardless of payment method. The alert specifically called out nominal charitable payments to the Iranian Red Crescent Society, Bonyad Mostazafan, or Iranian embassy accounts, alongside other methods of providing value.[2]

That warning matters because sanctions evasion rarely arrives labeled as evasion. It may arrive as a reimbursement, an “administrative fee,” an agreed deduction from freight, a cargo-side concession, a third-party charitable remittance, a digital-asset transfer, or a promise to make Iran whole through some later commercial adjustment. The compliance question is not whether the invoice uses the word toll. It is whether value is being provided in connection with the safe-passage demand.

Reuters reported the same day that the U.S. Treasury had warned shippers not to pay Hormuz tolls even in the form of charity.[3] That reporting is useful for market context, but the operative control should still be traced back to OFAC’s own alert and FAQ materials. A sanctions file that relies only on a news summary is a weak file when a voyage, claim, payment, or enforcement inquiry later turns on what the agency actually said.

PGSA’s SDN designation hardens the counterparty issue

The May 27, 2026 designation of the Ports and Gulf Security Authority, or PGSA, as a Specially Designated National is the next control point.[1] Once a body positioned in the safe-passage architecture is on the SDN List, the problem is not limited to an abstract sovereign-demand risk. It becomes a named-counterparty screening problem, with all the timing and documentation burdens that follow.

The reported toll structure included demands of up to $2 million per vessel, and Reuters reported on the U.S. warning against payment routes in that context.[3] Those figures should be handled as reported market and government-warning context, not as proof that every vessel faced the same demand or that every threatened transit produced an actual payment. The compliance conclusion does not need that broader inference. It is enough that OFAC warned against providing value and that the PGSA designation then made the named-entity problem more concrete.

For a commercial team, the designation changes the escalation path. A sanctions clause may let a party refuse performance when sanctions are triggered, but the business still has to identify the trigger in time. That means checking current SDN data, confirming whether the safe-passage communication, account, agent, port authority, guarantor, or intermediary is linked to PGSA or another sanctioned person, and preserving evidence of the screening decision as of the date the instruction was given.

Why contract language may lag the facts

Standard sanctions clauses are still useful. They allocate responsibility, create disclosure duties, preserve termination or suspension rights, and give commercial teams a route to stop performance without inventing a fresh theory at the worst moment. But clause language does not by itself screen a vessel, identify a newly designated authority, or resolve whether a safe-passage benefit has already been received.

DAC Beachcroft has pointed to a practical difficulty with BIMCO standard sanctions clauses in this setting: the “actual and demonstrable involvement” threshold can be hard to satisfy in a fast-moving designation environment.[4] That is the kind of phrase that looks reassuring on paper and becomes awkward when a vessel is waiting, a port agent has incomplete information, and a counterparty demands a decision before every beneficial-owner, operator, and transfer-history question has been resolved.

The legal drafting problem is therefore downstream of the verification problem. If the facts are stale, the clause will be asked to carry more certainty than the operation can supply. Counsel can improve the clause, but the more immediate control is a documented process for checking live sanctions data, vessel identifiers, ownership links, and voyage behavior before performance continues.

Non-U.S. parties should not treat this as someone else’s OFAC issue

Non-U.S. owners, charterers, traders, brokers, insurers, and law firms may be tempted to frame the toll regime as a U.S.-person problem unless dollars, U.S. banks, or U.S. insurers are directly involved. That is too narrow. The cited materials identify secondary-sanctions exposure for non-U.S. parties that provide material support or value to sanctioned Iranian activity, and the PGSA designation increases the risk that a transaction once described as a passage arrangement is in fact support for a designated person.[1][2]

The U.K. comparison reinforces the same operational lesson from a different direction. Legl’s 2026 briefing describes U.K. sanctions strict liability under the Sanctions and Anti-Money Laundering Act 2018 and notes that there is no good-faith or ignorance defense in that framing. It also flags SRA Code of Conduct Rule 8.1 duties around verifying client identity and alerting OFSI on grounded suspicion.[5] Those points do not make U.K. law identical to OFAC practice. They do show why a non-U.S. legal or maritime team cannot reduce the issue to “we are not the payer.”

Insurers face a particularly unforgiving sequence. Cover may be requested before all sanctions facts are known; a claim may arise after a transit; and a later designation or vessel-history finding may force a review of what the insurer knew, what it checked, and when. Banks and payment intermediaries face a parallel problem when a payment description is cleaner than the underlying passage arrangement.

The screening burden is vessel-level, not just name-level

A counterparty name search is not enough in Gulf trade under these conditions. The vessel may have changed flag, ownership, manager, operator, AIS pattern, cargo route, or transfer behavior. Legl’s 2026 briefing estimated a shadow-fleet universe of more than 430 tankers, with about 87% already designated, and described more than 1,800 OFAC-designated IMO-registered vessels after a greater than 46% single-year increase.[5] Because that briefing is vendor-published, those figures are best used as attributed indicators of scale, not as a substitute for checking current OFAC, State Department, IMO, and other primary records at the time of the voyage.

The U.S. State Department’s February 2026 release on illicit traders of Iranian oil and the shadow fleet supplies the broader enforcement context: vessel-linked sanctions are not a side issue in Iranian-oil enforcement; they are one of the main ways sanctions authorities track and disrupt trade.[6] In that environment, a vessel that is not named on yesterday’s list may still require scrutiny because its operator, beneficial owner, cargo source, or transfer history points toward a prohibited network.

The practical file should be built around the voyage, not the contract form. At minimum, a defensible screening record for a Hormuz-linked movement should show:

• The vessel’s IMO number, current and recent names, flag history, registered owner, beneficial owner where known, technical manager, commercial manager, operator, charterer, and relevant brokers or agents.
• Screening against current OFAC SDN and sanctions lists, including vessel records and aliases, with date and time captured.
• Checks against U.S. State Department designation releases and any other primary sanctions sources relevant to the parties’ jurisdictions.
• Review of cargo links, including whether the cargo, seller, buyer, shipper, receiver, or financing chain suggests Iranian oil, sanctioned Iranian trade, or a designated network.
• AIS and voyage-pattern review for indicators such as unexplained gaps, spoofing concerns, unusual routing, or behavior inconsistent with the stated commercial purpose.
• Review of recent reflagging, renaming, ownership transfers, and management changes.
• Review of ship-to-ship transfer indicators where relevant, especially where the cargo history is central to the risk assessment.
• A documented decision on whether any safe-passage communication, guarantee, agent instruction, account, or demanded undertaking involves PGSA, the Government of Iran, or another sanctioned person.
• A stop-work or escalation record showing who reviewed the hit, who approved any continuation, and what source evidence supported that decision.

What to do when the screen is not clean

A sanctions hit does not always mean the same thing. It may be a true SDN match, a weak-name similarity, a vessel alias, a past ownership link, a cargo concern, or an unresolved behavioral indicator. The response should separate those categories instead of treating every alert as either a false positive or a commercial emergency.

The records should show the source checked, the date checked, the identifiers used, the reviewer, the decision, and the reason for any override. That is basic evidence discipline, but it is also where many sanctions files fail. A contract clause says what the parties promised. A screening file shows what the approving person knew before the vessel moved, the payment released, the guarantee accepted, or the cover bound.

The compliance boundary

The cited materials do not solve the Strait of Hormuz closure risk, forecast the next interruption, or tell commercial parties how to perform every Gulf-trade contract. They support a narrower and firmer conclusion. Under OFAC’s May 1 alert, toll or facilitation payments to Iran’s safe-passage regime cannot be made lawful by changing the form of value. Under the May 29 expansion of FAQ 1249, accepting a safe-passage service or guarantee without payment is also a sanctions exposure point. With PGSA designated as an SDN as of May 27, 2026, the counterparty problem is no longer theoretical.[1][2]

The defensible posture is current, documented, primary-source vessel screening before and during performance. If the next movement depends on an Iranian toll, a PGSA-linked instruction, a disguised value transfer, or an unpaid safe-passage benefit, the file should not be looking for reassurance. It should be looking for authority to stop.

References

1. OFAC Expands Guidance on Strait of Hormuz "Safe Passage" Restrictions — Baker McKenzie Global Sanctions Blog.
2. OFAC Alert — U.S. Department of the Treasury, Office of Foreign Assets Control, May 1, 2026.
3. US Treasury warns shippers not to pay Hormuz tolls, even in form of charity — Reuters, May 1, 2026.
4. Strait of Hormuz Tensions: Sanctions and Safe Passage Payments — DAC Beachcroft.
5. Navigating the Storm: Shipping Law Firms, Vessel Sanctions & the Crisis in the Strait of Hormuz — Legl.
6. Sanctions to Combat Illicit Traders of Iranian Oil and the Shadow Fleet — U.S. Department of State, February 2026.