On 18 September, the Bank of Russia announced draft rules introducing N31 and N32 ratios for risks involving digital currencies and foreign digital instruments. The scope includes instruments whose payouts depend on digital-currency values. As of 20 September, the rules remain a proposal; implementation and reporting dates are stated plans, not completed changes.
Event / source publication date: 18 September 2026The following is Human Fintech’s analysis
Read the obligation behind the product label.
For a partner or investor assessing a Russian banking proposition, the first task is to map contractual cash flows. Establish what determines the customer payout, which party holds the underlying position and what the bank must deliver if normal settlement fails. A product name or accounting category may provide less information than the actual allocation of obligations between counterparties.
The operating map should show where the bank needs to value, fund or close a position and which external services it depends on. Product, treasury and risk teams can build this together, with legal specialists checking the contractual basis. The exercise clarifies the business even before the final regulatory calculation is settled and provides a common reference for later decisions.
Data readiness can proceed without guessing the final rule.
A multi-system product may store customer records, transaction details and financial exposure in separate places. Test whether these can be joined consistently at a defined point in time. Instrument identifiers, valuation timestamps and links to the relevant contract are practical starting points. Missing information should have an owner and a plan for collection rather than an informal promise to reconstruct it later.
This does not require building a final regulatory return around draft details. It requires understanding the records the business already produces and the evidence it will need to explain its positions. If a critical field is absent from transaction history, a new report template will not repair the gap. Early discovery gives teams time to address the underlying process.
Treat the proposal as a scenario boundary.
A commercial model can distinguish present operations from a scenario in which new requirements take effect. Assess the implications for capacity, operating costs and product scope under explicit assumptions. Decisions affecting existing agreements should follow review of the final applicable documents. The announcement itself should not be represented to customers or partners as either an approval or a newly effective prohibition.
Investors should also ask who can authorise launch, restrict activity and revisit the business case when rules change. A useful readiness package combines an exposure map, a data-gap register and clear decision ownership. For readers outside Russia, the proposal is jurisdiction-specific; the transferable lesson is to evaluate the obligations a financial product creates before relying on its marketing description.
White Fintech.
Part VII of White Fintech covers payment businesses, including company structure, risks, compliance and economics. Explore the contents and the free sample.
Complete English edition, PDF + EPUB. Read the first 30 pages free, with no sign-up.