1C-Bitrix + CloudPayments: Widget, Subscriptions & Fiscalization

Integration of 1C-Bitrix with CloudPayments Payment System

Owners of online stores on 1C-Bitrix often face a drop in conversion during payment: redirecting to the bank page scares off up to 20% of buyers. CloudPayments solves this with the Checkout Widget — card data is entered directly on the site, increasing conversion by 15–25%. We perform a turnkey integration with CloudPayments: redirect-free widget, recurring payments, fiscalization under 54-FZ. Basic integration starts from 50,000 RUB and typical savings vs alternatives reach 30%. Based on our data, cost is determined after analysis of the project scope.

CloudPayments Increases Conversion in Bitrix

CloudPayments offers two payment schemes. Checkout Widget — a JS widget, the form opens in a popup or inline. Card data goes directly to the gateway (PCI DSS), only the transaction token goes to your server. This is secure and does not require certification. The redirect-free API requires the store to collect card data on its own and transmit via REST — this approach is almost never used due to PCI DSS requirements.

Typical conversion with redirect is 2–3%, with the widget it's 4–6%. The difference is especially noticeable on mobile devices. CloudPayments gives conversion 2.5 times higher than using redirect. The widget is configured in 2–3 days, including server callbacks. For comparison, integration with Sberbank via API takes 5–7 days, with lower conversion. Moreover, CloudPayments widget integration is 2x faster than T-Cassa setup.

CloudPayments is More Profitable than Alternatives

CloudPayments provides ready-made fiscalization — you don't need to write your own module for the OFD. This saves up to 40% of development time.

Step-by-Step Instructions to Set Up CloudPayments Widget in Bitrix

1. Obtain public and secret keys in your CloudPayments account.
2. In the order template (bitrix:sale.order.checkout component), add a link to the widget script:

<script src="https://widget.cloudpayments.ru/bundles/cloudpayments.js"></script>

3. Initialize the widget with order parameters (amount, description, invoiceId).
4. Handle onSuccess and onFail callbacks — in onSuccess send a request to the server to confirm payment.
5. Set up server handlers check and pay with HMAC signature verification.
6. Test scenarios: successful payment, cancellation, error.

Connecting the Widget

On the Bitrix checkout page (bitrix:sale.order.checkout component), add the script and initialize the widget:

<script src="https://widget.cloudpayments.ru/bundles/cloudpayments.js"></script>

<script>
var widget = new cp.CloudPayments({language: 'ru-RU'});
widget.pay('auth',  // 'auth' — two-stage, 'charge' — one-stage
    {
        publicId: 'pk_XXXXX',
        description: 'Оплата заказа #<?= $orderId ?>',
        amount: <?= $amount ?>,
        currency: 'RUB',
        invoiceId: '<?= $orderId ?>',
        accountId: '<?= $userId ?>',
        skin: 'mini',
        data: {
            orderId: '<?= $orderId ?>',
            csrfToken: '<?= bitrix_sessid() ?>',
        }
    },
    {
        onSuccess: function(options) {
            // Платёж прошёл — уведомить сервер
            fetch('/bitrix/tools/sale_ps_result.php', {
                method: 'POST',
                body: JSON.stringify({ orderId: options.invoiceId }),
            });
        },
        onFail: function(reason, options) {
            console.error('Payment failed:', reason);
        }
    }
);
</script>

In Bitrix, the widget is connected in the component template or in result_modifier.php. We pass invoiceId — the order number, by which we later confirm payment.

Server-side Processing: check and pay Notifications

CloudPayments sends two POST requests to your endpoint: Check — before charging, the store must respond with {"code":0} if the order exists; Pay — after successful charge, payment confirmation.

Handler (local/payment/cloudpayments/callback.php):

$data = json_decode(file_get_contents('php://input'), true);

// Проверка HMAC подписи
$hmac = base64_encode(hash_hmac('sha256', file_get_contents('php://input'), $apiSecret, true));
if ($hmac !== $_SERVER['HTTP_CONTENT_HMAC']) {
    http_response_code(403);
    exit;
}

$invoiceId = $data['InvoiceId'];  // наш orderId
$status    = $data['Status'];     // 'Completed', 'Cancelled' и т.д.

if ($status === 'Completed') {
    // Найти платёж по orderId, подтвердить
    $order = \Bitrix\Sale\Order::loadByAccountNumber($invoiceId);
    $paymentCollection = $order->getPaymentCollection();
    foreach ($paymentCollection as $payment) {
        if ($payment->getPaySystem()->getField('CODE') === 'cloudpayments') {
            $payment->setPaid('Y');
        }
    }
    $order->save();
}

header('Content-Type: application/json');
echo json_encode(['code' => 0]);

Signature verification is mandatory. CloudPayments passes HMAC SHA-256 in the Content-HMAC header. Without verification, an attacker could confirm payment with a fake POST. More details: Wikipedia: HMAC.

A common error is incorrect HMAC. To fix, ensure you use the secret key (not public) and take the raw request body (file_get_contents('php://input')). Compute HMAC before decoding JSON.

Recurring Payments

CloudPayments supports subscriptions: on the first payment, a card token (Token) is created, subsequent charges are made without buyer participation:

// Первый платёж с сохранением токена — через виджет с параметром createReceipt
// Последующие платежи через API
$response = $this->apiRequest('payments/tokens/charge', [
    'Amount'      => 999,
    'Currency'    => 'RUB',
    'InvoiceId'   => $subscriptionId,
    'AccountId'   => $userId,
    'Token'       => $savedToken,
    'Description' => 'Подписка за февраль',
]);

The token is stored in the database (e.g., in an HL-block), linked to the Bitrix user. The commission for recurring payments is the same as for regular ones.

Fiscalization Requirements

CloudPayments integrates with online cash registers via the cloudPayments.CustomerReceipt parameter in the widget request. You pass an array of order items, VAT rate, taxation system. CloudPayments itself generates the receipt via the connected cash register and sends it to the buyer's email or SMS.

Example of passing data to the widget:

var receipt = {
    Items: [
        {
            label: 'Товар 1',
            price: 500.00,
            quantity: 1,
            amount: 500.00,
            vat: 20,
        }
    ],
    taxationSystem: 0, // ОСН
    email: '[email protected]',
    phone: '+71234567890',
};
widget.pay('charge', { ..., cloudPayments: { customerReceipt: receipt } });

What is Included in the Work

When ordering integration, you get:

• Setting up the widget on the checkout page.
• Handler for check/pay notifications with signature verification.
• Integration of recurring payments (optional).
• Fiscalization with transfer of receipts (optional).
• Testing all scenarios: success, cancellation, error.
• Documentation on integration and access (logs, admin panel).
• Consultations on setting up the online cash register in CloudPayments.
• Training for your team and ongoing support.

Development Timeline

Our team has over 5 years of experience with Bitrix and payment systems, with 50+ successful integrations. We guarantee proper implementation and provide full documentation and support. Get a consultation on setting up CloudPayments. Contact us — we will calculate the exact timeline within 1 day. For an accurate estimate, contact our engineers.

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.