On September 14, 2026, the U.S. Treasury's Office of Foreign Assets Control (OFAC) issued Venezuela-related General License 52C authorizing certain transactions involving Petróleos de Venezuela, S.A. (PDVSA), amended FAQ 1245, and escalated VTB Bank Public Joint Stock Company by tagging it under the Iran sanctions program. The action, announced under Operation Economic Outcast, adds a Tehran address to VTB's listing and marks the bank as subject to secondary sanctions, expanding exposure well beyond U.S. persons to any foreign financial institution that touches it.
VTB Bank was already blocked on the SDN and Sectoral Sanctions Identifications lists under the Russia and Ukraine programs (Executive Order 13662 Directive 1 and EO 14024). The September 14 update adds the [IRAN-EO13902] program tag, a Tehran, Iran address, and the flag "Additional Sanctions Information, Subject to Secondary Sanctions." This is a cross-program escalation: a systemically important Russian bank is now also an Iran-sanctions target, with secondary-sanctions reach into non-U.S. counterparties.
What does the Iran tag on VTB Bank change for foreign banks?
It converts VTB from a primary-sanctions problem into a secondary-sanctions problem for everyone else. Under secondary sanctions, a non-U.S., non-Russian financial institution that knowingly facilitates a significant transaction for VTB can be cut off from the U.S. financial system, including loss of correspondent account access, even where no U.S. person or U.S. dollar leg is involved. The authorities cited are EO 14024 Section 11 alongside the Ukraine-/Russia-Related Sanctions Regulations at 31 CFR 589.201 and 589.209, and now the Iran program under EO 13902.
For European, UK and Asian banks that still route residual VTB-related flows through non-USD channels, the Iran tag raises the screening stakes: the same transaction can now trigger both Russia and Iran program logic, and Iran secondary-sanctions exposure historically carries a lower evidentiary bar in OFAC enforcement. Screening engines must treat the Tehran address and the new program tag as material risk indicators, not cosmetic list metadata.
What does General License 52C authorize for PDVSA?
GL 52C, "Authorizing Certain Transactions Involving Petróleos de Venezuela, S.A.," re-opens a narrow, defined band of PDVSA-related activity after the prior 52-series authorization (52B) expired in December 2025. The amended FAQ 1245 explains the license's scope and boundaries. Energy traders, banks and insurers with existing Venezuela exposure must re-map which PDVSA transactions are now authorized, which remain prohibited, and which depend on a specific license.
Because GL 52C is general rather than specific, it carries conditions: every authorized transaction still requires compliance with the rest of the Venezuela Sanctions Regulations, other OFAC programs (now including the Iran tag where VTB is a counterparty), and the 50 Percent Rule. A PDVSA authorization does not immunize a transaction that also touches a newly Iran-tagged VTB account.
Who must act, and by when?
The list update is effective immediately as of September 14, 2026. Three groups face concrete obligations now:
- Sanctions screening owners at global banks: push the updated SDN and SSI entries for VTB (new Tehran address, Iran program tag, secondary-sanctions flag) to all screening and transaction-monitoring systems today, and re-run retrospective screening over the look-back window your risk appetite mandates.
- Energy and commodities compliance teams: reconcile open PDVSA positions against GL 52C and amended FAQ 1245, and flag any flow where a VTB entity sits in the payment chain.
- Correspondent banking and de-risking units: review VTB nested-correspondent exposure and document the secondary-sanctions risk decision, since enforcement risk no longer depends on a U.S. nexus.
| VTB Bank listing field | Before September 14, 2026 | After September 14, 2026 |
|---|---|---|
| Program tags | EO 13662, EO 14024 (Russia/Ukraine) | EO 13662, EO 14024, EO 13902 (Iran) |
| Secondary sanctions | Russia secondary (31 CFR 589.201/.209) | Russia secondary + Subject to Secondary Sanctions |
| Addresses | Russia, India, China | Russia, India, China, Tehran, Iran |
Subscribe to the free newsletter
Next steps: verify your screening vendor has ingested the September 14 SDN/SSI delta, confirm that VTB's Iran tag and Tehran address are firing in your transaction-monitoring rules, brief relationship managers on the secondary-sanctions shift, and re-document any PDVSA activity against GL 52C and FAQ 1245 before the next risk committee. Obsidian surfaces OFAC list changes and general-license issuances the moment they publish, per jurisdiction, so compliance teams can push the delta before the next clearing window.
