ERIP Payment Integration for 1C-Bitrix in Belarus

We have often encountered situations where a Belarusian online store loses up to 30% of orders simply because the list of payment methods does not include ERIP. For the local market, this is not just an option but a necessity — over 90% of all non-cash payments in Belarus go through the Unified Settlement and Information Space. Without ERIP, you cut off a significant part of the audience accustomed to paying via ATMs, internet banking, or mobile apps.

Why ERIP is more profitable than card acquiring

ERIP is not instant payment, but a process: the store registers an invoice through the bank agent's API, the buyer receives a number or QR code and pays it at any bank or terminal. Then the system sends a notification. The ERIP commission is 5–10 times lower (0–0.5%) compared to acquiring (1–3%). The average payment confirmation time is 5–15 minutes after payment.

Comparison with classic acquiring:

Why ERIP is critically important for Belarusian e-commerce

According to National Bank, about 40% of the population does not use bank cards for online payments, preferring terminals and internet banking. ERIP provides access to this audience, increasing conversion by 10–20%. A typical online store receives 50–200 ERIP transactions per day, 70% of which are recurring.

How we implement ERIP integration in 1C-Bitrix

Since there is no single API, integration is built as a custom payment system handler for the sale module, adapted to the specific bank's API. Typical handler structure in /local/php_interface/include/sale_payment/erip/:

handler.php         — logic for invoicing and status checking
.description.php    — metadata, name, icon
.settings.php       — bankApiUrl, merchantId, apiKey, serviceCode
template/           — display of payment details to the buyer

{
  "merchantId": "YOUR_MERCHANT_ID",
  "serviceCode": "ERIP_SERVICE_CODE",
  "invoiceNumber": "ORD-12345",
  "amount": 125.50,
  "currency": "BYN",
  "description": "Payment for order No. 12345",
  "expireAt": "YYYY-MM-DDTHH:MM:SS",
  "callbackUrl": "https://yourshop.by/bitrix/tools/sale_ps_result.php",
  "returnUrl": "https://yourshop.by/personal/order/detail/12345/"
}

serviceCode — service code in the ERIP tree, assigned by the bank upon connection. It is used by the buyer to find the store in the ERIP menu ("Online stores → Category → Your store").

How to display payment details to the buyer?

After issuing the invoice, show:

• The ERIP invoice number (or QR code) for manual payment.
• Instructions: "Internet banking → ERIP → Search by number" or the path through the service tree.
• Invoice validity period (usually 24–72 hours).
• QR code for quick payment via mobile banking.

The template/ of the payment system component handles this screen. The standard "thank you for your order" page is not suitable here — you need a payment waiting page with dynamic status updates via AJAX or WebSocket.

How to process notifications and confirm payment?

The bank sends a POST notification to callbackUrl when a payment is received. The handler should:

1. Verify the request signature (HMAC, RSA, or IP whitelist depending on the bank).
2. Find the payment by invoiceNumber or billId.
3. Check the amount — the buyer may have partially paid.
4. Call $payment->setPaid('Y') only for full payment.
5. Update the order status according to business logic.

Partial payment — a specific feature of ERIP. The system allows partial payments. If this is undesirable, specify partialPaymentAllowed: false when registering the invoice.

From our practice: a Belarusian building materials store had a buyer pay an ERIP invoice, but the order was not confirmed due to a 1 BYN discrepancy from manual entry. The solution — add automatic manager notification for deviations up to 1% and a manual confirmation interface in the admin panel. In your project, we will foresee similar scenarios.

What is included in the work

• Analysis of the selected agent bank and obtaining API documentation.
• Development of a custom handler considering the bank's protocol specifics.
• Configuration of the payment details template and waiting page.
• Integration of webhook notifications and handling partial payments.
• Registration of the service in the ERIP tree (support from the bank side).
• Testing the full cycle: invoice issuance → payment → confirmation.
• Provision of setup and operation documentation.

Timeline and stages

Registration in the ERIP tree is the longest stage, independent of the developer. Start it in parallel with development.

Contact us to connect ERIP to your 1C-Bitrix online store — we will assess your project within 1 day and offer the optimal solution for your bank.

We rely on the official ERIP documentation and many years of experience with Bitrix 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.