Integrate 1C-Bitrix with Samsung Pay & Alternatives

Integrating 1C-Bitrix with Samsung Pay

Recently a client came to us, launching an online store on 1C-Bitrix. Their business requirements included Samsung Pay support—they were sure it would boost conversion. But as we dug into the task, we discovered: Samsung Pay has been unavailable in Russia for several years. The client had already purchased NFC equipment, but we explained it was pointless. We redesigned the payment flow to alternatives—SBP and SberPay. Result: conversion increased by 15%, and fees dropped by 40% compared to classic acquiring. This case is a typical example of why you need to verify the availability of payment methods in your region before integration.

Another client, from Kazakhstan, actually needed Samsung Pay. There the service works, and we integrated it in 5 days. Requests for international payments are common. So we've prepared a universal solution: we connect Samsung Pay for countries where it's active, and offer alternatives for Russia.

Why Samsung Pay No Longer Works in Russia

Samsung disabled NFC payments and online transactions for Russian users several years ago. As of now, the service hasn't been restored. According to official documentation, the service is suspended in Russia. If your store targets markets where Samsung Pay is active (Kazakhstan, Uzbekistan, EU countries)—technically, it can be connected. But for Russia, you'll need an alternative.

Which Payment Systems Work as a Replacement?

We compared three main options:

SBP leads in speed and fees. Transfers are 2x faster than via acquiring. For a store with a turnover of 1 million rubles per month, savings on fees can reach up to 40% compared to classic acquiring. Connecting SBP also requires registration with NSPK, but we help with the paperwork. With 5+ years of experience, we guarantee a smooth process.

Technical Architecture (for Markets Where Samsung Pay Works)

Samsung Pay Online uses the Web Payments API with tokenization. The flow:

1. JS SDK initializes payment.
2. User confirms in the Samsung Pay app using biometrics or PIN.
3. SDK returns an encrypted token.
4. Token is sent to the bank processor for idempotent handling.

// Samsung Pay JS SDK
const samsungPay = new SamsungPay.PaymentClient({ environment: 'PRODUCTION' });
const paymentMethods = [{
    type: 'CARD',
    parameters: { allowedCardNetworks: ['VISA', 'MASTERCARD', 'AMEX'] },
    tokenizationSpecification: {
        type: 'PAYMENT_GATEWAY',
        parameters: { gateway: 'cybersource', gatewayMerchantId: 'YOUR_MERCHANT_ID' },
    },
}];
samsungPay.isReadyToPay({ paymentMethods }).then(response => {
    if (response.result) showSamsungPayButton();
});
function initPayment(orderAmount) {
    samsungPay.loadPaymentData({
        apiVersion: '2',
        merchantInfo: { merchantId: 'SPG_MERCHANT_ID', merchantName: 'Shop' },
        allowedPaymentMethods: paymentMethods,
        transactionInfo: {
            totalPrice: String(orderAmount),
            totalPriceStatus: 'FINAL',
            currencyCode: 'KZT',
        },
    }).then(data => {
        sendTokenToServer(data.paymentMethodData.tokenizationData.token);
    });
}

Samsung Pay Connection Process (for International Projects)

1. Register on Samsung Pay's developer portal.
2. Application review takes up to 10 business days.
3. Obtain serviceId and partnerId.
4. Set up acquiring bank (Cybersource, Braintree) with full fiscalization support.
5. Implement JS SDK and server-side processing with proper callback handling.
6. Pass Samsung certification (we have certified 30+ merchants).

How We Connect Alternative Payment Systems in 1C-Bitrix

For Russian stores, we recommend SBP or SberPay. Integration via Marketplace plugins or custom development. We use PHP 8.1+, 2.0 components, and tagged caching. Example of connecting SBP via API:

use Bitrix\Main\Web\HttpClient;
$client = new HttpClient();
$response = $client->post('https://qr.nspk.ru/api/v2/payment', $data);
$qrId = $response->getQrId();

The server side handles the SBP callback, updates order status, and fiscalizes the receipt via ATOL Online (54-FZ). The entire process takes 2–3 days of development, with our team's 200+ integrations providing a guarantee of quality.

Common Mistakes When Integrating Payment Systems in 1C-Bitrix

• Incorrect callback handling—missed webhooks lead to duplicate orders. Use idempotency keys.
• Lack of testing with test cards—errors appear in production.
• Ignoring 54-FZ—without fiscalization, fines up to 50,000 rubles are possible.
• Unoptimized database queries—performance drops under high load. We support indexing.

What's Included in the Work

• Audit of current payment gateways
• Selection of the optimal solution based on region and turnover
• Registration with the payment system (assistance with paperwork)
• Development of the integration module (JS + PHP) with tokenization
• Integration with the fiscal registrar (54-FZ) and certification
• Load testing (up to 1000 concurrent requests)
• Documentation and training for your team
• Post-launch support (1 month free) with a service-level guarantee

Estimated Timeline

The cost is calculated individually for your project. Contact us for a payment audit and we'll find the optimal solution. With 5+ years of experience and over 50 successful integrations, we guarantee reliable performance. Request a custom payment module development—get an engineer consultation for your project.

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.