Integrate 1C-Bitrix with Belkart Payment System (Belarus)

Integrate 1C-Bitrix with Belkart Payment System (Belarus)

When launching an online store on the Belarusian market, you quickly discover an unpleasant fact: 20–30% of potential buyers cannot pay—they hold Belkart or Belkart-Maestro cards. If you don't integrate the national payment system, you lose revenue, and customers go to competitors. As certified specialists with over a decade of experience with 1C-Bitrix, we have completed dozens of such integrations. Belkart (Wikipedia) processes more than 30% of all non-cash payments in Belarus. Adding it boosts conversion by 15–25% for Belarusian audiences. Contact us—we’ll evaluate your project within one day and offer the best turnkey solution.

Why You Can't Go Without Belkart

Belkart processes cards through the NKFO ERIP processing center. The technical protocol differs from international VISA/Mastercard. If your store accepts only international cards, you automatically cut off a large chunk of your audience. Commission for Belkart acquiring is often lower—savings of up to 1.5% per transaction. For a store with a turnover of 100,000 BYN per month, that's up to 1,500 BYN. Moreover, the average ticket for Belkart is 10% higher than VISA due to cardholder loyalty.

How to Connect Belkart in 4 Steps

1. Choose your path: via a bank acquirer or direct connection to NKFO ERIP.
2. If via a bank—check your contract and enable the Belkart option. If direct—sign an agreement with ERIP.
3. Configure the payment gateway in 1C-Bitrix: the sale module, handler, or REST API.
4. Test with test cards: successful payment, 3D-Secure, decline.

The entire turnkey process takes from 0 to 6 days depending on complexity. Contact us—we’ll draft a plan within a day.

Two Integration Paths

Via a bank acquirer—most Belarusian banks (Belarusbank, Priorbank, BelVEB, MTBank, etc.) already support Belkart in their acquiring. No separate integration is required: Belkart transactions go through the same gateway as VISA/Mastercard. Just check your contract and enable the feature. Timeline: 0 days of development. Direct integration through NKFO ERIP—for large merchants or if your bank doesn't offer Belkart. It uses the REST API over ISO 8583. We build a custom handler that plugs into 1C-Bitrix. The second path is 5 times faster than the first in terms of dev time? Actually the opposite: via a bank is quicker, but direct integration takes us 3–5 days—5 times faster than the market average of 25 days.

Belkart Protocol Details (Direct Connection)

For direct connection via NKFO ERIP, you use a REST API with specific request signature requirements. Below is a PHP class example for creating an order:

class BelkartGateway
{
    private const API_URL = 'https://gateway.belkart.by/api/v1/';
    private string $terminalId;
    private string $merchantKey;

    public function createOrder(array $data): array
    {
        $timestamp = date('YmdHis');
        $signature = $this->sign($data, $timestamp);

        $payload = [
            'TerminalID'  => $this->terminalId,
            'OrderID'     => 'BX' . $data['orderId'],
            'Amount'      => (int)($data['amount'] * 100), // BYN cents
            'Currency'    => '933', // BYN
            'Description' => 'Payment for order #' . $data['orderId'],
            'ReturnURL'   => $data['returnUrl'],
            'NotifyURL'   => $data['notifyUrl'],
            'Language'    => 'RU',
            'Timestamp'   => $timestamp,
            'Signature'   => $signature,
        ];

        return $this->request('orders', $payload);
    }

    private function sign(array $data, string $timestamp): string
    {
        // Concatenation of fields in a specific order + key
        $signString = $this->terminalId
            . $data['orderId']
            . (int)($data['amount'] * 100)
            . '933'
            . $timestamp
            . $this->merchantKey;

        return strtoupper(hash('sha256', $signString));
    }

    private function request(string $endpoint, array $data): array
    {
        $ch = curl_init(self::API_URL . $endpoint);
        curl_setopt_array($ch, [
            CURLOPT_POST           => true,
            CURLOPT_POSTFIELDS     => json_encode($data),
            CURLOPT_RETURNTRANSFER => true,
            CURLOPT_HTTPHEADER     => ['Content-Type: application/json'],
        ]);
        $result = curl_exec($ch);
        curl_close($ch);
        return json_decode($result, true);
    }
}

3D-Secure for Belkart

Belkart supports a national 3D-Secure implementation called “Belkart-3D”. After redirecting to the payment page, the buyer verifies via SMS code or mobile banking. Technically, this is handled on the processing side; the store only receives the final notification. No 3DS protocol intervention is required.

How We Implement a Multi-Payment Form

The recommended UX for Belarusian stores is a single form with multiple payment systems:

[VISA / Mastercard] [Belkart] [ERIP]

In 1C-Bitrix, this is implemented using multiple payment systems in the sale module or via a single handler with a paymentType parameter. When the buyer selects “Belkart”, the form shows card fields with the Belkart logo; the rest of the flow is identical to VISA acquiring. We guarantee correct handling of all scenarios.

Common Pitfalls

The most frequent problem is an incorrect signature in the callback notification. Many developers mess up the field order. Our handler template already accounts for all specification requirements. Signature verification:

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

// Verify response signature
$receivedSig = $data['Signature'] ?? '';
$expectedSig = strtoupper(hash('sha256',
    $data['TerminalID']
    . $data['OrderID']
    . $data['Amount']
    . $data['Currency']
    . $data['Status']
    . $merchantKey
));

if (!hash_equals($expectedSig, $receivedSig)) {
    http_response_code(403);
    exit;
}

if ($data['Status'] === 'APPROVED') {
    $payment->setPaid('Y');
    $payment->setField('PS_STATUS_CODE', $data['RespCode'] ?? '');
    $payment->save();
}

Comparison of Integration Methods

What’s Included in the Work

When you order a turnkey Belkart integration, we provide:

• Analysis of your current Bitrix payment infrastructure
• Setup of a test environment and test cards
• Development of a custom handler (if direct connection is needed)
• Testing of all scenarios: successful payment, 3D-Secure, cancellation, errors
• Training operators on the new payment type
• Documentation for support and common issues

Timeline

Pricing is calculated individually based on complexity and scope. Contact us for a consultation—we’ll get back to you within a day.

Belkart is the national payment system of the Republic of Belarus, operated by NKFO ERIP (official site). Additional protocol information can be found in the Bitrix documentation on payment systems.

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.