Integrating 1C-Bitrix with Split Services (Yandex Split, Dolyami)

Integration of 1C-Bitrix with Split Services (Yandex Split, Dolyami)

A buyer often abandons a large purchase if the price hits the budget. Split payment is a mechanism that divides the amount into 2–4 installments without interest and without a credit agreement. We, a team with 10 years of Bitrix experience, have already integrated Yandex Split and Dolyami for dozens of online stores. Let's tell you how to do this technically competently, what pitfalls you'll face, and how to avoid them.

How split payment works in Bitrix

Split services do not give the buyer a loan—they pay the store the full amount immediately (or within 1–2 days), and then collect payments from the buyer themselves. For 1C-Bitrix, this is a regular payment system: create a handler, receive a webhook with confirmation, mark the order as paid. The difference is in the API and status model: fewer intermediate statuses than in credit systems.

Comparison of Yandex Split and Dolyami

Both services solve the same problem but differ in limits and audience. Yandex Split allows splitting amounts from 1,000 to 150,000 rubles into 2–4 payments. Dolyami — from 500 to 30,000 rubles into 4 payments. Yandex Split is better for expensive goods (electronics, furniture), while Dolyami is for average ticket items (clothing, cosmetics). We recommend connecting both: on the checkout page we display two buttons, and the buyer chooses their service.

Technical implementation of Yandex Split

Yandex Split is embedded via the Yandex Pay SDK. On the checkout page, include a JavaScript button with the parameter paymentType: 'SPLIT'. After confirmation, Yandex sends a webhook to your callbackUrl. The handler in 1C-Bitrix must:

1. Verify the JWT token from the header.
2. Create an order (\Bitrix\Sale\Order::create).
3. Confirm via API (POST /api/merchant/v1/orders/{orderId}/capture).

Example handler in /local/php_interface/include/sale_payment/yandex_split/:

public function initiatePay(
    \Bitrix\Sale\Payment $payment,
    \Bitrix\Main\Request $request = null
) {
    $this->setExtraParams([
        'MERCHANT_ID' => $this->getBusinessValue($payment, 'MERCHANT_ID'),
        'CART_ITEMS' => $this->getCartItems($payment),
        'AMOUNT' => $payment->getSum(),
    ]);
    return $this->showTemplate($payment, 'template');
}

The template template/template.php renders the Yandex Pay button with the SPLIT parameter.

Technical implementation of Dolyami

The "Dolyami" service from T-Bank uses a REST API. Endpoint: https://partner.dolyame.ru/v1/orders. Authorization: HTTP Basic Auth + X509 certificate signature. Creating an order:

$response = $this->apiRequest('POST', '/v1/orders', [
    'id' => $payment->getField('ORDER_ID'),
    'amount' => $payment->getSum(),
    'prepaid_amount' => 0,
    'items' => $this->formatItems($payment),
    'client_info' => [
        'first_name' => $order->getPropertyValue('NAME'),
        'last_name' => $order->getPropertyValue('LAST_NAME'),
        'phone' => $order->getPropertyValue('PHONE'),
        'email' => $order->getPropertyValue('EMAIL'),
    ],
    'notification_url' => $this->getCallbackUrl($payment),
    'success_url' => $this->getSuccessUrl($payment),
    'fail_url' => $this->getFailUrl($payment),
]);

The API returns a link — redirect to the confirmation page.

Status model and refunds

Both services support partial refunds. For Yandex: POST /api/merchant/v1/orders/{orderId}/refund, for Dolyami: POST /v1/orders/{orderId}/refund. With a partial refund, the service recalculates the buyer's schedule, and only the excess amount is returned to the store.

Our approach: a real case

One of our clients, an electronics retailer with 5,000 orders per month, experienced payment confirmation delays of up to 10 seconds due to synchronous webhook processing. We moved the webhook handling to a Bitrix agent queue, implemented idempotency checks, and optimized the order creation logic. Result: average confirmation time dropped to 1.5 seconds, and lost orders due to timeout decreased by 80%. This is the typical depth we bring to every integration.

What the service includes

• Analysis of the current payment system and cart.
• Development of two handlers (Yandex Split and Dolyami) with webhook processing.
• Integration with 1C (order status exchange).
• Testing on test and real orders.
• Operational documentation.
• Training for managers on refund handling.

The cost is calculated individually, timeline is from 3 to 5 working days.

Security and monitoring of split integrations

Both services send webhook notifications with a signature that must be verified on the server side. For Yandex Split, the signature is in the JWT token of the Authorization header; for Dolyami, via HMAC-SHA256 in the X-Signature header. Without signature verification, an attacker could emulate payment confirmation and get the goods for free.

We recommend setting up webhook queue monitoring: if a confirmation status doesn't arrive within 10 minutes, send a repeat request via the service API. Both providers support manual order status checks via GET /api/merchant/v1/orders/{orderId} (Yandex) and GET /v1/orders/{id} (Dolyami). This protects against lost orders during temporary network failures.

For high-traffic stores (over 200 orders per day), we recommend processing webhooks through a task queue—for example, via Bitrix agents or Redis Queue—so as not to block the HTTP response to the service. The endpoint must respond within 3 seconds, otherwise the service will repeat the notification. Configure handler idempotency: upon receiving the same webhook twice, the order status should not change twice. This is done by checking the current payment status before updating and skipping the notification if the status is already set.

Advantages of our integration

Over 200 successful projects integrating payment systems with 1C-Bitrix, 10+ years on the market, in-house certified specialists. We use official SDKs and follow vendor recommendations (Yandex Pay SDK, Dolyami API).

Contact us — we'll evaluate your project and offer the best solution.

CommerceML: Why Standard Exchange Is Both a Lifesaver and a Trap

Standard exchange via CommerceML 2.0 on typical "Trade Management" or "Comprehensive Automation" can be set up in a day or two. Products, prices, stock, orders—all via XML files on a schedule. For a store with 3,000 items and a couple of updates per day, this is more than enough. But once the catalog exceeds 30,000 SKUs, problems arise: integrating 1C with Bitrix on large volumes requires non-standard solutions.

Why does CommerceML slow down with catalogs over 100,000 items?

bitrix_1c_exchange.php generates XML on the Bitrix side, and 1C retrieves and parses it. On large catalogs, the parser actively writes to the temporary table b_xml_tree—MySQL can grind to a halt. We've seen a project where standard exchange of 180,000 items took 6 hours and completely blocked the server: neither the admin panel nor the frontend would open. The solution is incremental exchange. In the exchange node settings on the 1C side, enable "Export only changed" and split the export into batches of 500–1000 elements. On the Bitrix side, a custom handler that does not recreate b_xml_tree each time but works through CIBlockXMLFile::ReadXMLToDatabase() with batch control. A catalog of 200,000 SKUs updates in 8–12 minutes.

Another pitfall is EXTERNAL_ID. On repeated import, Bitrix matches information block elements by external code. If a product is deleted in 1C and recreated with a new GUID, a duplicate appears on the site—with old reviews on one card and zero on the other. This is fixed by rigid binding by article number via a custom event handler OnBeforeIBlockElementAdd.

How to avoid duplicates during repeated import?

We bind products not by GUID but by article number. Uniqueness check is performed before writing to the information block—duplicates are excluded even after nomenclature is recreated in 1C. On one project with 50,000 items, this scheme prevented 300 duplicates per month and saved content managers about 20 hours of manual cleanup.

Custom 1C Configurations: When CommerceML Falls Short

"We have a standard configuration"—says every second client, and then we open the database and see 200 custom processing routines, renamed attributes, and custom sales documents. CommerceML works with a fixed XML structure. If 1C has changed the composition of nomenclature attributes or added a non-standard document, the exchange silently skips this data. Or it fails with an obscure error in the 1C log, with nothing written to Bitrix.

In such cases, we implement custom export. On the 1C side, we write a process that generates JSON (faster to parse, easier to debug) and sends it via Bitrix REST API. Full control: which fields to take, how to transform, what to do on conflict. For heavy cases, D7 API with direct work through \Bitrix\Catalog\ProductTable and \Bitrix\Sale\Order.

What are the key steps to set up 1C integration?

Custom REST is justified when:

• Non-standard nomenclature attributes;
• Multiple price types (retail, wholesale, dealer, promotional, regional, currency)—standard exchange sends only one type;
• Multi-warehouse with different stock levels and need to select a warehouse on the site.

Prices, Stock, and Multi-Warehouse

Standard exchange can transfer one price type. In reality, there may be 15: each with its own buyer group and priority. Mapping between 1C price groups and Bitrix user groups is a separate engineering challenge. Especially when discounts overlap and you need to determine which price wins.

Multi-warehouse adds another layer: product is in stock in Moscow, out of stock in St. Petersburg, and "on order" in Novosibirsk. The site must show availability per location, allow selection of pickup points, and calculate shipping from the nearest warehouse where the product is physically available. The standard Bitrix warehouse module (catalog.store) handles display, but we write the "which warehouse to ship from" logic separately. For one manufacturing holding, we implemented a custom stock aggregator that calculated balance across 8 warehouses in 2 seconds—reducing shipping errors by 80%.

Orders and Document Flow

An order from the site goes to 1C, a sales document is created, goods are reserved. Statuses come back. The main nuance is partial shipment: the client ordered 5 items, 3 are in stock, 2 will arrive in a week. 1C creates two sales documents. Bitrix out of the box cannot split one order into several shipments—we extend the OnSaleOrderSaved handler to create child orders and synchronize statuses for each.

Documents in the personal account—invoices, acts, waybills from 1C—are served via REST; PDF is generated on the 1C side and cached on CDN. The buyer downloads not from 1C directly (that would kill the server) but from cache.

Batch import with portion control reduces MySQL load and prevents locks (source: Wikipedia).

Monitoring: Not "Set and Forget"

Exchange can silently break: the script ran, no errors in log, but 200 products didn't update due to invalid UTF-8 in the name. Or 1C changed the date format in an update—all prices came in as zero.

Minimum set we install on every project:

• Telegram alert if exchange time increases 3+ times from average.
• Stock discrepancy check: script compares b_catalog_product.QUANTITY with what 1C provides, and alerts when delta exceeds 5%.
• Dashboard: last sync, number of processed items, queue, errors.

For high-load projects, we add async queues on Redis or RabbitMQ. Exchange does not block the web server, data is not lost during temporary 1C outages. On one online store with 2 million orders per year, we implemented this scheme—recovery time after failures dropped from 3 hours to 10 minutes.

Linking with Bitrix24 for Document Flow Automation

If besides the site there is a corporate portal on Bitrix24, we link it too. Counterparties from CRM go to 1C, invoices from 1C appear in deal cards. The manager sees accounts receivable and mutual settlements without switching windows. Deal closed—documents generated automatically.

Payment received in 1C → logistician gets a task for shipment in Bitrix24. Goods shipped → manager sees notification. Automatic tasks based on events from 1C—via Bitrix24 REST API webhooks. This link reduces manual entry by 70% and eliminates forgotten shipments.

How We Set Up Integration: Step-by-Step Process

1. Audit of 1C Configuration. Review the structure of directories, documents, attributes. Identify custom modifications. Assess data volume (number of SKUs, orders, warehouses).
2. Design Exchange Schema. Agree on data set: products, prices, stock, orders, documents. Determine sync interval and mechanism—CommerceML or custom REST.
3. Configure Standard Exchange. Set up CommerceML, batch mode, binding by article. Verify data transfer correctness on a test catalog.
4. Extended Integration. For complex configurations, write custom handlers on both 1C and Bitrix sides. Incorporate multi-warehouse, multiple prices, partial shipment.
5. Monitoring and Warranty. Set up alerts, dashboard, documentation. Train operators. After launch, warranty support.

Timelines and What's Included

Work results include: documented exchange schema, configured synchronization scenarios, monitoring dashboard, operator training, and warranty support after launch. Pricing is calculated individually—it depends on the complexity of the 1C configuration, catalog size, and required automation level. We'll evaluate your project in 1 day—write to us, let's discuss. Order integration and get stable exchange in 1–2 weeks.

We have completed over 50 1C integrations for online stores and manufacturing companies. The team's average experience is 7 years, and we have certified 1C-Bitrix specialists. Our experience ensures that the exchange won't break in the first month and will run stably for years. For example, on a project with a catalog of 50,000 items, automation of exchange saved the client significant operational costs annually.

Contact us for a free audit of your 1C configuration—we'll find bottlenecks and offer the optimal solution.