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:

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();

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

1. Analysis: Determine the scheme (marketplace / BNPL / custom), choose a payment aggregator.
2. Design: Design the integration with Bitrix — infoblocks, payment systems, unit tests.
3. Implementation: Write code, configure widgets, test on staging.
4. Testing: Check scenarios (success, partial refund, errors).
5. 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

Contact us — we guarantee a quality split payment implementation. Our experience: over 50 payment integration projects. Get in touch to discuss your project.

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.