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 $9k–13k 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 $450–650 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.