SberPay Installment for 1C-Bitrix – Turnkey Integration

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

Our competencies:

Frequently Asked Questions

Latest works

  • B2B ADVANCE company website development
    B2B ADVANCE company website development
    1460
  • Website development for FIXPER company
    Website development for FIXPER company
    1019
  • Development based on Bitrix, Bitrix24, 1C for the company Development of an Online Appointment Booking Widget for a Medical Center
    Development based on Bitrix, Bitrix24, 1C for the company Development of an Online Appointment Booking Widget for a Medical Center
    764
  • Development based on 1C Enterprise for MIRSANBEL
    Development based on 1C Enterprise for MIRSANBEL
    882
  • Website development on CRM Bitrix24 for DOLBIMBY
    Website development on CRM Bitrix24 for DOLBIMBY
    809
  • Development based on Bitrix24 for the company TECHNOTORGKOMPLEKS
    Development based on Bitrix24 for the company TECHNOTORGKOMPLEKS
    1166

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:

Example code
$orderData = [ 'partnerOrderId' => $payment->getField('ORDER_ID'), 'amount' => $payment->getSum(), 'currency' => 'USD', '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

Criteria Pokupay so Sberom Tinkoff Credit
Audience ~60% of population ~30% of Tinkoff users
Minimum amount depends on scope depends on scope
Scoring speed 2 min (for Sber clients) up to 5 min
API documentation Closed (after contract) Open
Acceptance testing Strict Simplified

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 $1.1k–1.6k. 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.