Payments are experiencing issues due to temporary restrictions in Russia. If your payment does not go through, please submit a support request.Our support team is available 24/7 — we are always here to help with hosting and server issues.We are now accepting requests for dedicated server rental and colocation services in our data center.Reminder: we recommend enabling backups for additional data protection.A new VPS/VDS lineup with NVMe storage and improved performance is now available.Maintenance work on some servers has been completed. All services are operating normally.

MODULE FOR 1C-BITRIX

Pavel Shulaev

T-Bank Internet Acquiring Payment Processing

The module integrates T-Bank (formerly Tinkoff Bank) e-commerce acquiring with 1C-Bitrix of any edition, from 'First Site' to 'Enterprise'. It automatically creates the payment system, supports migration from the official module, maintains an operations log, and sends error notifications via the rover.notifier module.

5.00/5 · 6 ratings

1C-Bitrix Marketplace: 5/5 · 6 ratings

Technical details

Published
12 April 2017
Updated
22 September 2026
Version
2.9.0
Installed
500–999 times
Responsive design
Yes
Composite support
Yes
Compatible with Sites24
Yes
Developer
Pavel Shulaev

What this solution does

The module integrates T-Bank (formerly Tinkoff Bank) e-commerce acquiring with 1C-Bitrix of any edition, from 'First Site' to 'Enterprise'. It automatically creates the payment system, supports migration from the official module, maintains an operations log, and sends error notifications via the rover.notifier module.

The solution addresses standard integration tasks, including correct VAT calculation in receipts and protection against duplicate bank notifications. Development has been ongoing since 2017, with regular updates aligned with security requirements, bank standards, and Federal Law 54-FZ. The code is written directly by the author, ensuring deep architectural understanding and the ability to resolve non-standard scenarios and API-related questions directly.

Supported payment methods:

- Bank cards (Mir, Visa, MasterCard)

- SBP (QR code payment, including in the popup widget)

- T-Pay, SberPay, Yandex Pay, MIR Pay

- Payment in the popup widget without redirecting to the bank's website

The module provides automatic redirection to the payment page immediately after order placement. It supports full and partial refunds with automatic order status updates, as well as partial payments.

Receipts and 54-FZ compliance

The module enables receipt generation via T-Bank in full compliance with 54-FZ regulations. All VAT rates are supported, including current calculated rates of 20/120 and 22/122. It works with all tax systems: OSN, USN, ENVD, ESCHN, and patent taxation. A complete reference of calculation items and payment methods according to FFD version 1.2 is included, allowing accurate reporting of marked goods, contributions, and agency payments. Closing receipts are generated upon shipment, payment, or when the order transitions to a specified status.

Two-stage and recurring payments

Fund holding is implemented: payment confirmation can be done in one click directly from the order card in the admin panel or automatically after a specified timeout (in days). The order is marked as paid only after bank confirmation. If the charge fails, the operator sees the reason and can retry, avoiding the situation where an order is marked as paid without funds received. After holding funds, the buyer sees a clear message stating that money is reserved on the card and will be charged once the store confirms the order, rather than an error message indicating payment failure.

The module provides automatic confirmation of reserved payments after a specified timeout in days. For multisite installations, saved card binding can be configured individually for each site or globally.

Automation and flexibility features

Order statuses can be customized for specific events: payment, partial payment, hold, refund, and cancellation.

A "Send payment link" button is available in the order card. If payment has not been completed or ended with a fixable error, the system sends the buyer a new payment link via email with a single click. The email template is freely editable in the admin panel. If the template is missing, disabled, or not linked to the order site, the module reports this immediately rather than after a failed send attempt.

Flexible templates for order links in the customer personal cabinet are supported. Components are provided to embed the payment form in the order card, personal cabinet, CRM forms, and the Sites24 block.

Upon installation, the module automatically creates the payment system and opens its settings. The user only needs to enter the terminal ID and password.

The module enables a seamless transition from the official T-Bank solution: if tinkoff.payment is already installed, terminal parameters, password, and receipt settings are automatically migrated to the new payment system, after which the old module is disabled. Ready-made icons are provided for each payment method, including cards, SBP, T-Pay, and pop-up widgets. The component operates independently of the 'Online Store' module, featuring its own logging and notification settings.

The failure notification system alerts administrators to critical events that would otherwise remain unnoticed in logs: payment amount mismatches with bank confirmation, rejected bank notifications, failure to send a closing receipt, issues with fund reservation, refunds issued without order cancellation, or error messages displayed instead of the payment form. Two independent notification modes are implemented: critical failures are sent immediately, while user errors are grouped to prevent the mailbox from being flooded with identical messages during bank-side outages.

The module uses the free 'Error Notifications' component (rover.notifier, requires PHP 8.2) to send alerts via email, SMS, or messengers (Telegram, WhatsApp, MAX). Without this component, the core functionality operates normally, but notifications are not sent.

The order card includes a 'T-Bank Operations' tab. It displays the payment status in the bank and the receipt date, the order status set by the module, the bank-confirmed amount, whether a closing receipt was sent, and the terminal number used for the transaction.

A detailed operation log is maintained for each order. It records the receipt and processing of bank notifications, responses to status queries, order status changes, hold confirmations, and receipt dispatches. The initiator of each action is also recorded: the bank, an operator, or a background agent.

Rejected bank notifications are displayed with the specific reason for rejection, clarifying why a payment failed.

The operation log is maintained continuously, regardless of general logging settings. Storage depth is configurable, and old records are automatically deleted. The log does not contain customer personal data or receipt composition details.

Reliability and Security

Protection against duplicate closing receipts is provided when the bank sends repeated notifications.

The module enables secure payment processing via T-Bank by restricting incoming notifications to a whitelist of the bank's IP addresses. Logs are automatically rotated and cleaned, with the log directory protected from direct access. Payment status is stored in a dedicated module table rather than site settings, preventing full data retrieval on every request and ensuring stable performance even with tens of thousands of transactions. Background automatic confirmation of reserved payments continues despite errors in individual orders, ensuring that one failure does not leave other orders unconfirmed. A separate 'Debug' tab in the module settings provides logging and notifications without interfering with main settings, and is available in all editions, including those without the 'Online Store' module.

Compatibility

The module is compatible with all 1C-Bitrix editions, including 'First Site' and 'Start'. It supports Composite mode. Adaptive payment templates are provided, including a dedicated template for Sites24. The system supports balance top-ups on internal accounts. Multicurrency support is implemented, along with correct handling of alphanumeric order numbers. Internal events are available for fine-tuning the module to specific needs.

Complete documentation for installation and configuration is available. Free consultation is provided before and after purchase, assisting with connection, setup, and test payments. Technical support is handled directly by the module developer rather than an automated script or a general support line. In non-standard cases, responses are clarified directly with the author, bypassing standard ticket queues.

Search keywords: Tinkoff, T-Bank, t-bank, tbank.

When needed, General iT can implement “T-Bank Internet Acquiring Payment Processing”, configure the module and verify it against the current website setup.

UPDATE HISTORY

What’s new

68 releases
2.9.0 (22.09.2026)Latest update

The payment system is created during installation. The module creates it automatically and immediately offers to proceed to its settings—you only need to enter the terminal ID and password. It is created in a disabled state so that the buyer cannot see it before it is configured.

Settings can be migrated from the tinkoff.payment module. If it is installed on the site, during installation you are offered to create a payment system based on its settings: the terminal ID, password, and invoice parameters are transferred automatically, and the previous payment system is disabled. Restrictions are transferred via a separate checkbox.

Custom icons for each payment method—card, SBP, T-Pay, and pop-up widgets—are now provided, so you no longer need to manually select images.

The invoice now includes calculation method indicators: 'partial payment and credit', 'transfer to credit', and 'credit payment'.

2.8.0 (05.09.2026)

The "T-Bank Operations" tab in the order card. For each payment, the bank status, the assigned order status, the confirmed amount, and the sending of the closing receipt are visible. Nearby is the operations log: which notifications were received from the bank and whether they were accepted, what the module did, and who initiated it — the bank, the operator, or the agent. Previously, this could only be determined from the log if it was enabled in advance. The log is maintained independently of system logging, and the storage depth is configurable.

Rejected bank notifications are visible along with the rejection reason — these explain why the payment "did not arrive."

Two-stage payments no longer appear unsuccessful to the buyer. After reserving funds, the order is not marked as paid, and the result page previously displayed this as an error. Now the buyer sees that the funds are reserved and will be debited after the order is confirmed by the store.

Sending the payment link checks the email template. If it is missing, disabled, or not linked to the order's website, the module reports this immediately instead of showing a failed send.

Payment status has been moved to the module's own table. Previously, it was stored as rows in the site settings and read entirely on every access to the module. During updates, the data is automatically migrated.

After installation, a "Go to Module Settings" button is added.

2.7.2 (28.08.2026)

An intermediate status has been added to the successful payment redirect page: Payment accepted by the bank; the status will be updated within a few minutes.

The hold confirmation has been redesigned: an order can no longer appear as paid if the bank failed to debit funds due to an error. If the bank rejects the payment, the button in the order card displays the actual reason, remains in place, and the attempt can be retried immediately.

Fixed: reserved funds are no longer lost due to connection interruptions. A single connection failure no longer removes the payment from processing; the next attempt will resume it.

Discovered vulnerabilities have been patched.

2.7.1 (28.08.2026)

Security. Payment status verification has been moved from a custom public endpoint to the standard Bitrix service.

Fixed: an order that was not cancelled no longer appears as cancelled. If something blocked the order cancellation after a refund or hold release, this was previously silently ignored and logged as success. Now the administrator receives a notification.

Fixed: the payment form layout in the Aspro theme — when automatic redirection to the bank is disabled, an unclosed tag broke the page markup.

The onBeforeActionReverse event has been enhanced — the store handler can now override the result of hold release processing, as was already possible for payment, refund, rejection, and authorization.

Refactoring: obsolete and unnecessary module files have been removed

2.7.0 (26.08.2026)

Failure notifications. The module informs the administrator about issues that were previously visible only in the log: payment amount mismatch, bank notification rejected, closing receipt not sent, hold not released, buyer saw an error instead of the payment form. Delivery is handled by the free "Error Notifications" module (rover.notifier) — via email, SMS, or messenger. Two independent checkboxes on the "Debug" tab: critical failures are sent immediately, buyer errors are grouped.

The hold auto-confirmation agent no longer stops at the first error — previously, a failure on one payment left all others unconfirmed.

Settings now work in editions without "Online Store": the "Debug" tab with logging and notifications is available there as well.

Payment information processing security has been enhanced.

Discovered vulnerabilities have been fixed

USER EXPERIENCE

Solution reviews

How does this solution work in a real project? Share your experience and help others choose.

Be the first to share your experience

There are no reviews of this solution on git.ru yet. Tell us what worked well and what could be improved.

Verified purchaseAdd a key if you wish. A verified review gets a badge, priority placement and more rating weight.

Open to every clientJust sign in to your account. A key is optional; all reviews are moderated.

YOUR EXPERIENCE MATTERS

Your review

YOUR PROJECT INFRASTRUCTURE

A home for your website

BEFORE YOU ORDER

Let’s go through the details.

What does the price cover?
The displayed price covers the solution itself. Platform licensing, installation and customisation are checked separately. If the page offers bundles, select the required option before submitting a request.
How do I check compatibility?
Compare the supported editions and solution version in the technical details with your project. Before installing on a live website, we recommend making a backup and checking the solution in a test environment.
Is there a trial?
The developer lists a trial of 5 days. The trial button opens the installer in your website control panel. Check the required features and compatibility before purchasing.
How much does this solution’s renewal cost?
The current renewal price is 4,450 ₽. Before you order, a manager will confirm the renewal period and whether it applies to your licence.
Can you help with implementation?
We can help install the module, check its settings and verify how it works in your project. Compatibility with other customisations and the scope of work are assessed before we begin.

GENERAL iT

Let’s discuss your project

Получатель: ООО «Дженерал Ай Ти Рус»

1C-BITRIX

Install solution

Enter a domain with or without https://. The installer will open in your website control panel in a new tab.

Solution screenshots

Solution screenshot