Sberbank Wins Russia Crypto Exchange Approval
Russia's largest bank has secured official authorisation to trade cryptocurrencies, and the clock is now running toward a December 2026 launch. The Bank of Russia's updated register confirms that Sberbank, alongside a handful of other major lenders and non-bank platforms, can now operate as a regulated crypto exchange under a framework that only came into force on 1 September 2026. For accounting firms, CFOs, and compliance teams operating anywhere near Russian counterparties, this development reshapes how you categorise, monitor, and report digital asset exposure. Good crypto accounting software is no longer optional in this environment; it is the operational baseline.
What the Bank of Russia Actually Did
The Bank of Russia publishes a formal register of authorised crypto market participants. The version dated 13 October 2026 lists ten authorised crypto exchange operators and six authorised digital custodians. The prior week's register carried only four exchange operators and five custodians. That jump of six new exchange authorisations in a single week reflects a deliberate acceleration of the licensing process.
Who Made the Register
Among the newly authorised entities, Sberbank and VTB stand out as systemically important banks already embedded in Russia's domestic financial infrastructure. They join non-bank entrants including T-Invest Lab and Atomyze. The fact that the regulator has admitted both large state-controlled banks and independent platforms suggests the framework is designed to accommodate a broad range of business models, not just specialist fintech firms.
The Regulatory Trigger: September 2026
The authorisations follow the entry into force on 1 September 2026 of legislation placing crypto exchange operators and custodians under direct Bank of Russia supervision. Before that date, crypto trading in Russia existed in a legal grey zone: not explicitly permitted for financial institutions, yet not consistently enforced against. The September legislation created the formal licensing categories for which entities are now applying and receiving approval. Think of it as Russia's equivalent of the EU's MiCA authorisation process, compressed into a much tighter timeframe and administered by a single central bank rather than a distributed network of national competent authorities.
Sberbank's December Launch Plan
Sberbank has stated publicly that it intends to launch crypto products on 1 December 2026, contingent on any additional regulations the Bank of Russia issues before that date. The planned offering covers three assets: Bitcoin, Ether, and Tether's USDt. Critically, the bank intends to deliver these products through its existing retail and business platforms, specifically SberBank Online, SberInvestments, and SberBusiness, rather than through a standalone crypto application.
Testing Already Under Way
Russian business publication Vedomosti reported, citing Sberbank's press office, that the bank has already begun testing crypto purchases, sales, deposits, and withdrawals inside the SberBank Online app. That means the technical infrastructure is not a future project; it is being validated right now against live user journeys. The December date therefore looks credible, subject to regulatory clearance, rather than aspirational.
What Remains Prohibited
One constraint matters enormously for anyone trying to model the commercial scope of this launch: Russia continues to prohibit using cryptocurrency to pay for goods and services. Sberbank's authorised activities are exchange and custody, not payment settlement. Customers will be able to buy, sell, hold, and transfer digital assets through Sberbank's platforms, but they cannot use those assets at the point of sale inside Russia. This distinction is not a minor footnote; it defines the entire accounting and tax treatment of the activity, and it limits the systemic payment-system risk that Western regulators might otherwise flag.
Accounting and Reporting Implications
For accounting firms and CFOs advising clients with any Russian nexus, the Sberbank authorisation creates a new category of counterparty to think about.
Balance Sheet Classification
Under IFRS, digital assets held by an entity are typically classified as intangible assets under IAS 38 or, where held for trading, measured under IAS 2. The inclusion of USDT in Sberbank's planned offering complicates this further. A stablecoin pegged to the US dollar but traded through a Bank of Russia-regulated entity occupies an unusual position: it may read as a monetary item for IFRS 21 (foreign currency) purposes in some jurisdictions, yet be treated as an intangible or commodity in others. Finance teams receiving USDT from a Sberbank-regulated account will need to document the classification basis explicitly, because an auditor reviewing the transaction will face genuine ambiguity.
Transfer Pricing and Group Reporting
Multinationals with Russian subsidiaries face a further layer of complexity. If a Russian subsidiary holds BTC or ETH through Sberbank and the group consolidates under IFRS or US GAAP, the parent must decide how to translate the fair value of those holdings at the reporting date. Exchange rates, custody arrangements, and the legal recoverability of assets held with a sanctioned-adjacent institution all feed into that judgment. Robust digital asset accounting software that can pull in exchange rates from multiple sources and tag transactions by custodian is not a luxury here; it is what makes the audit trail defensible.
Sanctions Screening at the Transaction Level
The participation of Sberbank and VTB in Russia's crypto register is the headline. The compliance implication is quieter but sharper. Both banks have been subject to varying degrees of Western sanctions since 2022. Sberbank's crypto operations are domestic and currently outside most Western payment rails, but any firm that receives digital assets that can be traced back to a Sberbank-originated address has a potential sanctions exposure. On-chain analysis and wallet screening become mandatory steps, not optional enhancements. For a practical framework on how to structure that monitoring efficiently, see our piece on scaling crypto transaction monitoring without ballooning costs.
AML Considerations for Financial Institutions
The Bank of Russia's new framework places exchange operators and custodians under central bank oversight, which in theory means KYC and AML obligations apply to Russian-licensed platforms. In practice, the standards, technology, and international data-sharing arrangements behind that oversight differ materially from the FATF-aligned regimes operating in the EU, UK, or US.
The Travel Rule Gap
FATF's Travel Rule requires originator and beneficiary information to travel with virtual asset transfers above threshold. Russia is an FATF member but has historically had a mixed implementation record. Whether Sberbank's platform will transmit Travel Rule data in a format compatible with EU or UK VASP systems remains unknown at this point. Firms receiving transfers from Sberbank-originated wallets should not assume that FATF-standard data will accompany those transactions and should build their screening workflows accordingly.
USDT as a Specific AML Risk Vector
The inclusion of Tether's USDt in Sberbank's planned offering deserves particular attention. USDT is the most widely used stablecoin in cross-border value transfer in high-risk corridors, and its inclusion in a state-bank-distributed Russian crypto product will attract scrutiny from financial intelligence units in multiple jurisdictions. Compliance teams should update their risk appetite statements and SAR trigger criteria to account for USDT flows that route through Russian-licensed custodians. Our earlier analysis of stablecoin AML compliance obligations for banks provides a working framework for categorising that risk.
Correspondent Banking Knock-On Effects
Even where a non-Russian bank has no direct relationship with Sberbank, the existence of a regulated domestic crypto market in Russia increases the probability that digital assets will move through intermediary wallets before reaching correspondent accounts elsewhere. Nested exchange risk, where a retail customer of a foreign exchange uses Sberbank's platform as an upstream liquidity source, is a realistic scenario that AML teams should model in their risk assessments now, before the December launch.
What Firms Should Do Before December 2026
The window between now and Sberbank's planned 1 December launch is short. It is, however, long enough to take a few targeted actions that will reduce both compliance and accounting risk.
Update Counterparty Risk Classifications
Review your existing customer and counterparty database for any entity that holds accounts with Sberbank or VTB, or that transacts through their affiliated platforms. Flag those records for enhanced due diligence once Sberbank begins live crypto operations. If your crypto bookkeeping software supports tagging by counterparty jurisdiction and institution, apply those tags now so that transactions from December onwards are automatically routed to a higher-scrutiny review queue.
Clarify Ledger Treatment for Russian-Originating Digital Assets
Agree with your auditors, before year-end, how digital assets received from or traded through Russian-licensed platforms will be classified on the balance sheet, what fair value hierarchy level applies, and how impairment will be assessed if regulatory conditions change materially. Documenting that judgment before transactions occur is significantly less painful than reconstructing it under audit pressure in Q1 2027.
Brief the Board on Sanctions Interaction Risk
The sanctions status of Sberbank and VTB is not static, and the extension of their activities into crypto creates new vectors for inadvertent exposure. A brief, factual board paper setting out the regulatory position, the firm's current exposure, and the monitoring steps being taken is both good governance and good evidence of adequate controls if a regulator ever asks.
Frequently Asked Questions
Is Sberbank's crypto trading platform accessible to non-Russian clients?
Based on the information currently available, Sberbank's crypto products are designed for its existing domestic customer base, accessed through SberBank Online, SberInvestments, and SberBusiness. There is no indication that the platform will be open to customers outside Russia, and the Bank of Russia's authorisation framework is a domestic licensing regime.
Can companies use BTC or USDT received through Sberbank to pay Russian suppliers?
No. Russia currently prohibits the use of cryptocurrency as a means of payment for goods and services. Sberbank's authorisation covers exchange and custody activities only. Any company treating crypto received through Sberbank's platform as a payment instrument inside Russia would be operating outside the current legal framework.
How does Sberbank's authorisation affect sanctions screening for Western firms?
It increases the complexity of on-chain due diligence. Sberbank and VTB are subject to sanctions measures in several Western jurisdictions. Firms that receive digital assets traceable to wallets operated by these institutions face potential exposure, regardless of whether the transaction itself was conducted on a Russian-regulated platform. Wallet-level screening and Travel Rule data verification become essential steps.
What accounting standard should apply to USDT held at a Russian-licensed custodian?
This is genuinely unsettled. Under IFRS, USDT could be treated as a monetary item (IAS 21), a financial instrument (IFRS 9), or an intangible asset (IAS 38), depending on its contractual terms and the entity's business model. Custody by a Bank of Russia-regulated entity does not resolve the classification question, but it does add a layer of recoverability risk that may affect impairment assessment. Firms should seek explicit auditor sign-off on the classification before December 2026 transactions appear on the books.
Does the Bank of Russia framework align with FATF's Travel Rule requirements?
Russia is an FATF member and is expected to implement Travel Rule obligations, but whether Sberbank's systems will transmit originator and beneficiary data in a format compatible with EU or UK VASP infrastructure is not yet confirmed. Financial institutions should not assume compliant data flows and should build manual verification steps into their workflow for transactions originating from Russian-licensed platforms until interoperability is confirmed.
Source: Cointelegraph