Russia to Ban P2P Crypto Trades from July 2027
Russia's central bank has confirmed that direct peer-to-peer cryptocurrency transactions between individuals will become unlawful from 1 July 2027, and that transfers from regulated digital accounts to self-custody wallets are already prohibited under rules in force since September 2026. For accounting firms, auditors, and CFOs with any exposure to Russian digital asset flows, both measures carry immediate practical consequences, regardless of where the firm itself is domiciled.
What the Bank of Russia Has Actually Said
The Bank of Russia published updated guidance confirming two distinct restrictions, each with a different effective date and legal basis.
The July 2027 P2P prohibition
From 1 July 2027, individuals will no longer be permitted to exchange crypto assets directly with one another without using an authorised intermediary. The central bank's framing is unambiguous: direct bilateral trades, the kind that have historically occurred via messaging apps, decentralised exchange interfaces, or simple wallet-to-wallet transfers, will cease to be a lawful settlement mechanism for individuals in Russia. All such transactions will need to be routed through operators that have been licensed or otherwise recognised under the Bank of Russia's oversight framework.
The self-custody transfer ban already in force
Separate from the P2P deadline, the Bank of Russia has clarified that individuals are already not permitted to move crypto assets from a regulated digital account held with a licensed custodian to their own non-custodial wallet. This restriction took effect alongside the broader framework that came into force on 1 September 2026, which brought exchange operators and custodians under central bank supervision. The practical effect is that any Russian individual who holds digital assets through a licensed platform cannot unilaterally withdraw those assets to a private wallet address.
Context: Russia's Regulated Crypto Market Is Expanding
These restrictions do not sit in isolation. Russia has been building a supervised digital asset market in parallel with tightening controls on unmediated activity. The September 2026 framework formalised central bank oversight of exchange operators and custodians, and the same week that the updated P2P guidance was published, Russia's largest bank received approval to offer crypto exchange services, having previously been authorised as a digital asset custodian. The approval of a major state-linked institution as an exchange operator signals that the government intends to channel crypto activity through entities it can supervise and audit, rather than prohibit digital assets outright.
For context on how that Sberbank authorisation fits into the wider Russian digital asset landscape, see our earlier note on Sberbank winning Russia's crypto exchange approval.
Russia also continues to prohibit cryptocurrency as a means of payment for goods and services, a ban that predates the September 2026 framework. Taken together, the direction of travel is clear: the Russian state wants crypto activity centralised within a supervised, identifiable intermediary layer, with self-directed custody and bilateral settlement routes progressively closed off.
Enforceability: A Live Debate
Industry participants have publicly questioned how effectively either restriction can be enforced in practice. Peer-to-peer networks are structurally more resistant to takedown than centralised platforms, and banning a wallet application does not necessarily eliminate access to the underlying protocol. These observations are accurate, and they matter for risk modelling. However, they do not change the legal position: from the Bank of Russia's perspective, unlicensed P2P trades and self-custody withdrawals are non-compliant activities, and the legal and reputational risk of being party to a non-compliant transaction falls on any counterparty that knowingly facilitates or records one.
What "difficult to enforce" means for compliance officers
When a regulation is hard to enforce uniformly, the practical consequence is often selective and unpredictable enforcement, not zero enforcement. Firms that deal with Russian counterparties, process payments routed through Russian digital asset platforms, or hold Russian-facing crypto positions on behalf of clients cannot rely on regulatory opacity as a compliance substitute. The question for a compliance officer is not whether every violation will be caught, but whether the firm's own processes and audit trail would survive scrutiny if they were.
Accounting and Audit Implications
Both the P2P ban and the self-custody prohibition create specific pressure points for financial reporting and audit work.
Counterparty and settlement risk on the balance sheet
Any digital asset position that is currently settled via direct wallet-to-wallet transfers with Russian counterparties will need to be reclassified or restructured before July 2027. If that restructuring has not happened by the balance sheet date and the settlement route is materially non-compliant with the Bank of Russia framework, auditors will need to consider whether the asset can still be recognised, whether a contingent liability exists, and whether adequate disclosure has been made of the regulatory exposure. Under IFRS, the substance of control and recoverability of an asset are always relevant to recognition; a digital asset that cannot lawfully be transferred without a licensed intermediary may affect how "control" is assessed, particularly if the intermediary layer has not yet been established.
Custody disclosures and the self-custody prohibition
The prohibition on transferring assets from a regulated digital account to a self-custody wallet has an immediate implication for firms that hold crypto on behalf of Russian clients or that rely on Russian custodians within a broader asset-management structure. If an asset is held at a Russian-licensed custodian and cannot be withdrawn to a private wallet, the client's practical control over that asset is limited. Firms preparing financial statements or advising clients on asset disclosures need to reflect that restriction accurately. This is not a hypothetical: the rule is already in force.
AML and transaction monitoring
The requirement to route all trades through authorised intermediaries is, from an AML standpoint, a transparency mechanism. Licensed platforms are subject to the Bank of Russia's KYC and reporting obligations. For firms conducting correspondent due diligence or reviewing the provenance of crypto inflows from Russian sources, the question from July 2027 onward will be whether those inflows can be traced to a licensed operator. Inflows that cannot be attributed to a licensed intermediary will, by definition, originate from a prohibited transaction, raising the risk rating of the counterparty regardless of the underlying transaction economics.
The parallels with other jurisdictions' approaches to unlicensed crypto activity are instructive. Our analysis of South Korea's decision to block 27 unlicensed crypto exchanges illustrates how rapidly regulators can move from warning to enforcement when the licensing perimeter is clearly defined.
Practical Steps for Firms Before July 2027
The deadline is roughly eight months away at the time of writing. That is not a long runway for firms that need to restructure counterparty arrangements, update KYC workflows, and revise accounting policies.
Counterparty review
Firms should map every Russian counterparty or Russian-domiciled digital asset position and identify the current settlement mechanism. Any position that relies on direct wallet-to-wallet transfer or on a non-licensed platform needs a remediation plan. That plan should identify which Bank of Russia-licensed intermediary will replace the current arrangement and what the associated custody and reporting obligations are.
Policy and procedure updates
Onboarding checklists, AML risk assessments, and transaction monitoring rules will need to reflect the post-July 2027 environment. A Russian individual counterparty who claims to settle via a private wallet will be making a representation that is, on its face, non-compliant with Russian law. That should be flagged in the firm's risk scoring model, not accepted at face value.
Digital asset accounting software and audit trail integrity
Firms using crypto accounting software to track digital asset positions need to ensure that the custody source of each position is recorded at the point of acquisition. When the regulatory environment shifts, as it has here, the ability to demonstrate the lawfulness of the original settlement route becomes an audit necessity. Crypto bookkeeping software that does not capture custodian identity and transaction provenance at the ledger level will leave gaps that are difficult to reconstruct retroactively. This is the moment to verify that the firm's digital asset accounting software captures that data and retains it in an auditable format.
Client communication
For accounting firms advising Russian-based clients or international clients with Russian digital asset exposure, a proactive letter or briefing note setting out the two restrictions and their effective dates is appropriate now. Waiting until Q2 2027 to raise the issue will compress the remediation window to a point where orderly restructuring may not be possible.
Frequently Asked Questions
From when is the P2P crypto ban effective in Russia?
The Bank of Russia has confirmed that direct peer-to-peer crypto transactions between individuals will be prohibited from 1 July 2027. Trades must be routed through a Bank of Russia-authorised intermediary from that date.
Is the self-custody transfer restriction already in force?
Yes. The prohibition on transferring crypto assets from a regulated digital account to a non-custodial wallet is already in effect, having been introduced as part of the framework that came into force on 1 September 2026.
How does this affect the audit of a client holding Russian crypto positions?
Auditors need to assess whether the settlement and custody arrangements supporting each Russian digital asset position are compliant with the Bank of Russia framework. Positions that rely on self-custody or direct P2P settlement may require disclosure of a contingent compliance risk, and the question of whether the firm retains effective control of the asset is relevant to IFRS recognition.
What does this mean for AML due diligence on Russian counterparties?
From 1 July 2027, any crypto inflow from a Russian individual that cannot be traced to a Bank of Russia-licensed intermediary originates from a prohibited transaction. Firms should update their transaction monitoring rules and counterparty risk scoring to reflect this change ahead of the deadline.
Does this affect non-Russian firms with no Russian operations?
Potentially, yes. If a non-Russian firm has counterparties, clients, or fund investors who are Russian individuals holding or transacting in crypto, the compliance status of those individuals' arrangements becomes relevant to the firm's own AML and KYC obligations. Knowing your counterparty includes knowing whether their settlement flows are lawful in their home jurisdiction.
Source: Cointelegraph