Payment Status Exchange Between 1C and Bitrix: Setup and Automation

Payment status exchange between 1C and 1C-Bitrix is a task that cannot be solved with standard tools without custom development. A typical situation: a customer paid via acquiring, the status changed in Bitrix, but 1C doesn't know about it. Or vice versa — an invoice was paid in 1C, but the website still shows 'awaiting payment'. Accountants spend hours on manual reconciliation, orders are not reserved in time, customers don't receive notifications. We configure automatic synchronization for each scenario: online acquiring, invoice payment, cash on delivery. Let's look at the technical details of status transmission, show a practical case, and discuss typical errors. Our team has been doing integrations for over 7 years and has completed more than 50 projects with bidirectional exchange.

Main Payment Scenarios

Automatic synchronization via scheduled task is 10 times faster than manual posting — confirmed by our practice.

How to Transfer Payment Status from Bitrix to 1C?

When a payment is successful in Bitrix, a payment object (Bitrix\Sale\Payment) is created with PAID = Y. During the next order exchange, this status is transmitted in XML:

<Документ>
  <Ид>order-guid</Ид>
  <Оплачен>true</Оплачен>
  <СуммаОплаты>4500.00</СуммаОплаты>
  <ДатаОплаты>today_date</ДатаОплаты>
</Документ>

In 1C, upon importing an order with <Оплачен>true</Оплачен>, you can configure automatic creation of a Cash Receipt document (for 1C:Accounting) or a transaction in the settlement register (for 1C:Trade Management). This automates online payment posting and frees the accountant from routine. Read more about the exchange format in the official CommerceML documentation.

How to Transfer Payment Status from 1C to Bitrix?

When a bank statement is posted in 1C and the Receipt document is processed, the order in Bitrix needs to be updated. The mechanism: when the status of an order document changes in 1C (or when a payment receipt is processed), mark the order as "Paid". During the next exchange, 1C sends the updated status.

On the Bitrix side, the order update handler:

// Upon receiving an order update from 1C
if ($arOrder['PAID'] === 'Y') {
    $payment = $order->getPaymentCollection()->getItemByIndex(0);
    if ($payment && $payment->isPaid() === false) {
        $payment->setPaid('Y');
        $order->save();
        // Trigger automatic events: email to the customer, manager notification
    }
}

Configuring Partial Payments

In B2B scenarios, partial payments are common: 30% advance → 70% remaining. In 1C, this is two receipt documents; in Bitrix, one order with multiple payments. When transferring partial payment from 1C to Bitrix, you can create separate payments for each receipt or update a single payment with the cumulative amount. The second option is simpler to implement. Indication for the customer: "Paid: 1,500 out of 5,000 RUB (30%)" — via a custom order property PAID_AMOUNT, updated at each exchange.

Configuring partial payments includes the following steps:

1. Determine which orders allow partial payment (e.g., B2B clients).
2. Configure 1C to generate multiple payments for one order.
3. Implement in Bitrix the update of a single payment with an amount equal to the sum of all receipts.

Refund Synchronization

Refunds are a critical case. If a refund is initiated in 1C, it must notify Bitrix to update the order status, trigger a refund via the acquiring system, and send a notification to the customer. If a refund is initiated via acquiring (chargeback), Bitrix receives a notification, changes the payment status to "Refunded" — this needs to be transmitted to 1C to create a refund document. Bidirectional refund synchronization eliminates accounting discrepancies.

Case Study: Real-Time Payment Synchronization

One of our clients — an online store with a high share of B2B (60% of orders paid by bank invoice). Problem: an order in 1C moved to "Paid" status only after manual processing of the bank statement (1–2 days). Customers saw an outdated status. We configured automatic bank statement loading in 1C via the 1C-DirectBank service. The statement is loaded and automatically posted every 30 minutes. After posting, a scheduled task triggers the exchange with Bitrix, updating the order status. The delay from payment receipt to status update on the site is 30–60 minutes. The customer receives an email confirming payment without manager intervention. Additionally, upon payment receipt in Bitrix, automatic stock reservation in 1C is launched.

What's Included in the Exchange Setup

As a result, you get: configured status exchange, documentation on the scheme, and employee training. The cost is calculated individually. We guarantee stable synchronization under any load.

Get a consultation on your project — we'll estimate the timeline and complexity. Order the setup of status exchange, and your accounting department will forget about manual reconciliation.

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.