On 29 October, the Bank of Russia proposed raising the single-payment ceiling for businesses using SBP to RUB 30 million. The proposal also covers payments into the budget system. Comments are invited through 12 November 2026. It is a consultation, not confirmation that banks already offer the higher limit.
Event / source publication date: 29 October 2026The following is Human Fintech’s analysis
A system ceiling is only one layer.
For an international reader, this is a Russian proposal with a broadly useful design question: when does a payment limit become an operational bottleneck? Consider an illustrative invoice that needs several transfers because of a technical restriction. Removing that restriction could reduce the number of instructions and confirmations to reconcile. It does not, by itself, guarantee a better end-to-end process.
A company still needs to understand its own bank’s service, the authority of the employee initiating the transfer and the available funds. These are separate from a system-wide ceiling. A proposal to change one layer should not be read as a promise that every provider will offer the same user journey or the same customer-level permissions.
Approval belongs before execution.
A useful workflow distinguishes preparation from authorisation. In a hypothetical business, one employee enters the instruction and another checks its commercial basis. Faster execution should not silently remove that separation. Changes to beneficiary details deserve particular attention because the right invoice amount can still be sent to the wrong destination.
The other test is an uncertain outcome. If the interface fails to display a confirmation, the operator needs a reliable way to establish whether the instruction succeeded. Repeating the transfer should not be the default diagnostic step. This is an operational design consideration, not a claim that the draft introduces a specific new control.
Measure the work around the payment.
Transaction fees are only part of a business’s comparison. Preparation time, approval steps, status enquiries and matching the result to the invoice also consume resources. A lower fee can coexist with expensive manual handling. Conversely, fewer instructions may be valuable when their accounting trail remains complete and easy to verify.
The practical response during consultation is to identify questions rather than assume availability. Once final rules and bank implementation details exist, users can ask which transactions are supported, what restrictions apply to their account and which confirmation records they receive. Budget payments also require a clear purpose and an execution check. This keeps the analysis tied to a usable service: a higher headline number matters only when the surrounding process can reliably handle the payment it permits.
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.