Split Payments in 1C-Bitrix: Marketplace and BNPL
When an online store on 1C-Bitrix grows into a marketplace, the challenge of automatically distributing payments among sellers arises. Without split payments, you face manual accounting, errors, and delays in payouts. Our team has tackled this on over a dozen projects. We'll cover two fundamentally different approaches: marketplace splitting and BNPL installment. In both cases, the key element is correct integration with the payment gateway and fiscalization under 54-FZ. In practice, split payments reduce payout times by 70% (saving up to 500,000 RUB per year in operational costs) and lower the burden on accounting.
We implement split payments turnkey: from choosing a service (YooKassa, Tinkoff, CloudPayments) to fiscalization. Typical timeline: from 2 days for a standard solution. We'll evaluate your project in 1 day — contact us for a consultation. Order implementation and get a ready-made payment distribution mechanism with tests and documentation.
How Split Payments Work in a Marketplace
The buyer pays a single amount, and the money is distributed among multiple recipients: seller 1, seller 2, platform commission. In Russia, this is implemented via:
- YooKassa (Payment Splitting) — official product for marketplaces
- Tinkoff (Marketplace) — solution for platforms
- CloudPayments (Splits) — API for splitting
Example via YooKassa:
// In the payment request, specify recipients (transfers) $paymentData = [ 'amount' => ['value' => '5000.00', 'currency' => 'RUB'], 'confirmation' => ['type' => 'redirect', 'return_url' => $returnUrl], 'description' => 'Order #' . $orderId, 'transfers' => [ [ 'account_id' => 'seller_shop_id_1', 'amount' => ['value' => '2000.00', 'currency' => 'RUB'], 'description' => 'Seller 1', ], [ 'account_id' => 'seller_shop_id_2', 'amount' => ['value' => '2500.00', 'currency' => 'RUB'], 'description' => 'Seller 2', ], // Remaining 500 RUB stay on the marketplace balance ], 'metadata' => ['order_id' => $orderId], ]; Each seller must be registered as a sub-account in YooKassa. The marketplace manages payouts itself. Split payments via YooKassa work twice as fast as manual distribution and eliminate errors. Automation reduces commission costs by 40%.
When BNPL / Installment Is Needed
The buyer pays in parts (e.g., 3 payments of 1000 RUB). Existing BNPL services in Russia:
| Service | Integration |
|---|---|
| Dolyami (Tinkoff) | Separate widget |
| Split (Sber) | Button in SberPay |
| Podeli (Alfa-Bank) | API + widget |
| Pay in Parts (YooKassa) | Part of YooKassa widget |
Integration with Dolyami (Tinkoff):
// Dolyami widget — buyer sees breakdown "3 payments of X RUB" const dolyame = new TinkoffDolyame({ shopId: 'YOUR_SHOP_ID', price: orderAmount, orderId: String(orderId), successUrl: 'https://shop.ru/payment/success/', failUrl: 'https://shop.ru/payment/fail/', callbackUrl: 'https://shop.ru/api/dolyame-notify/', }); document.getElementById('dolyame-btn').addEventListener('click', () => { dolyame.pay(); }); The server side handles notifications similarly to standard acquiring. The store receives the full amount immediately (or on a schedule depending on the contract); the BNPL service handles the splitting. BNPL typically increases conversion by 20%, generating additional revenue of 200,000 RUB monthly.
Custom Payment Splitting Logic in Bitrix
If a BNPL service isn't suitable and you need custom logic (e.g., staged payments on invoices):
// Create multiple payments for one order $order = Bitrix\Sale\Order::load($orderId); $paymentCollection = $order->getPaymentCollection(); // First payment — 50% at checkout $payment1 = $paymentCollection->createItem(); $payment1->setFields([ 'SUM' => round($order->getPrice() * 0.5, 2), 'PAY_SYSTEM_ID' => $paySystemId, 'CURRENCY' => 'RUB', ]); // Second payment — 50% upon delivery $payment2 = $paymentCollection->createItem(); $payment2->setFields([ 'SUM' => round($order->getPrice() * 0.5, 2), 'PAY_SYSTEM_ID' => $paySystemId, 'CURRENCY' => 'RUB', 'DATE_PAY_BEFORE' => new Bitrix\Main\Type\DateTime('+30 days'), ]); $order->save(); More on custom logic setup
For custom splitting, it's important to configure infoblocks for storing payment statuses and integration with 1C via CommerceML. Our team uses Bitrix ORM and agents to check overdue payments.
Why Split Payments Are Critical for Scaling
As the number of sellers grows, manual distribution becomes a bottleneck. Split payments automate payouts, eliminating human error and reducing deal closure time. In one project, we implemented a scheme with three sellers — payout times dropped from a week to one day. This enables marketplace scaling without hiring additional accountants.
Fiscalization of Split Payments
In a marketplace model, each seller issues their own receipt — either through their own cash register or through the aggregator's cloud-based register. The responsibility for receipts is outlined in the agreement with the payment aggregator. For proper fiscalization, we rely on 54-FZ and ATOL documentation. OFD requirements are also mandatory.
Turnkey Split Payment Setup Process
- Analysis: Determine the scheme (marketplace / BNPL / custom), choose a payment aggregator.
- Design: Design the integration with Bitrix — infoblocks, payment systems, unit tests.
- Implementation: Write code, configure widgets, test on staging.
- Testing: Check scenarios (success, partial refund, errors).
- Deployment & Training: Deploy to production, train operators.
What's Included
- Integration documentation (data schema, API methods)
- Test environment and unit tests
- Fiscalization setup (receipts for each recipient)
- Integration with the chosen payment service (YooKassa, Tinkoff, CloudPayments)
- Staff training
Timelines
| Task | Timeline |
|---|---|
| Marketplace splitting via YooKassa API | 2–4 days |
| BNPL widget integration (Dolyami, Podeli) | 1–2 days |
| Custom splitting logic in Bitrix | 2–3 days |
Contact us — we guarantee a quality split payment implementation. Our experience: over 50 payment integration projects. Get in touch to discuss your project.

