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 1 million rubles per month, the savings amount to up to 18 thousand rubles. 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' => 'RUB'],
    '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.

How can you avoid typical mistakes when connecting payment systems on 1C-Bitrix?

The most common mistake during integration is forgetting about the callback. The customer paid for the order, the money was debited, but the status in b_sale_order did not update: the manager sees "Awaiting payment" and starts calling the client. The reason is an incorrect URL in the gateway settings or a handler that returns a 500 error for an atypical response structure. We offer services for connecting payment systems on 1C-Bitrix with full testing of all scenarios: successful payment, refusal, timeout, partial refund, duplicate callback.

Why are callbacks critical?

Each payment gateway sends a notification to your server. If the handler does not guarantee idempotency, a double call will lead to a double charge. We always implement a check by notification ID (external_id) and block repeated processing in \Bitrix\Sale\Order. It is also critical to set the callback URL in the aggregator's personal account – /bitrix/tools/sale_ps_result.php for the standard module. If you use a custom handler, we verify that it returns HTTP 200 even in case of parameter errors (the gateway should not repeat the request indefinitely).

use Bitrix\Sale\Order;
use Bitrix\Main\Application;

// Get notification data
$data = Application::getInstance()->getContext()->getRequest()->toArray();
// Check signature (depends on aggregator)
if (!checkSignature($data, 'SECRET_KEY')) {
    die('FAIL');
}
// Find order by external ID
$order = Order::loadByExternalId((int)$data['order_number']);
if ($order && $order->isPaid() === false) {
    $order->setField('PAYED', 'Y');
    $order->save();
}
echo 'OK';

How do we optimize payment flow for higher conversion?

How to choose a payment aggregator for 1C-Bitrix?

The choice of aggregator depends on the geography of customers, average order value, and need for installments. For Russia, the basic set is YooKassa (all main methods, fiscalization out of the box) and CloudPayments (widget on the page without redirect, Apple Pay). If you work with large corporate clients, add Sberbank (SberPay, SBP). For international sales, use Stripe or PayPal. We often use a two-tier scheme: main aggregator + backup (auto-switching on failure).

What payment gateways and methods do we use?

YooKassa

One contract – all main methods: Visa/MasterCard/MIR cards, YooMoney, SberPay, internet banking, installments. Fiscalization under 54-FZ out of the box (via the sale module). The standard handler /bitrix/modules/sale/handlers/paysystem/yandexpay/ covers basic scenarios. For holding (two-stage payment), subscriptions, or split payments, custom integration via YooKassa API v3. Callback is configured to /bitrix/tools/sale_ps_result.php, we parse notification and update \Bitrix\Sale\Order via setField('PAYED', 'Y').

CloudPayments

Focused on conversion: the payment widget directly on the checkout page, without redirect to an external domain. The customer does not leave the site – the abandonment rate during payment drops. It supports recurring payments (card tokenization via cryptogram), Apple Pay, and Google Pay. 3D Secure with intelligent routing – requested only for high fraud risk. Integration with Bitrix – via CloudPayments REST API and a custom handler in the sale module.

Tinkoff Payment

API integration via TinkoffPaymentAPI (ready-made module or manual implementation). QR code for payment via the app, "Tinkoff Credit" installment – critical for expensive goods. Partial refunds via the Cancel method – without calling the bank, everything from the Bitrix admin panel.

Sberbank (SberPay and SBP)

SberPay – payment via push notification or QR, SBP – commission 0.4–0.7% vs 1.5–2.5% for cards. This is a significant savings on volume. Holding via registerPreAuth / deposit API. Note that SberPay requires a separate agreement with the bank.

Apple Pay and Google Pay

Payment in two clicks, without entering card data. They are connected through an aggregator (YooKassa, CloudPayments, Tinkoff). Important nuances:

• Apple Pay requires domain verification: the file apple-developer-merchantid-domain-association in /.well-known/. Without it, the button will not appear.
• Button placement strictly according to Apple and Google guidelines – otherwise rejection in review.
• Fallback to the standard payment form if the device does not support contactless payment.

How do we handle installments, BNPL, and 54-FZ compliance?

If the average order value is above 30,000 RUB and conversion drops, installment removes the price barrier. We connect:

• Tinkoff Installment (3–24 months)
• Buy with Sber
• Mokka / Dolyami – BNPL: 4 payments, 0% for the buyer

Integration: widget with monthly payment calculation on the product card ("from 2,500 RUB/month"), order data transfer to the bank via API, status processing (approval, rejection, awaiting documents) in OnSaleStatusOrder handlers.

Fiscalization under 54-FZ is a mandatory requirement. The fine for a missing receipt is up to 100% of the payment amount. In accordance with Federal Law No. 54-FZ, an electronic receipt must be sent to the buyer. We connect ATOL Online, Orange Data, Module.Kassa, Evotor, Shtrikh-M. Setup in Bitrix – the "Cash Registers" section in the sale module:

• VAT rate, item and method of payment – an error in any field can lead to a fine during inspection.
• Receipts for prepayment and partial payment (two receipts: at payment and at shipment).
• Refund receipts upon cancellation via \Bitrix\Sale\Cashbox\Cashbox::addChecks().
• Monitoring: if the receipt is not sent, an alert to the manager.

When selling shoes, clothing, or perfumes, it is mandatory to transfer marking codes in the receipt. Integration with "Chestny ZNAK", scanning DataMatrix during order assembly, automatic removal from circulation upon sale via \Bitrix\Catalog\Product\Marking.

Payment support: refunds, multicurrency, security

Refunds

Full and partial refund without calling the bank – via the aggregator API (refund / cancel). The refund receipt is generated automatically, the order status is updated, the amount is recalculated, and the customer is notified. Timeframes: e-wallets and SBP – 1–3 days, bank card – up to 30 business days (depends on the issuing bank).

Multicurrency

Price types in b_catalog_price for each currency, rates via the Central Bank API (\Bitrix\Currency\CurrencyManager::updateCBRFRates()) or manual input. Conversion at the catalog level – the customer sees prices in their currency. For accepting dollars/euros, we connect Stripe, PayPal. We take into account conversion fees when calculating margin.

Security

Card data is processed on the certified gateway side (PCI DSS) – the card number never passes through your server. Anti-fraud at the aggregator level. Logging all events in b_sale_order_change for audit. Anomaly monitoring: transaction spike, atypical geography – alert.

How we work and estimated timelines

1. Analysis – what payment methods are needed, markets, transaction volume, current aggregator.
2. Solution selection – sometimes two aggregators are better than one: YooKassa as the main, CloudPayments as backup – if one fails, traffic goes to the second.
3. Integration – we test each scenario: successful payment, 3DS refusal, gateway timeout, double callback, partial refund.
4. Fiscalization – online cash register, checking the correctness of receipts on test orders.
5. Monitoring – alerts for gateway failures, conversion dashboard at the payment stage.

What is included in the work

• Full setup of selected payment systems in 1C-Bitrix: modules, handlers, callbacks, testing.
• Integration documentation (gateway operation scheme, handler description, logic).
• Training your manager to work with payment modules and refunds.
• Technical support during launch and the first 2 weeks of operation.
• Monitoring – we set up alerts for errors and conversion drops.

All work is performed by certified 1C-Bitrix developers. We guarantee the operability of each scenario. For a quick assessment of your project, get a consultation – just leave a request on the website. Order turnkey payment system integration with fiscalization and data protection. Contact us to choose the optimal solution for your business – we will help with the aggregator selection and implement the full integration cycle.