Setting Up Internet Acquiring on 1C-Bitrix | Custom Payment Processing

How to Set Up Internet Acquiring on 1C-Bitrix?

The task of "connecting card payment" seems trivial until the first production incident: order statuses don't update, money arrived but the order hangs in "Awaiting payment". The reason is that the bank's webhook doesn't reach the server due to WAF or PHP error. One project — an auto parts online store with a catalog of 50,000 items. When migrating to a dedicated server, Cloudflare blocked POST requests from the bank. Diagnosis took two hours, solution — configuring firewall exceptions. Afterwards, we developed a universal checklist for checking notification delivery. We, engineers with ten years of experience in Bitrix development, will cover the full cycle: from choosing a scheme to diagnostics. Our approach — reliability and transparency, we guarantee the integration works.

More about webhook technology can be read on Wikipedia Webhook.

Three Approaches to Integration

Ready Module from Marketplace — Sberbank, Tinkoff, YooKassa, Alfa-Bank have official modules. Installed via /bitrix/admin/update_system.php. Fast, vendor-supported, but limited flexibility.

Custom Handler in /local/ — when the standard module doesn't cover needs: non-standard status mapping, custom fiscalization, multiple acquirers.

JS Widget Acquiring — CloudPayments, Robokassa embed via a script. Part of the work on the client, server only verifies the result.

Installation and Configuration (Example: Tinkoff)

After installing the module from the Marketplace: Store → Settings → Payment Systems → Add → Tinkoff.

Custom Handler: Minimal Skeleton

<?php
// local/php_interface/include/sale_payment/mybank/handler.php

use Bitrix\Sale\PaySystem\BaseServiceHandler;
use Bitrix\Sale\PaySystem\ServiceResult;
use Bitrix\Sale\Payment;
use Bitrix\Main\Request;

class MyBankHandler extends BaseServiceHandler
{
    public function initiatePay(Payment $payment, Request $request): ServiceResult
    {
        $result = new ServiceResult();
        $order  = $payment->getCollection()->getOrder();

        $session = $this->createGatewaySession(
            $order->getId(),
            $payment->getSum()
        );

        if (empty($session['payUrl'])) {
            $result->addError(new \Bitrix\Main\Error('Gateway error: ' . ($session['error'] ?? '')));
            return $result;
        }

        $result->setPaymentUrl($session['payUrl']);
        return $result;
    }

    public function processRequest(Payment $payment, Request $request): ServiceResult
    {
        $result = new ServiceResult();
        $data   = json_decode(file_get_contents('php://input'), true);

        // ALWAYS verify signature — don't trust request data
        if (!$this->verifySignature($data)) {
            $result->addError(new \Bitrix\Main\Error('Invalid signature'));
            return $result;
        }

        if (($data['status'] ?? '') === 'PAID') {
            $result->setOperationType(ServiceResult::MONEY_COMING);
        }

        return $result;
    }
}

Diagnostics: Webhook Not Arriving

The most common reason — order statuses don't change, though money is debited. Diagnostic algorithm:

# 1. Check endpoint accessibility from outside
curl -v -X POST https://shop.ru/bitrix/tools/sale_ps_result.php \
  -d 'test=1'
# Should return 200, not 403

# 2. Check access.log for requests from bank IP
grep "sale_ps_result" /var/log/nginx/access.log | tail -50

# 3. Temporary logging (debug only!)
file_put_contents('/tmp/ps_debug.log',
    date('Y-m-d H:i:s') . ' ' . $_SERVER['REMOTE_ADDR'] . ' '
    . file_get_contents('php://input') . PHP_EOL, FILE_APPEND
);

Typical culprits: Cloudflare Bot Fight Mode blocks POST requests without User-Agent; fail2ban blocks bank IP by request count; PHP fatal error without log entry; HTTP→HTTPS redirect loses POST body.

Why a Custom Handler is Better Than a Ready Module?

A ready module doesn't allow flexible mapping of order statuses: for example, Tinkoff's "SUCCESS" status could mean "Paid" or "Awaiting confirmation". A custom handler gives 100% control over the logic, plus the ability to combine multiple acquirers into one interface. When integrating with 1C and fiscalization (54-FZ), a custom approach is mandatory — ready modules often don't support ATOL in non-standard scenarios. 54-FZ requirements are regulated by Federal Law.

When is Fiscalization Needed?

Fiscalization is mandatory for all online payments in the Russian Federation. When paying by card, a fiscal receipt must be sent to the buyer electronically. Setting up fiscalization includes integration with OFD and ATOL. In our stack — ATOL Online, which supports 54-FZ. Connecting fiscalization adds 1–2 days to the development timeline.

How We Ensure Integration Reliability?

After setup, we conduct load testing: emulate up to 50 simultaneous requests from the bank, check correct handling of duplicates and failures. For critical stores, we configure webhook monitoring via cron — every 5 minutes check that the endpoint returns 200. In the contract, we stipulate a delivery guarantee: if the order is paid, the status will change within a maximum of 30 seconds.

Two-Stage Acquiring

For stores that ship after reserving goods:

// On order placement — hold (PayType=T for Tinkoff)
// On status change to "Shipped" — confirm capture

AddEventHandler('sale', 'OnSaleStatusOrder', function(\Bitrix\Main\Event $event) {
    $order = $event->getParameter('ENTITY');
    if ($order->getField('STATUS_ID') !== 'OD') return;

    foreach ($order->getPaymentCollection() as $payment) {
        if ($payment->getField('PS_STATUS') === 'hold') {
            capturePayment($payment->getField('PS_INVOICE_ID'));
        }
    }
});

What's Included?

The full package when ordering acquiring setup: audit of the current payment system, selection of the optimal scheme, development or customization of the handler (including fiscalization), webhook configuration and notification delivery testing, integration with 1C (status exchange, synchronization), documentation of settings and logging, warranty support for 1 month after launch.

Timelines and Our Numbers

We have been working with 1C-Bitrix for over 10 years and have completed 200+ projects for online stores and B2B portals. Over 50 of them with custom acquiring. In case of issues, we respond within 2 hours, provide certificates of conformity.

The cost is calculated individually — contact us to evaluate your project. Order the acquiring setup service and get a reliable integration.

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.