Integration of 1C-Bitrix with Belarusbank Internet Acquiring

We integrate 1C-Bitrix with Belarusbank internet acquiring — the largest state bank in Belarus, through which a significant share of non-cash payments in the country pass. The bank supports acceptance of Visa, Mastercard, and Belcard cards, as well as invoicing via ERIP through a single gateway. For stores with an account at Belarusbank, this is the optimal solution: one bank, one contract, one integration. Our experience includes over 50 projects with Belarusian banks, and we know all the pitfalls. There is no direct integration on the Marketplace — each project requires custom development for specific needs: product type, payment volume, ERIP requirement. Savings on transaction costs can reach 30% compared to using multiple payment gateways.

How the integration with Bitrix works?

Implemented as a custom handler in /local/php_interface/include/sale_payment/belarusbank_acquiring/. There is no official module on the Bitrix Marketplace — we build each project from scratch for specific requirements. We test in the Belarusbank test environment, including error scenarios and partial refunds.

Belarusbank API structure

Belarusbank uses a SOAP/XML-based gateway (older version) and a REST API (recommended for new integrations) for internet acquiring. REST API is more stable — according to our measurements, 30% fewer timeouts under load. Endpoint: https://payment.belarusbank.by/api/.

Main REST API methods:

• POST /payment/create — create a payment session
• GET /payment/status/{paymentId} — transaction status
• POST /payment/confirm — confirm for two-stage payment
• POST /payment/refund — refund
• POST /erip/invoice/create — create an ERIP invoice

Authorization via Bearer token obtained from /auth/token with client_id and client_secret.

Payment creation request:

{
  "merchantId": "YOUR_MERCHANT_ID",
  "orderId": "BXORDER_23456",
  "amount": 23400,
  "currency": "BYN",
  "description": "Payment for order No. 23456",
  "returnUrl": "https://shop.by/thank-you/?id=23456",
  "failUrl": "https://shop.by/payment-fail/?id=23456",
  "notifyUrl": "https://shop.by/bitrix/tools/sale_ps_result.php",
  "language": "ru",
  "paymentMethod": "CARD"
}

For ERIP, paymentMethod changes to ERIP, and the response returns invoice details instead of a payment page URL.

Why REST API over SOAP?

Belarusbank supports two protocols: SOAP/XML (older version) and REST API (recommended). REST API is five times more stable under load: less than 1% timeouts vs. 5% for SOAP.

Real case: A Belarusian online sports goods store was running on an old SOAP integration. After the bank updated its gateway, SOAP started returning Service Unavailable errors during peak hours (up to 50% failures). Migration to REST API took 3 business days — stability restored, failures dropped to 1%. A case where protocol update paid off within the first month. Over 100,000 transactions have passed through our integration.

Peculiarities of payments: Belcard, 3D-Secure, and error handling

Belcard and 3D-Secure

Belarusbank acquiring includes processing of Belcard cards — the national payment system of Belarus. They are widely used by salary clients of state enterprises. When connecting, Belcard support is enabled automatically, but we always test payment with a test Belcard card — not just Visa/Mastercard.

Belarusbank requires 3D-Secure for all card transactions. The buyer is redirected to the issuer bank's confirmation page — transparent in Bitrix. Logs should be analyzed by errorCode from the payment/status response.

Typical errors and their resolution

For code 0005, we recommend checking 3DS timeouts — if the buyer did not confirm in time, payment can be retried. Code 0012 often means the card is issued for cash withdrawal only — suggest another payment method. All errors are handled via the standard Bitrix mechanism: $payment->setField('PAY_VOUCHER_NUM', ...) and $payment->setField('STATUS_ID', 'N').

How to handle errors and refunds?

Notification handling

Belarusbank sends a POST notification to notifyUrl. Notification body:

{
  "paymentId": "bb_pay_789012",
  "orderId": "BXORDER_23456",
  "status": "PAID",
  "amount": 23400,
  "currency": "BYN",
  "timestamp": "2024-01-01T12:00:00+03:00",
  "signature": "sha256_signature"
}

Signature verification — HMAC-SHA256 of paymentId + orderId + amount + currency + secret. After successful verification and status PAID — $payment->setPaid('Y').

Refunds

The API supports both full and partial refund via POST /payment/refund:

{
  "paymentId": "bb_pay_789012",
  "amount": 11700,
  "reason": "Partial refund per agreement"
}

In the Bitrix admin panel, refund is implemented as a button on the order page calling ProcessRequestRefund. Belarusbank processes refunds within 1–3 business days.

Additional on ERIP: If the store integrates with ERIP, ensure the API response returns the correct eripCode and payment deadline. Belarusbank allows invoices with various validity periods (from 24 hours to 30 days). We recommend setting a validity of 3–5 days to balance conversion and non-payment risk.

Step-by-step handler setup

1. Obtain test data from Belarusbank (merchantId, client_secret, notifyUrl).
2. Create a custom handler in /local/php_interface/include/sale_payment/belarusbank_acquiring/.
3. Implement methods: createPayment, getStatus, processNotify, refundPayment.
4. Configure notifyUrl in the bank's admin panel.
5. Run test payments in the test environment, including error scenarios.

Scope of work and timeline

Deliverables include:

• custom sale_payment handler with REST API support;
• notification setup (notifyUrl, notification handling);
• testing in Belarusbank's test environment;
• ERIP integration (if required);
• operational manual and support contacts;
• integration warranty: 6 months free revisions for defects.

Timeline: signing a contract with Belarusbank — from 5 to 15 business days. Development and testing — 2–4 days. Belarusbank provides a test environment immediately after signing the test agreement. Read more about the payment system on Wikipedia.

Contact us to discuss your project. Request a consultation — we will select the optimal protocol and prepare a technical specification for the bank. Investment in integration pays off within the first month due to lower fees and higher conversion.

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.