A7A5 Ruble Stablecoin: How Coordinated Sanctions Cut Off a $100B Network

A ruble-pegged cryptoasset that processed more than $100 billion in transactions has been reduced to a near-standstill. Transaction volumes on A7A5 are down 96% from their July 2025 peak, new issuance has stopped entirely, and the token's primary trading venue collapsed in April 2026 after a security breach that wiped more than one billion rubles in customer balances. The mechanism that brought it down was not a court order or a protocol hack. It was the combination of coordinated multi-jurisdictional sanctions and blockchain analytics that made every gateway in and out of the token toxic to any compliant counterparty. For accounting firms, auditors and CFOs with stablecoin exposure, this case sets a new standard for what indirect sanctions screening must look like inside crypto accounting software and compliance workflows.

What A7A5 Was and Why It Existed

Design and ownership

A7A5 is a stablecoin pegged one-to-one to the Russian ruble. It was created by A7 LLC, a Russian cross-border payments firm, and formally issued by Old Vector LLC, incorporated in Kyrgyzstan. Its main shareholders include Ilan Shor, a convicted fraudster sanctioned for interference in Moldovan elections on behalf of Russia, and Promsvyazbank (PSB), a Russian state-owned bank sanctioned for financing Russia's defence sector. The token claimed backing by ruble deposits, likely held at PSB, and runs on the Ethereum and Tron blockchains.

The sanctions-evasion rationale

After Western sanctions severed Russia's banks from the global financial system in 2022, Russian importers and exporters increasingly settled cross-border payments in cryptocurrency. Tether's USDT became the dominant tool: liquid, universally accepted, and stable. But USDT carries one compliance vulnerability for sanctions evaders specifically: Tether can and does freeze wallets at the request of US authorities. In March 2025, the US Secret Service, working with blockchain analytics, demonstrated precisely that capability.

A7A5 was engineered to work around that vulnerability. The model was straightforward: hold value in a ruble token that no Western entity controls, then convert into USDT only for the moments an actual settlement requires. The ruble stablecoin acted as a buffer, keeping Russian businesses insulated from prolonged exposure to Tether's freeze risk while still accessing global crypto liquidity. For roughly a year, the model worked, with approximately 251,000 transactions recorded before the floor gave way.

Three Enforcement Levers That Strangled the Token

The collapse was not the result of a single action. It came from three overlapping pressures applied in sequence across the second half of 2025 and early 2026.

Lever 1: coordinated multi-jurisdictional sanctions

The US, UK and EU each designated A7A5 and its supporting infrastructure in waves across the second half of 2025. On the surface, a sanctions designation cannot stop a smart contract. The Ethereum and Tron code that governs A7A5 kept running regardless. What the designations did accomplish was to make every regulated entity that touched A7A5 downstream a potential sanctions violator. That distinction matters enormously in practice.

Blockchain analytics firms trace the flow of funds from sanctioned entities across public ledgers, which are permanent and fully visible. Major exchanges use these tools to screen every incoming deposit. Once A7A5 was designated, USDT obtained by swapping A7A5 arrived at exchanges carrying a traceable history linking it to a sanctioned network, even several transaction hops back in the chain. From late September 2025 onward, A7A5 users began reporting that swapped USDT was being frozen or flagged on arrival at global exchanges. By early 2026, users were warning each other to avoid any wallet activity touching the A7A5 ecosystem, including the exchanges Grinex and Meer, because even indirect exposure was triggering account closures.

The three-jurisdiction coordination was not incidental. Cryptoassets move across borders without friction, so a designation in one jurisdiction alone creates an opening: activity simply shifts to venues that serve other markets. Coordinated designations across the US, UK and EU closed those gaps simultaneously, leaving no compliant routing option.

Lever 2: Russian domestic regulatory pressure

The second blow came from within Russia itself. The Bank of Russia has long opposed the domestic circulation of cryptoassets. Through late 2025, it tightened controls on the main channel through which ordinary Russians purchased A7A5: PSB-issued Mir bank cards. The official A7A5 website repeatedly suspended card purchases, and customer support staff directed users toward brokers and promissory notes instead. On 4 April 2026, Grinex, the primary A7A5 trading venue, announced that account top-ups via bank cards were offline. That was effectively the last accessible fiat on-ramp for retail participants. The steep decline in transaction volumes from early April 2026 followed immediately and directly.

Lever 3: exchange delisting and single-point-of-failure concentration

In November 2025, Uniswap removed A7A5 from its website interface. The underlying smart contracts continued to operate, but the delisting ended meaningful decentralised liquidity. By late 2025, the overwhelming majority of A7A5 trading was concentrated on Grinex, itself sanctioned and widely described as a Russia-linked successor to the previously disrupted Garantex exchange.

That concentration proved fatal. On or around 16 April 2026, less than two weeks after the card outage, Grinex suffered a security breach. More than one billion rubles, approximately $15 million, in customer assets were stolen. Grinex attributed the event to a sophisticated nation-state attack. Some observers considered it an exit scam. Regardless of the true cause, the only venue with meaningful A7A5 liquidity had failed, and customer balances went with it.

What the Data Shows

The volume trajectory tells the story with little ambiguity. Average daily transaction volumes fell to $24.3 million in June 2026, a 96% drop from the July 2025 peak. New issuance, or minting, of A7A5 stopped entirely after July 2025. Over the same period, USDT supply grew by around 14%, approximately $22 billion, illustrating that demand for ruble-denominated settlement collapsed while dollar-denominated stablecoin demand continued to expand globally.

The smart contracts are still live. Transfers and interest distributions continue at reduced levels. But a stablecoin that cannot be minted, cannot access compliant exchanges, and whose sole significant trading venue has collapsed is no longer fit for its stated purpose of facilitating cross-border payments.

AML and Compliance Implications for Accounting Firms and CFOs

Indirect exposure is the central risk

The most operationally significant lesson from A7A5 is that sanctions exposure does not require a direct relationship with a designated entity. A client's wallet may receive USDT that was swapped from A7A5 several hops earlier in the transaction graph. That indirect link is enough to trigger a freeze at a compliant exchange, prompt a Suspicious Activity Report, and in some jurisdictions constitute a sanctions violation requiring self-disclosure. Standard KYC checks at onboarding do not catch this. Only ongoing blockchain transaction monitoring, integrated with a reliable analytics feed, does.

Accounting firms running crypto accounting software workflows for clients with stablecoin positions need to confirm that their transaction-screening layer goes beyond simple address matching against published lists. Graph-based analytics that trace funds across multiple hops are now a baseline expectation for any firm with material digital asset exposure, not an advanced option.

Stablecoin due diligence: issuer and reserve screening

A7A5 claimed one-to-one ruble backing, likely through reserves held at PSB. Once PSB itself was sanctioned, any assertion of legitimate reserve backing became legally untenable, regardless of what the smart contract said. CFOs and auditors evaluating stablecoin positions for balance-sheet or treasury purposes must apply issuer-level due diligence: who controls the reserve, where are those reserves custodied, and are any of those entities subject to, or at material risk of, sanctions designation? This is now a standard audit question for any non-dollar stablecoin and arguably for dollar-denominated ones where the reserve bank or custodian carries elevated political-risk exposure. Sound digital asset accounting software should flag issuer-level risk attributes alongside price and volume data.

For a broader view of how sanctions designations in the crypto space are evolving, the US Treasury's actions against crypto-linked Iranian entities offer a useful parallel framework; see our earlier analysis of US Treasury sanctions against crypto-linked Iranian entities.

Concentration risk in trading infrastructure

A7A5's reliance on Grinex as its sole significant venue turned a sanctions-related liquidity squeeze into a total failure once that single exchange collapsed. CFOs who use narrow or non-mainstream exchange infrastructure for stablecoin conversion face analogous concentration risk, even where sanctions are not a factor. Treasury policies should specify minimum venue diversification and require that each approved venue is listed on at least one major compliant exchange's counterparty whitelist.

Jurisdiction coordination as a policy signal

The deliberate sequencing of US, UK and EU designations signals that sanctions authorities are actively coordinating to close the jurisdictional arbitrage gaps that have historically allowed illicit actors to reroute around single-jurisdiction restrictions. For compliance teams, this means that a token or counterparty that appears outside one jurisdiction's reach may be fully designated within weeks. Watchlist monitoring must be live and multi-jurisdictional, not a quarterly batch process.

The broader pattern of coordinated enforcement is consistent with what the BDO Worldwatch 2026 survey identified as an accelerating trend; firms that have not yet updated their screening cadence should read our summary of BDO white-collar crime trends and what accounting firms must act on.

Practical Steps for Firms and CFOs

Immediate review items

Any firm or treasury function with stablecoin inflows should carry out a focused review across four areas. First, confirm that transaction-screening tools perform multi-hop graph analysis, not only direct address checks against sanctions lists. Second, audit the issuer and reserve-custodian profile of every non-USDC, non-USDT stablecoin position, applying the same beneficial-ownership and sanctions-nexus tests you would apply to a bank counterparty. Third, review the exchange and liquidity-venue diversification policy for stablecoin conversion; single-venue dependency is a material operational risk. Fourth, verify that watchlist monitoring runs on a real-time or near-real-time basis across all three major sanctions lists: OFAC (US), OFSI (UK), and the EU Consolidated List.

Accounting and disclosure considerations

From an accounting standpoint, a stablecoin that becomes subject to sanctions designations affecting its issuer or primary exchange presents a potential impairment trigger. Even if the smart contract keeps running and a market price is technically observable, the practical realisability of that position is impaired if no compliant venue will process the conversion. Auditors should probe management's assessment of whether any stablecoin positions held by audit clients carry analogous characteristics, particularly where the issuer is a non-Western entity, the reserve custodian is not independently verified, or the token is not listed on any major regulated exchange.

Under IFRS 9, a financial asset whose contractual cash flows are at significant risk of not being collected due to legal or regulatory barriers, including sanctions, may require a revised expected-credit-loss assessment or outright derecognition if recovery is not reasonably expected. US GAAP preparers should consider whether the fair-value hierarchy classification remains appropriate when market depth has effectively evaporated.

Source: Elliptic