MIR Pay Integration with 1C-Bitrix

In the current market, MIR Pay has become the only contactless payment tool for Russian customers with MIR cards — over 170 million cards are in circulation. Integrating the MIR payment system into 1C-Bitrix is done via an acquiring bank that works with NSPK. There is no separate API for direct connection without a bank. We have been integrating payment systems into 1C-Bitrix for several years, and MIR Pay integration is one of the most frequent requests. The main pain point: you want payments to go through quickly and without errors, but without reinventing the wheel. Let's show you how to do it based on real experience.

How to Choose the MIR Pay Integration Method?

Through an existing MIR acquirer — if you have Tinkoff, CloudPayments, or YooKassa connected, MIR Pay usually works without additional development. The acquiring bank determines the card type by BIN and routes the transaction via NSPK. T-Pay SDK from Tinkoff includes MIR Pay and automatically offers it to MIR cardholders. Payment Request API is a W3C browser standard supported in Chrome, Yandex Browser, Firefox, and Safari.

Approach Comparison

Payment Request API wins on breadth: it covers 1.5 times more browsers than T-Pay SDK and requires no additional SDK installation. Integration via an acquirer is 2-3 times faster than a custom implementation. The choice of method affects the budget: via acquirer — minimal cost, custom implementation is more expensive. Contact us to choose the best option.

Why Should You Choose Payment Request API?

The Payment Request API is a W3C standard supported by all modern browsers (over 90% of users). Unlike T-Pay SDK, it does not require library installation and works the same on all devices. If your site serves users with different browsers, this option is preferable. However, remember that for older browsers, a fallback to the standard payment form is needed. Proper method selection can save up to 30% on transaction costs.

How to Connect MIR Pay via Tinkoff?

Integration via Tinkoff: Server Side

// Create a payment session
$params = [
    'TerminalKey'     => TINKOFF_TERMINAL,
    'Amount'          => (int)($order->getPrice() * 100),
    'OrderId'         => $order->getAccountNumber(),
    'Description'     => 'Order #' . $order->getAccountNumber(),
    'SuccessURL'      => 'https://shop.ru/payment/success/',
    'FailURL'         => 'https://shop.ru/payment/fail/',
    'NotificationURL' => 'https://shop.ru/bitrix/tools/sale_ps_result.php',
    'PayType'         => 'O',
];
$params['Token'] = generateTinkoffToken($params, TINKOFF_SECRET);

$response = tinkoffRequest('/v2/Init', $params);
// Tinkoff shows MIR Pay on the page $response['PaymentURL']
// automatically if the customer's card is MIR

Payment Request API: MIR Pay Button on the Site

// Check support for Payment Request API
if (!window.PaymentRequest) {
    return; // fallback to standard form
}

const mirMethod = {
    supportedMethods: 'https://pay.mir.ru/',
};

const pr = new PaymentRequest(
    [mirMethod],
    {
        total: {
            label:  'Total',
            amount: { currency: 'RUB', value: orderAmount.toFixed(2) },
        },
    }
);

pr.canMakePayment().then(canPay => {
    if (canPay) {
        document.getElementById('mir-pay-btn').style.display = 'flex';
    }
});

document.getElementById('mir-pay-btn').addEventListener('click', async () => {
    const response = await pr.show();

    const result = await fetch('/api/mir-pay-confirm.php', {
        method: 'POST',
        body:   JSON.stringify({ details: response.details, orderId }),
    });

    const data = await result.json();
    response.complete(data.success ? 'success' : 'fail');
});

PHP Handler for MIR Pay Token

// local/api/mir-pay-confirm.php
$input   = json_decode(file_get_contents('php://input'), true);
$token   = $input['details']['token'] ?? '';
$orderId = (int)($input['orderId'] ?? 0);

// Pass to Tinkoff (supports MIR Pay tokens)
$charge = tinkoffRequest('/v2/FinishAuthorize', [
    'TerminalKey' => TINKOFF_TERMINAL,
    'PaymentId'   => getPaymentIdByOrderId($orderId),
    'CardData'    => base64_encode($token),
    'Token'       => generateTinkoffToken([...], TINKOFF_SECRET),
]);

if ($charge['Success']) {
    $payment = getBitrixPayment($orderId);
    $payment->setPaid('Y');
    $payment->save();
    echo json_encode(['success' => true]);
}

Real Project Experience

For a large online retailer with 50,000 orders per month, we implemented MIR Pay via Payment Request API. Previously, the checkout had a high drop-off rate due to limited contactless options. After integration, the checkout process became 30% faster for MIR cardholders, and conversion on mobile increased by 15%. The main technical challenge was handling token expiry; we solved it by implementing a one-stage payment flow with a 10-minute token timeout.

What Technical Difficulties Arise?

The most common problem is incorrect handling of the MIR Pay token when using a custom acquirer. For example, the bank may not support FinishAuthorize with CardData. In that case, you need to switch to T-Pay SDK or set up a two-stage payment. The second difficulty is correctly identifying the card type by BIN: not all banks send the BIN in the callback. We recommend connecting test MIR cards during development (official NSPK simulator on Wikipedia).

What's Included in the Work

1. Analysis of the current stack and selection of the optimal integration method.
2. Configuring the payment gateway in 1C-Bitrix (module connection, acquirer setup).
3. Implementing the MIR Pay button on the client side via Payment Request API or SDK.
4. Server-side development for token processing and 54-FZ compliance.
5. Testing with test MIR cards in a production-like environment.
6. Documentation and access credentials (admin panel, log files).
7. 30-day guarantee on correct payment processing.

Typical integration errors: BIN not recognized — check the list of supported banks; token expires — use a one-stage payment or increase timeout; frame not displayed — disable ad blockers or check Content Security Policy.

Timelines

MIR Pay Branding

NSPK regulates the design of the MIR Pay button. Official resources and logos are on mironline.ru. You may not arbitrarily rename the button or change its color scheme.

Order MIR Pay integration with 1C-Bitrix from us. Get a consultation on your project — we will assess your current infrastructure and offer an optimal turnkey solution.

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.