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 los

Our competencies:

Frequently Asked Questions

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

Parameter Via bank acquirer Direct connection (ERIP)
Complexity Zero code Development + certification
Timeline 0 days 4–6 days
Commission Standard bank Negotiable, often lower
Control Minimal Full

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

Task Timeline
Integration via bank acquirer (no extra code) 0 days — already in acquiring
Custom handler for direct connection 3–5 days
Testing with Belkart test cards 1 day

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.