Setting up SBP in 1C-Bitrix: Accept Instant Payments

After hundreds of card acquiring integrations to stores on 1C-Bitrix, we noticed a pattern: owners return after six months with a request for SBP. The reason is obvious — commission of 0.4–0.7% versus the average 2% for cards. SBP is 3–5 times cheaper than cards — for a store with a turnover of $9k–13k per month, the savings amount to up to $160–230. And that's not counting the fact that money arrives in seconds, not the next day. The technical implementation is simpler than it seems: we have prepared integration with two popular providers — Tinkoff and YooKassa. Both provide simple APIs and fast onboarding. Average connection time is 1-2 days.

What is SBP and how it works

SBP is an interbank instant payment system of the Bank of Russia, launched in 2019. It is a direct transfer between the buyer's and seller's accounts without intermediary payment systems. The buyer scans a QR code or clicks a link — payment goes through without entering card data. For online stores, SBP provides the advantage of reducing commissions by 3–5 times compared to cards.

Comparison of SBP and card acquiring

An additional plus is increased conversion: according to our estimates, up to 15% of users abandon the cart when they see the card entry form. SBP removes this barrier.

Integration of SBP via Tinkoff

Tinkoff provides two formats: link (for mobile) and QR code (for desktop). Connection steps:

1. Get a terminal key in your Tinkoff personal account.
2. Create a payment session via the Init API.
3. Request a QR code via GetQr.
4. Display to the user depending on the device.

Example of creating a payment session and getting a QR:

// Create payment session $params = [ 'TerminalKey' => TINKOFF_TERMINAL, 'Amount' => (int)($order->getPrice() * 100), 'OrderId' => $order->getAccountNumber(), 'Description' => 'Order #' . $order->getAccountNumber(), 'NotificationURL' => 'https://shop.ru/bitrix/tools/sale_ps_result.php', 'PayType' => 'O', ]; $params['Token'] = tinkoffSign($params, TINKOFF_SECRET); $init = tinkoffPost('/v2/Init', $params); $paymentId = $init['PaymentId']; // Get QR for SBP $qrParams = [ 'TerminalKey' => TINKOFF_TERMINAL, 'PaymentId' => $paymentId, 'DataType' => 'PAYLOAD', ]; $qrParams['Token'] = tinkoffSign($qrParams, TINKOFF_SECRET); $qr = tinkoffPost('/v2/GetQr', $qrParams); $sbpLink = $qr['Data']; 

Adaptive display of QR and links

The next step is to show the user the correct interface. On mobile devices, it's better to open the banking app via a link, on desktop — a QR code. Check the user-agent and render the appropriate element:

const isMobile = /Mobi|Android/i.test(navigator.userAgent); if (isMobile) { const btn = document.getElementById('sbp-btn'); btn.href = sbpLink; btn.style.display = 'block'; } else { const qr = new QRCode(document.getElementById('sbp-qr'), { text: sbpLink, width: 200, height: 200, }); document.getElementById('sbp-qr-block').style.display = 'block'; } // Polling status const poll = setInterval(async () => { const status = await fetch('/api/sbp-status.php?orderId=' + orderId) .then(r => r.json()); if (status.paid) { clearInterval(poll); location.href = '/payment/success/'; } }, 2000); 

Integration via YooKassa

YooKassa also supports SBP. Example of creating a payment:

$payment = $client->createPayment([ 'amount' => ['value' => number_format($sum, 2, '.', ''), 'currency' => 'USD'], 'payment_method_data' => ['type' => 'sbp'], 'confirmation' => ['type' => 'qr'], 'capture' => true, 'description' => 'Order #' . $orderId, 'metadata' => ['order_id' => $orderId], ], uniqid('', true)); 

Handling callback notifications from the bank

After payment, the bank sends a POST request to the NotificationURL. This notification contains the payment status and must be handled correctly:

// Receive notification $json = file_get_contents('php://input'); $data = json_decode($json, true); // Verify signature $token = hash('sha256', $json . TINKOFF_SECRET); if ($token !== $_SERVER['HTTP_X_SIGNATURE']) { http_response_code(400); echo 'bad signature'; exit; } // Update payment status in Bitrix if ($data['Status'] === 'CONFIRMED') { \Bitrix\Sale\PaymentCollection::setPaid($data['OrderId'], 'Y'); } 

Important: never rely solely on callbacks. Implement polling of the status (as in the example above) — the callback may not arrive due to network failures, but the payment may have already gone through.

Important points: commission and fiscalization

To work with SBP, you need a separate product from the bank — "Accepting payments via SBP". Rates for e-commerce: 0.4% for individuals, up to 0.7% for legal entities, which significantly reduces operational costs compared to card acquiring. Fiscalization of SBP payments goes through the standard mechanism: you send a receipt with the attribute payment_method = 'sbp' to the OFD. A separate online cash register is not required — the same cash register as for cards is used. With proper setup in Bitrix, receipts are sent automatically upon payment confirmation via webhook from the bank.

Refunds and cancellations

When refunding an SBP payment, the money is returned to the buyer's account instantly (unlike cards, where there may be a delay). In Bitrix, implement the refund via the bank's Refund endpoint:

$refund = tinkoffPost('/v2/Refund', [ 'PaymentId' => $paymentId, 'TerminalKey' => TINKOFF_TERMINAL, ]); 

Partial refunds are also supported — pass the refund amount separately from the total payment amount.

More about SBP on Wikipedia

Our experience and connection time

We have implemented over 50 payment system integrations on 1C-Bitrix in recent years. Certified Bitrix specialists guarantee stable operation under load. Average times:

If you want to connect SBP to your project, contact us — we will assess the scope of work for free and offer the optimal solution. Get a consultation on SBP implementation today.