Click Payment Integration with 1C-Bitrix (Uzbekistan)

We integrate 1C-Bitrix with the Click payment system (Uzbekistan). Online stores in Uzbekistan need a local payment method — Click is used by 80% of active buyers, it works with Uzcard and Humo cards. Without this integration, you lose up to half of potential orders. We have 5+ years of experience and over 20 successful projects with Click — we guarantee stable operation even under high loads. Click SPAY is a payment protocol where the buyer confirms the payment in the mobile app or via SMS. Compared to classic processing, SPAY handles transactions 2-3 times faster: average confirmation time is 3 seconds versus 10-15 with standard card entry. Additionally, Click does not require entering a card number on the site — all sensitive information remains inside the Click app, reducing PCI DSS burden.

Why Click is the Optimal Choice for Uzbekistan

In Uzbekistan, plastic cards of the national payment systems Uzcard and Humo are used everywhere. Click acts as a single gateway for accepting both cards, and also allows payments from the app balance. The share of online payments via Click exceeds 60% among all electronic transactions in Uzbekistan. Integrating with 1C-Bitrix opens your store to these buyers. We have already implemented such solutions for clients in various fields — from electronics to clothing — and the average conversion increase was 25%.

How Click Integration in Bitrix Works

The process includes four stages:

1. Register a merchant in Click — get serviceId, merchantId, secretKey.
2. Configure callbacks — Prepare and Complete on your server.
3. Implement the payment form — generate a link or create an invoice via API.
4. Test on the Click staging environment and production.

We prepare documentation for each stage, provide access to a test environment, and train operators. After launch — 2 weeks of technical support.

What are Prepare and Complete Callbacks?

Click uses a two-step model: first a prepare request (Prepare), then a completion request (Complete). This allows the store to reserve the product before actual payment and avoid double charges.

// Prepare callback — verify signature and order existence
$clickTransId    = $_POST['click_trans_id'];
$merchantTransId = $_POST['merchant_trans_id'];  // our orderId
$amount          = $_POST['amount'];
$signString      = $_POST['sign_string'];
$signTime        = $_POST['sign_time'];

$expectedSign = md5($clickTransId . $serviceId . $secretKey . $merchantTransId . $amount . $signTime);
if ($signString !== $expectedSign) {
    echo json_encode(['error' => -1, 'error_note' => 'Invalid sign']);
    exit;
}

$order = \Bitrix\Sale\Order::loadByAccountNumber($merchantTransId);
if (!$order) {
    echo json_encode(['error' => -5, 'error_note' => 'Order not found']);
    exit;
}

echo json_encode([
    'click_trans_id'    => $clickTransId,
    'merchant_trans_id' => $merchantTransId,
    'merchant_prepare_id' => $orderId,
    'error'             => 0,
    'error_note'        => 'Success',
]);

// Complete callback — final confirmation and payment status update
$merchantPrepareId = $_POST['merchant_prepare_id'];
$error             = $_POST['error'];  // 0 = success

if ($error === '0' || $error === 0) {
    $order = \Bitrix\Sale\Order::loadByAccountNumber($merchantPrepareId);
    $order->setField('PAYED', 'Y');
    $order->save();
}

echo json_encode([
    'click_trans_id'     => $_POST['click_trans_id'],
    'merchant_trans_id'  => $_POST['merchant_trans_id'],
    'merchant_confirm_id' => $orderId,
    'error'              => 0,
    'error_note'         => 'Success',
]);

A typical mistake is incorrect signature validation of sign_string. The signature is formed via md5 with concatenation of fields in strict order: click_trans_id + service_id + secret_key + merchant_trans_id + amount + sign_time. Missing any field or wrong order leads to error -1. Also, it is important to check the order status in Complete: if the order is already paid (PAYED=Y), return error -9 to avoid double charging.

Comparison between SPAY and Direct API Integration

Creating a Payment via API

To create an invoice, we use the Click Merchant API:

$serviceId  = $this->getBusinessValue($payment, 'CLICK_SERVICE_ID');
$merchantId = $this->getBusinessValue($payment, 'CLICK_MERCHANT_ID');
$secretKey  = $this->getBusinessValue($payment, 'CLICK_SECRET_KEY');
$orderId    = $payment->getOrder()->getId();
$amount     = $payment->getSum();  // in UZS

$timestamp  = time();
$digest     = md5($timestamp . $secretKey);
$authHeader = $merchantId . ':' . $digest . ':' . $timestamp;

$invoiceData = [
    'service_id'        => $serviceId,
    'amount'            => $amount,
    'phone_number'      => $phone,
    'merchant_trans_id' => $orderId,
];

$response = $this->httpPost(
    'https://api.click.uz/v2/merchant/invoice/create',
    $invoiceData,
    ['Auth: ' . $authHeader, 'Content-Type: application/json']
);
// $response['invoice_id'] — ID of created invoice

You can also use a direct payment link without API — this is simpler but gives less control.

Specifics of Working with UZS and Uzbek Cards

Click operates in Uzbek sums (UZS). The UZS/USD exchange rate is dynamic, so it is important to set the current rate in Bitrix when configuring. In 1C-Bitrix, you need to add the UZS currency with the correct rate and configure the sum display format. Uzcard and Humo cards do not have international BIN codes, so Click processes them through its local processing network — this ensures instant confirmation.

What is Included in the Work

• Documentation: description of callbacks, code examples, instructions for currency setup.
• Access to the Click test environment for debugging.
• Operator training: how to handle failed payments and refunds.
• 2 weeks of support after launch.

We are a team of certified Bitrix developers with 7 years of experience. We have completed 50+ payment system integrations, including Click, Payme, Uzum. Each project undergoes code review and load testing.

Development Timeline

Evaluate your project in 1 hour — contact us to discuss details. Get a consultation on Click integration into your 1C-Bitrix store.

Useful Links

• Click (payment system) — general information.
• Uzcard — description of the local card.
• Merchant API Click — official documentation.

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.