YooKassa Payment Integration in 1C-Bitrix

Imagine: a customer places an order, proceeds to payment — but after a successful transaction, the webhook never arrives, the order status doesn't update, and the money hangs in limbo. YooKassa (formerly Yandex.Kassa) is one of the most popular payment aggregators in Russia, but the standard module from the Marketplace doesn't cover all scenarios. We've faced situations where notifications didn't come through, refunds failed with errors, and fiscalization produced invalid receipts. According to official YooKassa documentation, REST API version 3 allows flexible transaction management but requires careful setup. Over five years, we've completed more than 50 integrations — from simple stores to B2B platforms with tens of thousands of monthly transactions. Below, we break down the technical details and show how to avoid common pitfalls.

How YooKassa Works Technically

YooKassa provides a REST API (api.yookassa.ru/v3/). The classic payment flow:

1. The store sends POST /payments with amount, currency, and confirmation.type=redirect — YooKassa returns payment.id and confirmation.confirmation_url.
2. The customer is redirected to the YooKassa payment page.
3. After payment, YooKassa sends a webhook notification to the return_url and a POST to the configured notification URL.
4. The store calls GET /payments/{id} for final status verification.

Authentication: HTTP Basic with shopId:secretKey or OAuth token.

Supported payment methods: bank cards, SBP, YooMoney, SberPay, Tinkoff, QIWI (with limitations), cash via terminals. The method is passed in payment_method_type or chosen by the customer on the YooKassa form.

Why Choose Custom Integration

The official YooKassa module for Bitrix is available for free and works for standard stores. However, it has limitations: rigid binding to standard components, difficulty customizing order statuses, and lack of flexible fiscalization. A custom handler solves these issues and allows integrating YooKassa with any non-standard entities. Our experience shows that custom integration handles non-standard tasks 2-3 times faster than modifying the ready module. We are certified specialists with over 5 years of experience, guaranteeing correct operation across all scenarios. Contact us to evaluate your project — get a consultation on integration and exact timelines for your case.

How to Configure Webhooks for YooKassa

YooKassa sends a POST to the configured URL whenever the payment status changes. In Bitrix, the default handler URL is /bitrix/tools/sale_ps_result.php. Critical points:

• Verify the source IP address. YooKassa publishes its IP ranges: 185.71.76.0/27, 185.71.77.0/27, 77.75.153.0/25, 77.75.156.11, 77.75.156.35. Without filtering, you risk fake notifications.
• Verify the status via API. Don't trust webhook data directly — make a GET /payments/{id} for double-checking.
• Only handle terminal statuses. pending and waiting_for_capture do not require order changes.

// Sample handling
$body = file_get_contents('php://input');
$notification = json_decode($body, true);
$payment = $client->getPaymentInfo($notification['object']['id']);

switch ($payment->getStatus()) {
    case 'succeeded':
        $bitrixPayment->setPaid('Y');
        $bitrixPayment->save();
        break;
    case 'canceled':
        // Log the cancellation reason
        break;
}

Key Request Parameters

// Minimal payment creation request via SDK
use YooKassa\Client;

$client = new Client();
$client->setAuth($shopId, $secretKey);

$payment = $client->createPayment([
    'amount' => [
        'value'    => number_format($order->getPrice(), 2, '.', ''),
        'currency' => 'RUB',
    ],
    'confirmation' => [
        'type'       => 'redirect',
        'return_url' => 'https://shop.ru/personal/order/detail/' . $order->getId() . '/',
    ],
    'capture'     => true,  // false for two-stage payments
    'description' => 'Order #' . $order->getAccountNumber(),
    'metadata'    => ['bitrix_order_id' => $order->getId()],
    'receipt'     => $receiptData,  // mandatory if online cash register is connected
], uniqid('', true)); // idempotency key

capture: true — single-stage payment, funds are charged immediately. capture: false — two-stage: YooKassa holds the amount, and the store calls POST /payments/{id}/capture upon shipment.

The idempotency key (third parameter) is mandatory. Without it, a repeated request due to a network error will create a duplicate payment.

Fiscalization (54-FZ) and Why It's Mandatory

The requirements of 54-FZ (on the use of cash register equipment) apply to all online payments. YooKassa acts as a fiscal registrar, sending data to the OFD. If your YooKassa contract includes receipt transmission, the receipt object in the request becomes mandatory. Without it, the transaction will be rejected — this is one of the most common problems. The receipt structure must exactly match 54-FZ requirements. We use a proven schema with breakdown by VAT rates and item attributes. The total amount of all items in the receipt must exactly match the payment amount — YooKassa checks this on their side. Refunds also require a receipt that mirrors the original items. The official YooKassa documentation provides receipt structure examples, but we adapt them to your specifics.

Payment Statuses and Refunds

YooKassa supports partial and full refunds via POST /refunds. If a cash register is connected, a refund without a receipt is rejected. The refund receipt mirrors the original receipt items with type refund. We've implemented over 50 successful integrations with refunds, guaranteeing correct accounting.

Testing

YooKassa provides a test environment with the same endpoints. In test mode (shopId=test_...), payments proceed with test cards:

• 5555555555554477 — successful payment
• 5555555555554444 — decline

Be sure to test: successful payment, cancellation, delayed webhook (customer closes the browser before redirect), and partial refund. This helps avoid issues on the live site.

What's Included

• Audit of the current Bitrix configuration and trade catalog
• Development or refinement of the payment handler (with 54-FZ compliance)
• Webhook configuration and notification handling
• Testing all scenarios in the test environment
• Integration documentation and operator instructions
• 30-day warranty support after commissioning

Timelines and How to Start

Contact us to evaluate your project. Get a consultation on integration and exact timelines for your case. For more details, refer to the official YooKassa API documentation. About 54-FZ requirements, read on Wikipedia.

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.