US Sanctions Iran's BitBank Over IRGC Bitcoin Transfers
The US Treasury's Office of Foreign Assets Control has designated Iranian crypto exchange BitBank, accusing it of routing Bitcoin payments collected through a coercive Strait of Hormuz maritime scheme directly to the Islamic Revolutionary Guard Corps. For accounting firms, auditors, and CFOs managing digital asset exposure, the action is a sharp reminder that crypto exchanges operating outside the regulated perimeter can appear in transaction histories at any time, and that your crypto accounting software and sanctions-screening stack need to reflect designations the moment they are published.
What OFAC Actually Designated
The Treasury announced the designations on 18 September 2026. The formal action covers BitBank itself, its developer Pishtaz Simorgh Electronic Trade Company, and three individuals described as associates of Iranian financier Babak Zanjani. Treasury characterised the group collectively as "key components of the Iranian regime's digital assets-based sanctions evasion infrastructure."
The Hormuz Safe connection
At the centre of the case is an entity called Hormuz Safe Marine Services Authority, which Treasury has previously described as an IRGC-backed operation that forces vessels transiting the Strait of Hormuz to purchase maritime insurance, including coverage against seizure by Iran itself. According to OFAC, by June 2026 Hormuz Safe was using BitBank to forward those extorted payments onward to the IRGC in Bitcoin. The scheme is alleged to be part of a broader architecture designed by Zanjani to move hundreds of millions of dollars in Bitcoin to the corps.
What Treasury Secretary Bessent said
US Treasury Secretary Scott Bessent stated directly: "Today's designations of Iranian digital asset infrastructure make perfectly clear that efforts to finance the Iranian regime using cryptocurrencies are not beyond OFAC's reach." The language signals that Treasury is treating crypto exchanges used for sanctions evasion with exactly the same enforcement posture it applies to traditional financial intermediaries.
BitBank Iran Is Not Bitbank Japan
A potential source of compliance confusion is naming. Iran's BitBank, established in 2024 according to the OFAC listing, is an entirely separate legal entity from bitbank, inc., a fully licensed Japanese crypto exchange founded in 2014. The Japanese firm has no connection to the designation. Firms running automated sanctions screening should verify that their name-matching logic applies sufficient contextual filters, such as jurisdiction, year of establishment, and regulatory status, to avoid false positives that could disrupt legitimate counterparty relationships with the Japanese exchange.
Pattern of Escalating Iran Crypto Sanctions
This designation does not sit in isolation. It is the latest in a sequence of Treasury actions aimed at severing Iran's access to international value transfer networks.
Recent prior actions
In June 2026, Treasury sanctioned a range of Iranian digital asset exchanges, including the country's largest, Nobitex. In August 2026, two further digital asset exchanges were designated on similar sanctions-evasion grounds. In July 2026, the US government ordered the freezing of more than $130 million in USDT held in wallets linked to Iran. The BitBank designation is therefore the fourth distinct wave of Iranian crypto sanctions in roughly four months, and the trajectory points toward continued escalation rather than a pause.
Iran's countermeasures
Iran has not been passive. The Financial Times reported earlier in September 2026 that Iran's central bank moved to incentivise businesses to repatriate overseas earnings through cryptocurrency, a direct response to tightening dollar-denominated restrictions. That policy shift means Iranian actors are actively looking for new on-ramps and off-ramps into the crypto ecosystem. For compliance teams, this is material: the pressure on Iranian actors to exploit any available exchange or wallet infrastructure is intensifying at the same time as OFAC's enforcement activity.
Accounting and Compliance Implications for Firms
An OFAC designation creates immediate and practical obligations that go beyond simply noting the news. Here is how the action translates into operational requirements for accounting firms, auditors, and corporate treasury functions with any digital asset exposure.
Sanctions list update and screening
OFAC's Specially Designated Nationals (SDN) list must be consulted before processing any digital asset transaction. The BitBank designation adds new wallet addresses, entity names, and individuals to that list. Any digital asset accounting software or treasury management system that pulls blockchain data should be reconciled against the updated SDN list immediately. Firms that use automated reconciliation tools need to confirm that those tools consume the OFAC list feed in near-real time, not on a daily or weekly batch cycle.
Blockchain forensics and historical transaction review
If any counterparty in your client base or portfolio has transacted with BitBank Iran, those transactions may now constitute a sanctions violation that must be reported to OFAC. A historical review of on-chain transaction data is warranted for any entity with Iranian crypto exposure. The Zanjani network's alleged use of Bitcoin, rather than privacy coins or stablecoins, means blockchain analytics tools can trace flows back through the chain, which cuts both ways: regulators can find the exposure, and so can your own forensics review before they do.
Correspondent and counterparty due diligence
Accounting firms advising crypto businesses should revisit counterparty KYC files for any exchange or OTC desk with Iranian client bases. The broadening of the designation to include Pishtaz Simorgh, BitBank's developer, matters here: entity due diligence needs to look through to beneficial owners and technology providers, not just the named exchange. The August designations of two other unnamed exchanges show that OFAC is working systematically through the Iranian crypto infrastructure, so today's clean counterparty could appear on the list next month.
Financial statement and disclosure considerations
For auditors signing off on digital asset schedules, the existence of an OFAC designation against a counterparty is a potential contingent liability trigger. If a client held funds on BitBank Iran or received Bitcoin routed through the Zanjani network, those balances are effectively frozen and may need to be impaired or disclosed as restricted assets. The disclosure question is live now, not at year-end. Materiality thresholds aside, auditors should document the inquiry and the client's response as part of the current engagement file.
Robust crypto bookkeeping software requirements
The frequency of Iranian crypto sanctions actions over the past four months underlines why crypto bookkeeping software configurations need to treat SDN list synchronisation as a core function, not an optional module. Any firm that treats sanctions screening as a periodic manual check rather than a live data feed is operating with a gap that regulators and auditors will increasingly scrutinise.
What This Means for Global Firms Outside the US
Non-US accounting firms and CFOs might assume that OFAC designations apply only to US persons and US dollar transactions. That reading is too narrow. OFAC's secondary sanctions regime means that non-US entities that materially assist a designated person or entity can themselves face designation or loss of access to the US financial system. Given that Bitcoin settlement can route through US-based infrastructure, wallets, or exchanges at any point in the chain, the risk of secondary exposure is real for European and Asian firms that do not screen against the SDN list as a routine matter.
The growing alignment between US Treasury actions and Financial Action Task Force (FATF) guidance on virtual asset service providers also means that non-US regulators in FATF member jurisdictions are likely to treat OFAC designations as relevant intelligence, even where they lack direct legal force. Firms in the EU, UK, and Asia-Pacific should flag this designation to their local compliance function and consider whether their own AML policies need updating.
Frequently Asked Questions
Is Iran's BitBank the same as the Japanese bitbank exchange?
No. They are legally separate entities. Iran's BitBank was established in 2024 and is now on the OFAC SDN list. The Japanese bitbank, inc. was founded in 2014 and holds a valid registration under Japan's Financial Services Agency. Firms should apply jurisdiction and establishment-date filters in their screening logic to avoid conflating the two.
What should a firm do if a client has transacted with BitBank Iran?
The firm should pause any further transactions involving that counterparty immediately, document the exposure, and seek legal advice on whether a voluntary self-disclosure to OFAC is required. OFAC has a formal self-disclosure process that can mitigate penalties. Do not attempt to unwind the position without legal guidance, as certain remediation steps could themselves constitute prohibited transactions.
Does the designation affect Bitcoin transactions that predate the designation date?
OFAC designations are not retroactively illegal in the sense that a transaction that was fully compliant when executed does not become a past violation. However, if the pre-designation transaction was already connected to a sanctioned actor at the time, it may have already constituted a violation. Firms should analyse pre-designation exposure on a facts-and-circumstances basis with sanctions counsel.
How often should sanctions screening run against crypto transaction data?
Best practice for any firm with material digital asset exposure is continuous or near-real-time screening against OFAC's SDN list feed, supplemented by daily batch reviews at minimum. Given that OFAC has issued four waves of Iranian crypto designations in roughly four months, a weekly or monthly cycle is no longer defensible for higher-risk client segments.
What accounting standard governs the impairment of assets held on a sanctioned exchange?
Under IFRS 9, a digital asset held on a sanctioned exchange where withdrawals are blocked would likely need to be assessed for impairment or reclassified as a restricted asset, depending on the reporting framework in use. Under US GAAP, ASC 350 guidance on intangible assets and the emerging practice on digital assets under ASU 2023-08 both require fair value assessment; a frozen balance on a sanctioned platform could have a fair value of zero. Firms should involve their technical accounting team and, where material, disclose the restriction in the notes to the financial statements.
Source: Cointelegraph