Russia SBP limit for businesses rises to RUB 30m in 2027
Business SBP payments in Russia are capped at RUB 1 million each. A Bank of Russia draft raises the cap to RUB 30 million, effective 22 November 2027.
Right now a Russian company or sole trader can send at most RUB 1 million per transaction through the Faster Payments System (SBP). The Bank of Russia has proposed raising that cap to RUB 30 million, but the new limit only takes effect on 22 November 2027. Until then, large supplier payments over SBP still have to be split.
The change sits in a draft Bank of Russia directive amending Regulation No. 876-P of 3 December 2025 on the Bank of Russia payment system. Comments are open until 12 November 2026 inclusive. This summary relies on the regulator's announcement and trade-press coverage listed in the sources.
SBP limit for businesses: RUB 1 million now, RUB 30 million from November 2027
The current ceiling for a single business SBP payment is RUB 1,000,000. The draft lifts it to RUB 30,000,000 for two flows:
- transfers between accounts of companies and sole traders (B2B);
- payments by individuals, companies and sole traders to the state budget via the single treasury account.
The cap is per payment. Daily or monthly limits that banks set themselves are not part of the draft as reported, so check your own bank's terms.
The plan was signalled earlier: the central bank backed a RUB 30 million business limit in May, and its September draft of the 2027–2029 financial market strategy listed B2B SBP scaling, B2B Push and B2B refund scenarios, plus online B2G tax payments. The draft directive now puts a date on it.
Does it affect consumer checkout?
Barely. If you sell online and take QR or payment-link payments from individuals, this draft is about company-to-company and budget payments, not consumer checkout.
The businesses that will notice are those where money moves between firms: marketplaces paying out to merchant sellers, B2B SaaS billed annually, wholesalers with large orders, and anyone who wants tax payments to clear as fast as transfers.
In our view the real gain is dropping a second payment rail. With a RUB 1 million cap, large amounts still go by regular bank order, and finance teams reconcile two flows with different status logic.
Worked example: one supplier invoice, five transfers
Illustration only. A distributor owes a supplier RUB 4.5 million. Before 22 November 2027 that is five SBP transfers: four of RUB 1 million and one of RUB 500,000, each a separate line in the statement and in the supplier's reconciliation. After the change it is one.
Scale it up: a marketplace paying 40 large sellers about RUB 3 million each per month makes 120 SBP transfers instead of 40. Splitting is allowed, but it adds accounting work. At those volumes we would keep large payouts on regular transfers until late 2027 and use SBP for amounts under the cap.
One caveat: a run of identical transfers to the same recipient on the same day can draw your bank's compliance attention. If you split a contract payment on purpose, telling the bank up front is easier than explaining afterwards.
What to do before 12 November and before November 2027
If your business has a case that even RUB 30 million does not cover, or questions about refunds, the consultation is open until 12 November 2026.
Over the next year, ask your bank whether it supports B2B SBP transfers in online banking and via API, and what internal limits apply. If your payouts are automated, plan to remove the "split into RUB 1 million chunks" logic.
For consumer payments, compare acquiring costs in the fee calculator and see local options on the Russia payments page. For another market where transfer caps break checkout, see our piece on Nigeria's new-device limit.
Accepting payments in Russia or neighbouring markets? Send us a request and we will match methods to your volumes.
Sources
This article was prepared by the PayFlow editorial team with the help of AI, based on the public sources listed above. It is for information only and is not legal or financial advice; provider terms change — check current terms with an operator.