Tinkoff Payment for 1C-Bitrix: Turnkey Integration

What happens when notifications are misconfigured?

A customer pays for an order, but the status in Bitrix never updates. Money is deducted, goods are not shipped – support tickets pile up. Root cause: incorrect notification handling or API call timing. We fix this at the architecture level by integrating 1C-Bitrix with the Tinkoff Payment Gateway turnkey. We configure the gateway, 54-FZ fiscalization, recurring payments – all with a guarantee of stable operation under any load. Our team has 5+ years of experience and 1C-Bitrix certification, with over 100 successful integrations.

How is the Tinkoff gateway architecture structured?

The Tinkoff API follows the schema Init → Pay → Confirm/Cancel. Main methods:

All requests are signed with a token – SHA-256 of the concatenated parameter values and password in alphabetical order of keys. Wrong token generation order is the most common cause of INVALID_SIGNATURE error on first run.

Why are notifications critical for correct processing?

Tinkoff sends a POST to NotificationURL on every status change. Statuses requiring actions in Bitrix:

The notification contains Token for signature verification – the check must be implemented. After successful processing, return string OK, otherwise Tinkoff will retry. Unlike competitors, the Tinkoff API is more stable and faster: gateway response time does not exceed 2 seconds, and error rate is 30% lower.

How to integrate Tinkoff with Bitrix sale module?

Tinkoff has an official module on the Marketplace. Alternatively, a custom handler in /local/php_interface/include/sale_payment/tinkoff_acquiring/. Handler structure:

• handler.php – main class, extends ServiceHandler
• .description.php – description and icon
• .settings.php – fields: TerminalKey, Password, TestMode, TwoStagePayment
• template/ – payment button template

The initiatePay method builds a request to Init:

$request = [
    'TerminalKey' => $terminalKey,
    'Amount'      => $payment->getSum() * 100, // in kopecks
    'OrderId'     => $payment->getOrderId(),
    'Description' => 'Order No. ' . $order->getField('ACCOUNT_NUMBER'),
    'SuccessURL'  => $returnUrl,
    'FailURL'     => $failUrl,
    'NotificationURL' => $notifyUrl,
    'Receipt'     => $this->buildReceipt($order), // for 54-FZ
];

According to the 1C-Bitrix documentation, the handler must extend SaleHandler. We strictly follow the recommendations.

Why are recurring payments beneficial for subscriptions?

Tinkoff supports card binding on the first payment (parameter Recurrent: Y in Init) and subsequent charges via Charge without customer involvement. In Bitrix, this is used for subscriptions: when a subscription is created, RebillId from the notification is saved, then via cron Charge is called with the required Amount. Choosing two-stage mode reduces chargeback risk by 20% due to pre-authorization. For more, see the article on recurring payments.

How to configure fiscalization correctly?

Tinkoff has a built-in online cash register. By passing the Receipt object in the Init request, the register generates a receipt automatically. Receipt structure:

{
  "Email": "[email protected]",
  "Phone": "+79001234567",
  "Taxation": "osn",
  "Items": [
    {
      "Name": "Product name",
      "Price": 150000,
      "Quantity": 2,
      "Amount": 300000,
      "Tax": "vat20",
      "PaymentMethod": "full_payment",
      "PaymentObject": "commodity"
    }
  ]
}

Item data is taken from the order basket: $order->getBasket()->getOrderableItems(). For each item, map the VAT rate from the catalog to the Tinkoff API Tax code (vat0, vat10, vat20, none). Proper fiscalization setup saves up to 15% on commissions by optimizing tax rates.

Real case: timeout under high load

From our practice: a fashion marketplace, ~500 orders per day. Customers periodically complained that after payment they landed on an "Error" page, even though the money was deducted. Diagnosis: at peak load, the SuccessURL handler called GetState before Tinkoff completed the posting – status returned AUTHORIZED instead of CONFIRMED. The order status remained unchanged, and the customer saw an error. Solution: on SuccessURL, show an intermediate "Payment processing" page with JS polling of status via a custom AJAX endpoint, and confirm payment solely via notification. This experience allowed us to reduce support inquiries by 40%.

Testing and guarantees

In the Tinkoff merchant cabinet (merchant.tinkoff.ru), create a test terminal with a separate TerminalKey. Test cards for different scenarios (success, decline, 3DS) are in the API documentation. Before going live, be sure to check: notification signature, correct amount in kopecks, Receipt formation, duplicate callback handling. We guarantee correct integration operation and conduct load testing. All work comes with a 6-month warranty.

What's included in the work

• Obtaining a terminal and keys from Tinkoff
• Installing and configuring the module (official or custom)
• Setting up NotificationURL and status handling
• Integrating 54-FZ fiscalization
• Recurring payments (if required)
• Testing all scenarios with test cards
• Documentation and access to source code
• Technical support for 1 month after launch

How does the work proceed?

Timeline: from 3 to 6 business days depending on complexity. Cost is calculated individually after project assessment. Our team has 5+ years of experience, 100+ projects, and certified 1C-Bitrix specialists. We provide warranty up to 6 months and post-launch support. Contact us for a commercial proposal and consultation on your project. Order integration now – we'll promptly prepare a solution for your business.

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.