Payment Setup in Bitrix24: YooKassa, Sber, Fiscalization

Payment Integrations in Bitrix24.Store

Imagine: your store on Bitrix24.Store is running, orders are coming in, but at the payment stage — a failure. YooKassa rejects payments, fiscalization fails, order statuses in CRM don't update. Our experience — over 120 payment gateway integration projects — shows that a properly configured payment system is the foundation of conversion. Let's review typical problems and their solutions.

Available Payment Systems and Their Features

Bitrix24.Store supports YooKassa (Yandex Pay), Sberbank (online acquiring), Tinkoff, cash, bank transfer, cash on delivery, and Robokassa out of the box. Each system has its own setup requirements. YooKassa wins on the number of payment methods — a conversion advantage.

Why YooKassa Is the #1 Choice?

YooKassa processes transactions on average 1.5 times faster than Sberbank acquiring, thanks to direct HTTP notifications. This reduces payment confirmation time and lowers the risk of lost orders. Additionally, YooKassa supports all major payment methods: cards, SBP, YooMoney, Apple Pay, and Google Pay.

How to Set Up Webhook Correctly?

The webhook is the key element: it's how Bitrix24 learns about payment status changes. URL errors are the most common cause of non-working payments. After connecting YooKassa, copy the generated URL (like https://your-portal.bitrix24.ru/bitrix/services/sale/paysystem/handler.php?handler=Yookassa) into your YooKassa account under HTTP notifications. Without this, order statuses won't update automatically.

How to Connect YooKassa to Bitrix24?

In Bitrix24 interface: Store → Payment → Add → YooKassa. Required parameters:

• shopId — your store ID in YooKassa
• secretKey — secret key (from YooKassa settings)
• Payment methods — select available ones (card, SBP, YooMoney)
• Tax system and VAT rate — for automatic 54-FZ fiscalization

Webhook setup: The URL for notifications from YooKassa to Bitrix24 is generated automatically and displayed in the payment system settings. You need to manually add it to your YooKassa account (Integration → HTTP notifications).

What to Do If You Need a Non-Standard Payment System?

If your payment system is not supported out of the box, Bitrix24 allows creating a custom handler via REST API. This gives full control over payment logic. Example registration:

// Register custom payment system
BX24.callMethod('sale.paysystem.handler.add', {
    fields: {
        name: 'My payment system',
        code: 'my_payment',
        sort: 100,
        settings: {
            PAYMENT_GATEWAY_URL: { type: 'STRING', label: 'Gateway URL' },
            SHOP_ID: { type: 'STRING', label: 'Store ID' },
            SECRET_KEY: { type: 'STRING', label: 'Secret key' },
        },
    }
});

Fiscalization and 54-FZ: What You Need to Know?

Fiscalization is the mandatory transmission of payment data to the tax authority via a fiscal data operator (FDO). Bitrix24 automatically generates receipts if the payment system settings include the tax system and VAT rate. The payment gateway sends data to the FDO. Errors in fiscalization settings can result in fines of up to 50,000 rubles per receipt.

How to Avoid Payment Losses?

A common problem is mismatched tax rates between the store and the gateway. If YooKassa has one rate and Bitrix24 another, the receipt won't pass. Check settings before going live. Also ensure the FDO is registered and active. Fiscalization does not work in test mode — use production data on a separate staging environment for verification.

Process of Payment Setup: From Audit to Guarantee

1. Audit — we analyze your current payment systems, identify bottlenecks.
2. Selection — we recommend the optimal gateway for your business.
3. Connection — we set up the payment system, webhook, fiscalization.
4. 1C Integration — we configure data exchange for payments.
5. Testing — we verify all scenarios: successful payment, cancellation, errors.
6. Launch — we switch to production mode.
7. Support — 30 days of warranty service after launch.

What Is Included in the Result?

Upon completion, you receive:

• Configured payment system with webhook and fiscalization.
• Integration documentation (API keys, exchange schemas).
• Test report describing all verified scenarios.
• Support guide for typical incidents.
• 30-day warranty support.

Timelines

Cost is calculated individually after audit. The right gateway selection can significantly reduce acquiring fees. Order an audit — we evaluate your store in one business day. Get a consultation on payment setup right now.

Typical Mistakes During Setup

• Incorrect webhook URL — payments fail, statuses don't update.
• No test mode — production payments are lost on errors.
• Ignoring fiscalization — fines up to 50,000 rubles per receipt.

Our team's experience in integrating payment gateways in Bitrix24 — over 7 years, 120+ implemented projects. Contact us to get started.

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.