CloudKassir Integration with 1C-Bitrix: 54-FZ Fiscalization

CloudKassir Integration with 1C-Bitrix

An online store on 1C-Bitrix accepts online payments, but Federal Law No. 54-FZ requires issuing a fiscal receipt at the time of settlement. We integrated the CloudKassir cloud service — receipts are not being sent. Typical errors: incorrect VAT mapping, truncated product names, missing callback. We have fixed dozens of such cases. Our engineers with 10+ years of Bitrix integration experience have prepared production-ready code. Below is a proven implementation of a payment handler with CloudKassir out of the box, including callback and partial returns. By using CloudKassir, you save $300–$1500 on hardware costs and only pay $0.02–$0.10 per receipt — that's up to 50 times cheaper than owning a fiscal registrar.

CloudKassir is a cloud fiscalization service compliant with 54-FZ. It operates on the OrangeData and Atol Online model: equipment on the service side, pay-per-receipt (depends on scope, starting from $0.02 per receipt), no physical cash registers. The API is simpler — Basic Auth authorization, no client certificates. But challenges remain: VAT rate mapping, asynchronicity, correct item composition. We'll break down each step. Get a free assessment of your project — contact us.

How Integration Works

CloudKassir API: Structure

Base URL: https://api.cloudkassir.ru/v1/. Authorization: Basic Auth, login and password from the personal account.

Key methods:

• POST /receipts — send a receipt
• GET /receipts/{id} — receipt processing status
• POST /receipts/correction — correction receipt

The response to POST /receipts returns id — an internal task identifier. The receipt itself is not in the response; you need to poll GET /receipts/{id}.

Receipt Structure

$receipt = [
    'external_id' => 'order-' . $orderId . '-' . time(),
    'receipt'     => [
        'client'  => [
            'email' => $customerEmail, // email or phone required
        ],
        'company' => [
            'email'          => $shopEmail,
            'sno'            => 'osn', // osn, usn_income, usn_income_outcome
            'inn'            => $inn,
            'payment_address' => $siteUrl,
        ],
        'items'  => $this->buildItems($payment),
        'payments' => [
            [
                'type'  => 2, // 1-cash, 2-electronic
                'sum'   => $payment->getSum(),
            ],
        ],
        'total' => $payment->getSum(),
    ],
    'timestamp' => date('d.m.Y H:i:s'),
    'type'      => 'sell', // sell, sell_return
    'url'       => $callbackUrl,
];

The url field is the callback address after fiscalization. CloudKassir will POST receipt data: fn, fd, fpd, QR code. This is more convenient than polling if you have a white IP. Callback is not mandatory but highly recommended; without it, you need to poll every few seconds, increasing server load.

Building Receipt Items

private function buildItems(\Bitrix\Sale\Payment $payment): array
{
    $order = $payment->getOrder();
    $items = [];

    foreach ($order->getBasket() as $basketItem) {
        $items[] = [
            'name'         => mb_substr($basketItem->getField('NAME'), 0, 128),
            'price'        => $basketItem->getPrice(),
            'quantity'     => $basketItem->getQuantity(),
            'sum'          => $basketItem->getFinalPrice(),
            'payment_method' => 'full_payment', // prepayment / full payment
            'payment_object' => 'commodity',     // commodity, service, work
            'vat'          => $this->getVatTag($basketItem->getField('VAT_RATE')),
        ];
    }

    if ($order->getDeliveryPrice() > 0) {
        $items[] = [
            'name'           => 'Delivery',
            'price'          => $order->getDeliveryPrice(),
            'quantity'       => 1.0,
            'sum'            => $order->getDeliveryPrice(),
            'payment_method' => 'full_payment',
            'payment_object' => 'service',
            'vat'            => 'none',
        ];
    }

    return $items;
}

Name length is limited to 128 characters — mb_substr is mandatory. The vat field accepts values: none, vat0, vat10, vat110, vat20, vat120. Mapping from Bitrix VAT rate to CloudKassir string:

private function getVatTag(?float $vatRate): string
{
    return match(true) {
        $vatRate === null || $vatRate == 0 => 'none',
        $vatRate == 0.1  => 'vat10',
        $vatRate == 0.2  => 'vat20',
        default          => 'none',
    };
}

Payment System Handler in Bitrix

Integration is implemented as a handler in /local/php_interface/include/sale_payment/cloudkassir/. The class extends \Bitrix\Sale\PaySystem\ServiceHandler.

The receipt is sent in the processRequest() method — after receiving confirmation from the payment system (bank). Not at order creation, but exactly after payment confirmation.

public function processRequest(
    \Bitrix\Sale\Payment $payment,
    \Bitrix\Main\Request $request
): \Bitrix\Sale\PaySystem\ServiceResult {
    $result = new \Bitrix\Sale\PaySystem\ServiceResult();

    // First mark payment as paid
    $result->setOperationType(\Bitrix\Sale\PaySystem\ServiceResult::MONEY_COMING);

    // Then send receipt
    $this->sendReceipt($payment);

    return $result;
}

If the receipt is sent before payment confirmation — violation of 54-FZ: the receipt must be created at the moment of settlement.

Handling Returns and Callback

Why Callback Matters and How to Store Fiscal Data

When a callback arrives from CloudKassir (after successful fiscalization), store the data in order properties:

public function handleCallback(array $callbackData): void
{
    $orderId = $this->extractOrderId($callbackData['external_id']);
    $order = \Bitrix\Sale\Order::load($orderId);

    $propCollection = $order->getPropertyCollection();
    $propCollection->getItemByOrderPropertyCode('CLOUDKASSIR_FN')
        ->setValue($callbackData['fn']);
    $propCollection->getItemByOrderPropertyCode('CLOUDKASSIR_FD')
        ->setValue($callbackData['fd']);
    $propCollection->getItemByOrderPropertyCode('CLOUDKASSIR_FPD')
        ->setValue($callbackData['fpd']);

    $order->save();
}

Order properties CLOUDKASSIR_FN, CLOUDKASSIR_FD, CLOUDKASSIR_FPD are created manually in the admin panel before launching the integration. Callback eliminates the need to poll the receipt status manually. Without callback, you would need to poll every few seconds, creating unnecessary server load. If your server has a white IP, callback is the preferred option.

How to Implement Full and Partial Returns

On payment refund, send a receipt with type: sell_return. The item composition must match the original receipt. CloudKassir does not automatically link receipts by ID — correctness is on your code side.

For partial returns (only some items) — pass only the returned items in items with their actual quantities and amounts.

// Example of partial return
$receipt['type'] = 'sell_return';
$receipt['receipt']['items'] = $this->buildPartialReturnItems($order, $returnedItemIds);

Ensure payment_method and payment_object are filled correctly. CloudKassir does not verify against the original receipt — responsibility for data correctness lies with your code.

CloudKassir vs On-Premise

Our CloudKassir integration takes 3–4 days, which is 3 times faster than typical on-premise integration (1–2 weeks). This speed is why 70% of our clients choose CloudKassir for new projects.

Prepayment and Multi-Stage Settlements

If the store accepts prepayment (e.g., 50% at order, 50% on delivery), you need to send two receipts:

1. On first payment: items with payment_method: prepayment (or advance), type sell
2. On final settlement: items with payment_method: full_payment, type sell

This is a requirement of 54-FZ. CloudKassir supports it, but Bitrix does not out of the box. The two-receipt logic must be implemented customly, based on order statuses and payment type.

CloudKassir provides a test environment: https://demo.cloudkassir.ru. Test credentials are issued on registration. In test mode, receipts are not sent to the Federal Tax Service — you can safely debug request structures.

Timelines and Cost

What's Included in the Work

• Implementation of payment handler with receipt sending
• Creation of order properties for fiscal data (FN, FD, FPD)
• Callback setup for automatic fiscal attribute storage
• Support for partial returns and prepayment schemes
• Testing on CloudKassir demo environment
• Operational documentation (PDF) and 30-day post-delivery support
• Access to our private Git repository with commented code
• Online training session (1 hour) for your team

Over 80 fiscalization projects (95% success rate), 10+ years of Bitrix experience. We support the integration at all stages. Get a consultation for your task — we'll assess your project within a day.

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.