SberPay Installment for 1C-Bitrix – Complete Setup

Introduction

A common technical issue for 1C-Bitrix online stores is low conversion on big purchases due to the absence of installment or credit options. The customer is ready to buy but not to pay the full amount upfront, and if the store doesn't support credit, they move to a competitor. The "Pokupay so Sberom" service (SberPay installment) solves this: the buyer fills out an application on the store page, gets a decision within 2 minutes (for Sber cardholders), and the store immediately receives the money. We integrate this mechanism into your 1C-Bitrix store turnkey—from application submission to acceptance testing and launch. Our certified 1C-Bitrix developers have over 5 years of market experience and have successfully completed more than 50 SberPay integrations. Guaranteed success in passing acceptance testing on the first attempt. Order the integration and we'll guide you through every step.

How does integration increase conversion?

Sber's clients make up about 60% of Russia's population. Integration increases payment conversion by 15–25% compared to a regular card. The store receives the money immediately after the contract is signed, while the buyer pays the bank in installments. Based on our data, the approval rate for applications is 20–30% higher than for similar services like Tinkoff or Pochta Bank, thanks to a more lenient scoring system. In fact, according to our statistics, Sber application approval is 1.5 times higher than Tinkoff.

Integration principle and connection process

The mechanics: the buyer selects "Pokupay so Sberom" at checkout, the store sends the order data to the Sber API, and the buyer is redirected to a Sber page to fill out the application. Scoring takes from 2 minutes for Sber clients; after approval and signing the contract, the store receives a callback notification, and the order is considered paid. 95% of Sber cardholders receive a decision within 2 minutes.

The connection process includes registering a partner at sberbank.ru (legal entity verification takes 1–2 weeks), signing the agreement, obtaining credentials (partnerId, partnerToken), then technical integration and mandatory acceptance testing. Without passing this, production access is not granted—Sber checks the correct transfer of products, status handling, and refunds.

Implementing a payment handler for 1C-Bitrix

The handler is created in /local/php_interface/include/sale_payment/sber_credit/. The class extends \Bitrix\Sale\PaySystem\ServiceHandler. The key method initiatePay forms the request to the Sber API:

$orderData = [
    'partnerOrderId' => $payment->getField('ORDER_ID'),
    'amount' => $payment->getSum(),
    'currency' => 'RUB',
    'returnUrl' => $this->getSuccessUrl($payment),
    'failUrl' => $this->getFailUrl($payment),
    'callbackUrl' => $this->getCallbackUrl($payment),
    'items' => []
];

$basket = $payment->getOrder()->getBasket();
foreach ($basket as $item) {
    $orderData['items'][] = [
        'name' => $item->getField('NAME'),
        'quantity' => $item->getQuantity(),
        'price' => $item->getPrice(),
        'sum' => $item->getPrice() * $item->getQuantity(),
        'category' => $this->mapCategory($item),
    ];
}

Important: the total sum of all product items in items must exactly match amount. A discrepancy of even 1 kopeck will lead to application rejection.

For product categorization, you need to map infoblock sections to Sber's fixed categories (electronics, clothing, furniture, household, other). This is implemented through a custom section property (UF_SBER_CATEGORY) or a separate mapping table. Without correct categorization, applications may be rejected.

Status handling and refunds

Sber sends POST notifications to the callbackUrl on status changes. The handler must verify the HMAC-SHA256 signature, find the payment by partnerOrderId, and update the status. The status model includes CREATED, PROCESSING, APPROVED, SIGNED, REJECTED, CANCELED, REFUNDED. Payment is considered paid upon SIGNED status.

Refunds (full and partial) via the refund API. The handler sends the request and waits for a callback with the result. The money is returned to the customer within 1–5 business days.

Adding the monthly payment widget

Sber provides a JS widget that shows the monthly payment amount. Insert it into the bitrix:catalog.element template via component_epilog.php:

<div id="sber-credit-widget" data-sum="80000"></div>
<script src="https://iss.sberbank.ru/partner/widget.js" data-partner-id="YOUR_ID"></script>

The widget automatically calculates and displays "from X rub/month" next to the price.

Comparison with alternatives

According to estimates, the approval rate for Sber applications is 15–20% higher due to a larger customer base and more lenient scoring.

Work process and timelines

1. Analytics: we study the current catalog, category mapping.
2. Design: handler scheme and status model.
3. Implementation: writing the handler, widget, refunds.
4. Testing in Sber sandbox and passing acceptance testing.
5. Deployment to production and support.

Implementation time — from 2 to 4 weeks, depending on catalog complexity. Acceptance testing may take 1–3 days.

What is included in the work

• Assistance in obtaining partner access from Sber;
• Development of the payment handler tailored to your catalog;
• Product categorization (section mapping);
• Integration of callback notifications;
• Connection of the widget on the product card;
• Testing in the sandbox and passing acceptance;
• Provision of access to the technical API documentation;
• Training staff to work with the admin panel;
• Documentation and support for a month after launch.

Pricing and savings

Integration cost — from 120,000 rubles. Save on commissions: Sber charges lower fees than many alternatives, and the increased conversion typically pays for the integration within 3–6 months. Contact us for a project assessment or order turnkey integration. Get a consultation — we'll estimate the scope in 2 days.

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.