BREAKINGChina-linked hackers step up attacks on European shipping
← Eagle Intelligence News
SanctionsHIGH ALERT

OFAC Sanctions Reversal Backfires: US Waives Iran Oil Restrictions, Creates Compliance Minefield for Shippers and Banks

Eagle Intelligence AI·Eagle Intelligence·March 22, 2026 · 12:05 UTC·6 min read
Why This Matters

US Treasury issues General License permitting sale of Iranian oil loaded through April 19, attempting to ease prices; but opaque OFAC waiver terms create ambiguity for correspondent banks, maritime financiers, and traders on what transactions actually qualify for exemption.

OFAC Sanctions Reversal Backfires: US Waives Iran Oil Restrictions, Creates Compliance Minefield for Shippers and Banks

Advertisement

On March 20, 2026, the U.S. Treasury Department's Office of Foreign Assets Control (OFAC) issued General License D-2, authorizing the sale of Iranian crude oil and petroleum products loaded on vessels on or before March 20 through April 19, 2026. The stated objective: unlock 140 million barrels of stranded Iranian oil to help moderate global crude prices. The practical result: a compliance nightmare for maritime financiers, correspondent banks, and trading houses now forced to navigate ambiguous statutory language in a sanctions enforcement environment where penalties have historically reached USD 1.5 billion per violation (HSBC 2012) and criminal prosecution remains on the table for significant oversights.

The license language itself is the problem. OFAC permits all transactions ordinarily incident and necessary to the sale, delivery, or offloading of Iranian-origin crude on designated vessels (emphasis added: even vessels previously blocked). But OFAC does not define incident and necessary. Does a 15-day letter of credit issued by a Bank of America correspondent facility qualify as ordinarily incident? Does it? It arguably does—the LC is necessary for payment clearing. But does an 18-day LC (if the financing bank processes slowly) fall outside the temporal window and thus violate the license? No guidance exists. OFAC has historically interpreted ambiguity conservatively in enforcement, meaning banks operating under this license are effectively making probabilistic compliance judgments with incomplete information.

Second, the vessel designation creates a discrete enforcement vulnerability. The license permits transactions on vessels loaded before March 20 but does not specify how vessels are identified for exemption purposes. Is a vessel legally cleared if it carried Iranian oil three weeks prior to March 20 but is now in port being repainted with a new flag and identity? What if the vessel's original manifest indicated Iranian origin but the ship is now claiming transshipment from a UAE middleman who purchased the oil from Iran? The license exempts Iranian-origin crude, not crude that touched Iranian ports. This distinction matters critically for P&I clubs and maritime liens: if a vessel is flagged as Iranian-origin but the actual load-point was a third-party hub, does the license apply? Each answer requires forensic investigation that most maritime brokers lack capacity to conduct.

Third, the correspondent banking layer is particularly exposed. A typical crude oil sale involves 4-7 financial intermediaries: the exporting bank (Iranian), the shipping bank (likely a UAE or Singapore institution), the correspondent clearing bank (JPMorgan, HSBC, or Bank of New York Mellon), the trading intermediary (Trafigura, Vitol, or similar), and the importing bank. Each intermediary faces discretionary compliance obligations under OFAC regulations 31 CFR Part 501. OFAC does not exempt correspondent banking from due-diligence requirements simply because a General License exists—the license only permits the underlying transaction. The bank must still verify that the transaction is consistent with the license terms, which requires verifying vessel origin, bill-of-lading authenticity, shipper identity, and ultimate buyer nationality (some categories of end-users like Chinese national oil companies face additional restrictions not fully exempted by the license). This verification burden has historically required 15-25 business days of investigation for a single transaction. With 140 million barrels potentially moving, that requires a verification infrastructure that correspondent banks simply do not have.

Fourth, the temporal specificity creates a cutoff risk. The license covers oil loaded before March 20. But shipping manifests, bills of lading, and official vessel records often reflect load-dates that are disputed or ambiguous. A ship that loaded oil on March 19 but did not clear port until March 22 presents a classic compliance edge case: was it loaded before the cutoff (yes, on March 19) or was it loaded after (arguably, March 22 is the effective load-date for port authority purposes)? OFAC enforcement has historically treated manifests as the authoritative document, but actual load operations often span multiple days. Without explicit guidance, compliance officers face a binary choice: reject the transaction (forgoing profitable opportunity) or approve with elevated audit risk.

Fifth, and most critically, the license contains an implicit moral hazard. By authorizing Iranian oil sales through April 19, OFAC is betting that the revenue accruing to Iranian sellers will not materially increase Iran's war financing capability. But maritime intermediaries lack visibility into beneficial ownership. A bill of lading may show a UAE trading company as the buyer, but the beneficial owner could be an IRGC-linked front entity. Treasury Secretary Bessent acknowledged this explicitly, stating that Iran would face difficulty accessing revenues from oil sales. But he provided no enforcement mechanism to prevent it. In practice, Iranian entities can structure transactions through Kuwait, Oman, or Singapore intermediaries to access proceeds that OFAC intended to keep frozen. Compliance officers face a downstream enforcement risk: if OFAC later discovers that Iranian SDN-listed entities accessed revenues through intermediary transactions, will the correspondent banks and trading houses be held liable for participating in those transactions even if they relied on OFAC's General License?

Critiques from sanctions experts are sharp. David Tannenbaum, director of Blackstone Compliance Services, told the BBC: Essentially were allowing Iran to sell oil, which could then be used to fund the war effort. The remark captures the fundamental tension: OFAC is attempting to depoliticize energy markets by treating Iranian oil as fungible product rather than a geopolitical weapon. But sanctions are inherently political instruments. Once you authorize Iranian oil sales, you cede control over downstream capital flows. The license does not require that Iranian proceeds be frozen in escrow or transferred to third-party trustees. It simply permits the sale with the hope (not the guarantee) that Iran cannot spend it. This is not enforcement; it is wishful thinking embedded in regulatory text.

From a maritime financing perspective, the license creates a duration mismatch risk. Iranian crude typically moves through 90-120 day payment terms (importer pays on delivery). The license expires April 19. What happens to transactions initiated before April 19 but clearing payment after April 19? Are they still OFAC-compliant? The license language does not address post-expiration payment, leaving banks with a temporal discontinuity: they may have extended credit to finance a transaction authorized under the license, but the settlement occurs after the license expires and under the assumption of prior sanctions regimes. Recall of credit or triggering of letters of credit creates a cascading default scenario that correspondent banks want to avoid but may be forced into if OFAC enforcement tightens.

The practical impact on maritime trade: many correspondent banks are simply refusing to process Iran-linked transactions despite the General License, treating the license as legally ambiguous and operationally risky. This effectively nullifies the license's intent. Traders report that major Western banks will not issue LCs for Iranian oil even with OFAC authorization, forcing transactions into non-Western banking channels (Singapore, Dubai, Hong Kong), which creates systematic sanctions leakage. Iran accesses its oil proceeds through non-compliant intermediaries, defeating the purpose of the license while avoiding correspondent banking scrutiny. OFAC's attempt to granularly permit Iranian oil has instead driven the trade into darker channels.

The compliance lesson for maritime operators: General Licenses are not safe-harbor provisions. They are carve-outs that create new enforcement vectors. Any bank or trader participating in OFAC-licensed transactions should maintain contemporaneous documentation of compliance verification, including vessel identity corroboration, beneficial ownership diligence, and license-terms alignment review. The burden of proof has shifted: the bank must affirmatively demonstrate that it complied with the General License, not that OFAC must prove it did not. In a regulatory environment where penalties now reach billions, this burden is non-trivial.

Advertisement

⚠️ Intelligence Disclaimer: This analysis is produced by Eagle Intelligence's AI-assisted automated analysis system and is provided for informational purposes only. See our editorial standards. It is not a substitute for official maritime safety advisories from UKMTO, MSCHOA, IMO, or flag state authorities. Operational decisions should always be based on official guidance and professional judgment. Eagle Intelligence accepts no liability for any loss arising from reliance on this content.

Tracked actorsUS OFAC

Get Eagle maritime risk alerts by email

Live chokepoint status, war-risk shifts, and the daily maritime wire, straight to your inbox. Free.

📰 Related Analysis

Comments & Corrections

0Spot an error? Flag it below ↓

Leave a comment

All comments moderated for quality

Be the first to comment on this story
Corrections policy: Flag inaccuracies using the ⚠️ Correction type. Eagle Intelligence will review flagged corrections. Verified corrections result in an article update with a notice appended. Comments are stored locally in your browser and are not shared with other readers.