Seamless Hutkі Grosh Payment Integration for 1C-Bitrix

The problem: offline buyers can't pay online

In Belarus, a significant portion of buyers don't use bank cards – they actively pay through Hutkі Grosh self-service terminals. If your 1C-Bitrix store doesn't accept these payments, you're losing up to 30% of your audience from the regions. We solve this by integrating Hutkі Grosh with your 1C-Bitrix store, allowing customers to pay at any terminal, gas station, or post office. Our experience shows that after integration, conversion to payment for such orders reaches 85–90%.

How the Hutkі Grosh integration with Bitrix works

Once connected, you gain an additional payment channel with no card acquiring fees. The customer selects “Pay via terminal” at checkout, receives a payment code, and visits a nearby terminal. Within minutes, the order is automatically confirmed – no manager intervention needed. We have over 5 years of Bitrix experience and have successfully integrated more than 50 payment systems, confirming our expertise.

Technical mechanism: from XML request to confirmation

Hutkі Grosh provides an XML-based API, based on the CommerceML protocol (adapted for payment requests). The workflow:

1. The shop registers an invoice via API (POST XML packet to Hutkі Grosh gateway)
2. The system returns a transactionId and paymentCode
3. The customer pays using the code at a terminal, e-wallet, or app
4. The system sends a notification to the shop's callbackUrl

Unlike card acquiring, payment may arrive hours or days later – the customer chooses the convenient moment. This is especially important in regions where Hutkі Grosh terminals are installed at every Belpochta branch.

How to develop a custom handler?

There is no official module, so we implement a custom one at /local/php_interface/include/sale_payment/hutki_grosh/. The API accepts XML:

<?xml version="1.0" encoding="UTF-8"?>
<request>
  <service_id>YOUR_SERVICE_ID</service_id>
  <merchant_id>YOUR_MERCHANT_ID</merchant_id>
  <order_id>BXORDER_78901</order_id>
  <amount>125000</amount>
  <currency>BYN</currency>
  <description>Payment for order #78901</description>
  <callback_url>https://shop.by/bitrix/tools/sale_ps_result.php</callback_url>
  <return_url>https://shop.by/personal/order/detail/78901/</return_url>
  <expire_date>2027-12-25</expire_date>
  <signature>md5_hash</signature>
</request>

The amount is in Belarusian kopecks. The signature is MD5 of merchant_id + order_id + amount + currency + secret_key. The expire_date is generated dynamically (typically +7 days).

Display to the customer and AJAX polling

After creating the invoice, you need to show:

• Payment code (10–12 digits) – to be entered at the terminal
• Instructions: "Select Hutkі Grosh → Pay by code → Enter code"
• A terminal map (provided by Hutkі Grosh)
• Code validity period (usually 3–7 days)
• QR code for mobile app payment

In the component template, it's crucial to implement a waiting page with AJAX polling of the status – customers often return to the site after payment and want to see confirmation.

Handling callback notifications

Hutkі Grosh sends an XML notification to the callback_url:

<notification>
  <transaction_id>hg_txn_556677</transaction_id>
  <order_id>BXORDER_78901</order_id>
  <status>PAID</status>
  <amount>125000</amount>
  <paid_at>2027-12-23T09:15:00+03:00</paid_at>
  <signature>md5_verification_hash</signature>
</notification>

The order of processing in processRequest:

1. Parse XML (SimpleXMLElement or DOMDocument)
2. Verify the signature
3. Check the amount
4. Find payment by order_id in b_sale_payment
5. On status PAID – $payment->setPaid('Y')
6. Return <response><result>OK</result></response>

If you don't return a correct response, the system will retry for up to 24 hours.

Expiration and cancellation

When the expire_date passes, the system changes the status to EXPIRED. We recommend setting up a cron job to check:

// Request current status
$response = $this->apiRequest('GET', '/invoice/' . $transactionId);
if ($response['status'] === 'EXPIRED') {
    // Update order status, notify customer
}

What the work includes

• Development of a custom handler (payment system, template, callback handler)
• Setup of a waiting page with AJAX polling
• Integration with your shopping cart and checkout component
• Testing on the production environment
• Documentation for the handler and operator instructions
• 6-month code warranty

We have over 5 years of Bitrix experience and have successfully integrated more than 50 payment systems. This expertise is backed by 1C-Bitrix certificates.

Case study: automating weekend payments

From our client's practice: a Belarusian building materials store. Customers paid via terminals on Friday evenings and Saturdays; callbacks arrived on time, but managers didn't work on weekends and there was no automatic processing. Orders remained pending until Monday. We set up automatic order confirmation via callback without manager involvement and added Telegram notifications. As a result, 40% of orders started being confirmed instantly, and repeat purchase conversion increased by 15%.

Comparison of Hutkі Grosh with card acquiring

The comparison shows that Hutkі Grosh confirms payments 2x faster in regions where cards are rarely used, and the commission is 30% lower.

Why might the callback not arrive?

First, check the callback_url accessibility from the external network. Also ensure the handler returns <result>OK</result> – otherwise, Hutkі Grosh will keep retrying for up to 24 hours. We include callback monitoring in our warranty service.

Estimated timelines

Cost is determined individually after analysis of your store. Order a turnkey integration – we will assess your project for free and offer the optimal solution. Get a consultation on integration – just contact us.

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.