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

Tinkoff is more convenient than Sberbank for recurring payments: it does not require storing a clientId, but uses a simple RebillId. This cuts integration time in half.

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.