Recurring Payments on 1C-Bitrix: Tokenization, Acquiring, Retry Logic

You launch a subscription service on 1C-Bitrix — and immediately hit the problem: how to charge a customer's card without their involvement? According to statistics, up to 30% of recurring charges are declined for various reasons: limit exceeded, bank technical failure, card blocked. We've faced this task dozens of times and developed a proven approach. The key nuance many miss: card data (number, CVV) is never stored on the store's server. The store only stores a token — an opaque identifier issued by the acquirer. We are certified Bitrix specialists with years of experience and have implemented recurring payments on 40+ projects. Order turnkey recurring payment setup — we'll integrate with any acquirer in 3–5 days.

Why Recurring Payments in 1C-Bitrix Require Tokenization?

Tokenization is a mechanism where the first payment triggers storage of payment data with the bank, and the store receives a unique identifier (RebillId, payment_method_id). This ID is bound to the card within the bank's system. The store never sees the card itself — it only stores a token, which completely eliminates PCI DSS requirements. As stated in Wikipedia, tokenization replaces sensitive data with their digital equivalents.

How Does Retry Logic Work?

Often a card may be declined for various reasons. We implemented cascading retry logic with increasing intervals to reduce revenue loss. On one project with 5000 subscribers, the retry logic recovered 20% of failed charges, significantly reducing annual costs. Additionally, introducing this logic increased successful charges by 20% and generated substantial additional revenue.

foreach (getFailedCharges() as $sub) {
    // Retry after 1, 3, 7 days
    $delays = [1, 3, 7];
    $delay  = $delays[$sub['retry_count']] ?? 7;

    if (daysSinceLastAttempt($sub) < $delay) continue;

    if ($sub['retry_count'] >= 3) {
        suspendSubscription($sub['id']);
        sendSuspendedEmail($sub['user_id']);
        continue;
    }

    $success = chargeRecurring($sub['customer_key'], $sub['amount'], generateOrderId());
    updateRetryCount($sub['id'], $success);
}

Why Tokenization Is Mandatory for Security?

Without tokenization, you would have to store card numbers and CVV codes on your own server. This requires PCI DSS certification, which costs tens of thousands of dollars plus annual audits. With tokenization, the store only deals with an opaque identifier that cannot be used outside the specific acquirer. Even if an attacker gains access to the database, they will only see a set of RebillIds, useless for charging other cards. We also encrypt tokens in the database and restrict table access via Bitrix\Main\ORM.

How We Set Up Recurring Payments

The implementation process is split into three stages, each with specific technical steps.

Step 1: Choose Acquirer and Tokenization

First, we connect an acquirer that supports tokenization. For Tinkoff, we initialize a payment with the flag Recurrent: 'Y', get the RebillId after a successful first charge. Store tokens in a separate table:

CREATE TABLE b_user_payment_tokens (
    id          SERIAL PRIMARY KEY,
    user_id     INT          NOT NULL,
    paysystem   VARCHAR(32)  NOT NULL,
    rebill_id   VARCHAR(128) NOT NULL,
    card_mask   VARCHAR(20),
    card_type   VARCHAR(10),
    created_at  TIMESTAMP    DEFAULT NOW(),
    is_active   BOOLEAN      DEFAULT TRUE
);

Alternatively, use Bitrix's HL-blocks (Highload-blocks) for token storage with convenient API access via HLBlockTable::getEntity.

Step 2: Implement Automatic Charging

Write the function chargeRecurring that initiates a new payment and immediately charges funds by token:

function chargeRecurring(string $customerKey, int $amountKopecks, string $newOrderId): bool
{
    $rebillId = getRebillId($customerKey, 'tinkoff');

    // Step 1: initialize a new payment
    $init = tinkoffPost('/v2/Init', [
        'TerminalKey' => TINKOFF_TERMINAL,
        'Amount'      => $amountKopecks,
        'OrderId'     => $newOrderId,
        'CustomerKey' => $customerKey,
        'Recurrent'   => 'Y',
        'Token'       => tinkoffSign([...], TINKOFF_SECRET),
    ]);

    // Step 2: charge by RebillId
    $charge = tinkoffPost('/v2/Charge', [
        'TerminalKey' => TINKOFF_TERMINAL,
        'PaymentId'   => $init['PaymentId'],
        'RebillId'    => $rebillId,
        'Token'       => tinkoffSign([...], TINKOFF_SECRET),
    ]);

    return $charge['Success'] ?? false;
}

Step 3: Set Up Notifications and Business Processes

Integrate retry logic with Bitrix agents and configure alerts via Bitrix24: on successful charge — notification, on failure — email asking to update the card. For complex scenarios, use Bizproc. More details on business processes can be found in the documentation on dev.1c-bitrix.ru.

Typical Integration Mistakes

• Storing tokens in session — tokens must be tied to a user and stored in the database, otherwise access is lost after session restart.
• Ignoring idempotency key — repeated requests can create duplicate payments. Use a unique OrderId for each charge.
• Incorrect handling of partial success — if the first stage succeeded but the second failed, you need to roll back or fix the transaction.

Timelines and What's Included

Full cycle with testing — up to 5 days. We provide API documentation, integration code, Bitrix24 business process setup, and a 6-month warranty. Get a consultation on recurring payment setup — we'll evaluate your project for free. Contact us, and we'll tell you how to get started.

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.