Integrating 1C-Bitrix with Sberbank Online Payment System

Integrating 1C-Bitrix with Sberbank Online Payment System

We often encounter a common issue: an online store on Bitrix works perfectly, and orders flow in. However, buyers frequently call requesting to 'issue an invoice via Sber' — they don't see the payment button on the checkout page. Connecting Sberbank Online to Bitrix addresses this request and reveals several technical nuances not obvious at the 'just install the module' stage. In our practice, every third client comes with this pain: the absence of a payment method used by 60% of buyers. We have completed over 50 payment system integrations, so let's examine all the pitfalls.

Why the ready-made module doesn't always solve the problem?

The official sberbank.ecom module covers 80% of standard scenarios, but when non-standard logic is needed — for example, integration with 1C for automatic status changes or two-stage payment for pre-orders — the ready-made solution becomes a bottleneck. Comparison: the ready-made module is installed in 30 minutes, while a custom one requires 3–5 days but gives full control over payment processing. The speed-to-flexibility ratio is roughly 10:1, but custom development is 3 times more flexible.

How Sberbank's payment gateway works

Sberbank Online operates via the REST API of acquiring (securepayments.sberbank.ru/payment/rest/ for production, 3dsec.sberbank.ru/payment/rest/ for test). Interaction scheme:

1. The store calls register.do — registers the order in Sberbank's system, receives orderId and formUrl
2. The buyer is redirected to formUrl — Sberbank's payment page
3. After payment, Sberbank redirects the buyer to returnUrl and sends a notification to failUrl or performs a callback
4. The store calls getOrderStatus.do for final status verification

It is critically important not to rely solely on returnUrl for payment confirmation — the buyer may close the tab after payment without waiting for the redirect. A callback or periodic polling of getOrderStatus.do is always needed. Source: Sberbank Acquiring documentation

When is custom integration needed?

In the Bitrix ecosystem, Sberbank Online is implemented as a payment system handler of the sale module. There are two paths.

Ready-made module from the Marketplace. The official module from Sberbank (sberbank.ecom) is available on marketplace.1c-bitrix.ru. After installation, in the section Store → Settings → Payment Systems, a new type appears with fields userName, password (or token for the new authentication scheme). The module registers the handler \Sale\Handlers\PaySystem\SberbankHandler and a webhook URL like /bitrix/tools/sale_ps_result.php.

Custom handler is needed when: a non-standard order scheme is used, integration with 1C for automatic status changes is required, or the ready-made module conflicts with other components. It is placed in /local/php_interface/include/sale_payment/sberbank_custom/, with standard structure for Sale PaySystem.

Key parameters when registering an order

The register.do call requires mandatory parameters:

For fiscalization (54-FZ), the request includes an orderBundle object with product items, VAT rates, and payment object signs. Without orderBundle, Sberbank's cash register will not generate a receipt — this is a common reason for tax authority claims against stores that 'supposedly connected an online cash register'. More details on requirements — on Wikipedia.

Notification handling and statuses

Sberbank sends a POST notification to checkUrl when the transaction status changes. In Bitrix, the callback handler must:

1. Accept POST, parse mdOrder and orderNumber
2. Call getOrderStatus.do to obtain the actual status (do not trust callback data without verification)
3. On status 2 (paid), call $payment->setPaid('Y') and save the transaction
4. Return response {"errorCode": 0} — otherwise Sberbank will retry

Status table for getOrderStatus.do:

Two-stage payment

How to avoid duplicate payments?

From our practice: an electronics online store on a modern Bitrix version. After switching from test to production environment, about 3% of transactions were duplicated — the buyer paid once, but two payments were recorded in the order. Cause: the returnUrl handler and callback arrived almost simultaneously, both succeeded in calling setPaid('Y'). Solution — add a check $payment->isPaid() before confirmation and use locking via \Bitrix\Main\Application::getConnection()->lock() during transaction processing.

Testing

Sberbank's test environment (3dsec.sberbank.ru) works with test cards from the documentation. Be sure to check:

• Successful payment with callback confirmation
• Cancellation on the payment page (buyer clicked 'Back')
• Session timeout (default 1200 seconds — Sberbank cancels unfinished orders)
• Correct receipt generation when fiscalization is enabled

What is included in the work?

• Audit of current Bitrix configuration and payment methods
• Setting up the ready-made module or developing a custom handler
• Integration with fiscalization (54-FZ) and cash register
• Testing all scenarios: success, failure, timeout, duplication
• Documentation (installation guide, API parameters, troubleshooting)
• Access to test environment for 30 days
• Training session (1 hour) for your team
• 30 days of post-launch support

Timeline and cost

Integration timeline depends on the configuration: installing a ready-made module without a cash register — from 1 to 2 days. Custom integration with 54-FZ, two-stage payment, and adaptation to non-standard order structure — from 3 to 7 business days. Prices: ready-made module installation from $200; custom integration from $800; full integration with fiscalization from $1,200. 80% of our clients choose custom integration for flexibility. We have been working with Bitrix for over 5 years and have implemented 50+ payment system integrations — this allows us to guarantee quality. Contact us to discuss the details of your integration. We will prepare a solution tailored to your business and take into account all the specifics.

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.