1C-Bitrix Integration with Belagroprombank Acquiring

Lost notifications are a common problem when integrating with bank gateways. Incorrect HMAC configuration or timeouts cause payments to go through while order statuses in Bitrix remain unchanged. We solve this by implementing duplicate API status requests and verifying each notification. The result: zero payment loss and savings of up to 12,000 BYN per year in commissions for an average store.

We were approached by an agricultural holding with a catalog of 10,000 items and a monthly turnover of 500,000 BYN. After connecting standard Belagroprombank acquiring, they faced notification losses: customers paid, but orders remained in 'awaiting payment' status. The cause was incorrect verification settings and gateway timeouts. We developed a custom handler with HMAC check and duplicate status requests. Notifications no longer get lost, and average commission savings amount to about 12,000 BYN per year due to correct payment routing.

Our team has been doing Bitrix integrations for over 6 years — more than 50 projects with payment gateways, including REST API and handlers compliant with Federal Law 54-FZ requirements. We guarantee stable operation and provide documentation for accounting.

Problems we solve

• Belkart limits — the gateway automatically detects the card type, but during testing it often turns out that lower limits are set for Belkart. We configure monitoring and alerts to react promptly.
• Two-stage payment — for made-to-order items, amount blocking rather than deduction is required. Without two-stage mode, customers wait for a refund if the item is out of stock. We implement a 'Confirm deduction' button in the admin panel.
• Notifications — the bank sends POST requests, but if the URL is unreachable or verification is not configured, payments are lost. We add HMAC verification and IP filtering, plus duplicate status requests via API.

How to connect Belagroprombank internet acquiring to 1C-Bitrix?

1. Submit an application to the bank — sign a contract for internet acquiring (usually 7–14 business days).
2. Get test credentials — endpoint and account data for the test gateway.
3. Develop a custom handler — we create it in /local/php_interface/include/sale_payment/bapb_acquiring/. The handler registers the order, checks status, and processes refunds.
4. Configure notifications — specify the public handler URL and set up verification (HMAC or IP whitelist).
5. Perform testing — check all scenarios: successful payment, decline, refund, two-stage mode.
6. Activate production mode — after successful testing, switch to the production gateway.

Example of order registration via API:

{
  "merchantId": "BAPB_MERCHANT_ID",
  "orderNumber": "BXORDER_34567",
  "amount": 156800,
  "currency": "BYN",
  "returnUrl": "https://shop.by/order/success/34567/",
  "failUrl": "https://shop.by/order/fail/34567/",
  "notificationUrl": "https://shop.by/bitrix/tools/sale_ps_result.php",
  "description": "Online store: order #34567",
  "sessionTimeoutSecs": 1200
}

Why does two-stage payment cut refund time by 3 times?

For agricultural machinery stores where items may be made to order, the two-stage scheme saves time: first we block the amount, then after confirming availability we deduct it. With a single-stage scheme, upon cancellation the customer has to wait up to 8 business days for a refund. With two-stage — the block is released instantly, and money returns in 1–2 days. In Bitrix this is implemented via the 'Confirm deduction' button, which calls POST /orders/{orderId}/deposit.

How we sped up refunds for a garden equipment store

From practice: a Belarusian garden equipment store clicked 'Make refund' — the API returned success, but money arrived in 8 business days instead of 3. The cause: they used refund for a reserved (not deducted) amount. We fixed it by condition — void for status APPROVED, refund for DEPOSITED. Now refunds complete in 2–3 days.

Reporting and reconciliation

The bank provides registry API: GET /reports/transactions?dateFrom=...&dateTo=.... We automate downloading the report at the end of the day and compare with Bitrix data. If discrepancies appear, it's an immediate signal of unprocessed notifications.

What’s included in the work

• Custom payment handler with support for two-stage payment and refunds.
• Notification setup and verification (HMAC or IP whitelist).
• Automatic registry export for accounting.
• Setup and operation documentation.
• Employee training on refunds and reports.
• Technical support at launch.

Comparison of approaches: custom handler vs standard module

Timeline

Why choose us

• 1C-Bitrix certificate and over 6 years of integration experience.
• More than 50 completed projects with payment gateways.
• Result guarantee: the handler works without failures, notifications are not lost.
• We provide full documentation and post-launch support.

Order an integration — we will assess your project in 1 day. Get a consultation on connecting Belagroprombank acquiring to 1C-Bitrix.

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.