Setting Up Fund Holding on 1C-Bitrix: Two-Stage Payment

Setting Up Fund Holding on 1C-Bitrix

The buyer paid for the order — money debited, but the item is out of stock. Refunds take 3 to 10 business days, and each such case undermines trust. Holding (two-stage payment) solves this: the bank reserves the amount on the buyer's card, and actual debit occurs only after confirming availability. This is standard for high-volume online stores with large catalogs. Our experience: over 10 years in Bitrix development and 50+ projects with holding.

What problems does holding solve?

The most common mistake is selling out-of-stock items. If money already went to the store account, refund takes 3–10 business days. Hold allows instant cancellation without fees — the bank just removes the block. Additionally, two-stage payment halves return rates compared to one-stage (based on our project statistics).

Another issue is incorrect payment status mapping. In Bitrix, the Y (paid) status should be assigned only after hold confirmation. If set immediately, cancellation causes accounting confusion. We configure the status model so that PAID changes only after capture, with a custom 'held' status before.

How does two-stage payment work in practice?

Stage 1 — hold (authorization): the store sends a request to the payment system to reserve the amount. Money is not debited but blocked on the card. The acquiring bank returns a pre_auth_code or similar authorization ID.

Stage 2 — confirmation (capture): the store confirms debit when the item is ready for shipment. Money transfers to the store account. Or cancellation (void/cancel): if out of stock, the reserve is released without fees.

Bitrix implements this via the sale module, class \Bitrix\Sale\PaySystem\Manager and specific payment system handlers. For more on the mechanism, see Wikipedia.

Comparison of payment systems with hold support in Bitrix

If your acquirer is not listed, customization is needed. We integrated holding with 15+ payment gateways — from CDEK to foreign aggregators.

How to configure holding in Bitrix?

1. Select a payment system in "Store" → "Payment". Ensure it supports holding.
2. Enable two-stage mode: in the system settings find the "Two-stage payment" or "Holding mode" parameter and set to "Yes".
3. Set up order statuses: create a "Awaiting confirmation" status (or use existing C) where hold is active. The "Confirmed" status will trigger capture.
4. Check database configuration. Parameters are stored in tables b_sale_pay_system and b_sale_pay_system_params. For example, to find the payment system ID by name:

SELECT ID, NAME, HANDLER_TYPE FROM b_sale_pay_system WHERE ACTIVE = 'Y';

Example: automatic hold confirmation on status change

The OnSaleStatusOrderChange event allows automatic capture on transition to a confirmation status:

// /bitrix/php_interface/init.php
use Bitrix\Main\EventManager;

EventManager::getInstance()->addEventHandler(
    'sale',
    'OnSaleStatusOrderChange',
    function(\Bitrix\Main\Event $event) {
        $order = $event->getParameter('ENTITY');
        $value = $event->getParameter('VALUE');

        // Status "confirmed" (e.g. 'C') — confirm the hold
        if ($value === 'C') {
            $paymentCollection = $order->getPaymentCollection();
            foreach ($paymentCollection as $payment) {
                if (!$payment->isPaid()) {
                    \Bitrix\Sale\PaySystem\Manager::confirm($payment);
                }
            }
        }

        // Status "cancelled" (e.g. 'F') — release the hold
        if ($value === 'F') {
            $paymentCollection = $order->getPaymentCollection();
            foreach ($paymentCollection as $payment) {
                \Bitrix\Sale\PaySystem\Manager::cancel($payment);
            }
        }
    }
);

An agent for monitoring expired holds:

// Agent: ProccessExpiredHolds()
function ProccessExpiredHolds() {
    $cutoffDate = new \Bitrix\Main\Type\DateTime();
    $cutoffDate->add('-5D');

    $res = \Bitrix\Sale\Internals\PaymentTable::getList([
        'filter' => [
            'PAID' => 'N',
            '<DATE_BILL' => $cutoffDate,
            '!SUM' => 0
        ],
        'select' => ['ID', 'ORDER_ID']
    ]);

    while ($row = $res->fetch()) {
        \CEvent::Send('HOLD_EXPIRING', 's1', [
            'ORDER_ID' => $row['ORDER_ID']
        ]);
    }

    return 'ProccessExpiredHolds();';
}

We use this solution in all projects. It reduces manager workload and eliminates money loss. Average hold time is 5 days, with 80% of holds confirmed within 48 hours. Savings on fees from cancelling unfulfilled orders reach 2%.

What's included in turnkey holding setup

• Audit of current payment systems and status model.
• Configuration of the sale module for two-stage payment.
• Development of handlers for non-standard acquirers.
• Integration with business processes (Bizproc) and Bitrix24 robots.
• Writing and configuring an agent for expired holds.
• Testing on live environment and documentation.

Timeline and how to order

Setup takes 1 to 5 business days depending on integration complexity. Cost is determined individually after audit. We guarantee: all holds processed correctly, statuses synchronized, agents working. We'll assess your project within 24 hours. Contact us — we'll show case studies on live stores.

Why trust us with setup?

10+ years of commercial development on 1C-Bitrix. Certified specialists (Bitrix Certified). Over 50 successful holding implementations in stores with turnovers from 1 million RUB/month. Warranty: 12 months of support for changes in the sale module. Holding setup is not just a checkbox in admin — it's a guarantee that buyers' money won't be lost and refunds will be instant. Request an audit of your store — we'll check if holds are correctly configured. Contact us for a consultation on implementing two-stage payment.

What Professional 1C-Bitrix Installation Includes

We start by checking innodb_buffer_pool_size. The default MySQL value (128 MB) is a death sentence for an online store with a catalog of 10,000+ items. We set 70–80% of available RAM on a dedicated server, 50% on VPS. This single setting speeds up the site by 2–3 times compared to the default. We'll assess your project in one day — get a consultation. Contact us to order turnkey installation with performance guarantee.

How to Choose Hosting and Edition for 1C-Bitrix Installation?

BitrixVM is a virtual machine with a pre-installed stack: nginx + Apache, PHP-FPM, MySQL/MariaDB, Sphinx, Push server. For VPS — the best start. Everything is already configured for Bitrix, including OPcache, log rotation, and firewall. Management via web panel on port 8890. Bitrix documentation recommends starting with BitrixVM for predictable performance.

VPS/VDS is the sweet spot. Minimum configuration for a medium online store: 2 vCPU, 4 GB RAM, SSD. Optimal: 4 vCPU, 8 GB RAM. OS: Ubuntu 22.04 or Debian 12. If not BitrixVM, we configure the stack manually for the task. Virtual hosting — only for business cards and landing pages. Requirements: PHP 8.0+, MySQL 5.7+ / MariaDB 10.0+, 512 MB RAM, .htaccess. 1C-Bitrix hosting partners guarantee compatibility. Dedicated server — for highload. Typical architecture: web server separate, database separate, Redis/Memcached separate. For Enterprise edition — web cluster with load balancer. Cloud (Yandex Cloud, VK Cloud, Selectel) — when load spikes: sales, seasonal peaks. Autoscaling via Managed Kubernetes or simple VM vertical scaling.

Choosing the edition is equally important. A common mistake: choosing "Small Business" for a store that grows to B2B with wholesale prices and three warehouses in six months. Upgrading to "Business" — pay the difference, data is not lost, but it's better to plan ahead. Our specialists select the edition for current tasks and with room for growth. For example, the "Business" license (about 35,000 RUB) pays off through multi-warehouse and 1C exchange, while the wrong choice can lead to a loss of up to 30,000 RUB monthly on excess resources.

What Server Settings Are Critical for 1C-Bitrix?

Web Server and PHP

nginx as reverse proxy + Apache (mod_php) or nginx + PHP-FPM directly. The second option saves memory — Apache is not needed. But some Bitrix modules use .htaccess, so for compatibility we sometimes keep Apache. nginx configuration: fastcgi_read_timeout 300 — for long operations (1C import), client_max_body_size 1024m — large file uploads. Block access to .settings.php, .settings_extra.php, bitrix/.settings.php — they contain database passwords. Rewrite rules from urlrewrite.php — Bitrix generates them, but with nginx + PHP-FPM they need to be duplicated. PHP 8.0–8.2 with extensions: mbstring, curl, gd, xml, json, opcache, redis/memcached. Key php.ini settings: opcache.memory_consumption=256, opcache.max_accelerated_files=20000, max_execution_time=300, memory_limit=512M, upload_max_filesize=100M, post_max_size=128M.

Database and Caching

MySQL/MariaDB. Key my.cnf parameters: innodb_buffer_pool_size — 70–80% RAM, innodb_log_file_size=256M, tmp_table_size=256M, max_heap_table_size=256M, thread_pool_size — number of CPU cores. Encoding utf8mb4 mandatory, otherwise emoji and special characters break. Redis is preferable to Memcached for Bitrix — supports persistent connections and is more reliable. In production, Redis handles concurrent writes three times faster than Memcached under typical load. Configure in .settings_extra.php:

'cache' => ['value' => ['type' => ['class_name' => '\\Bitrix\\Main\\Data\\CacheEngineRedis']]]
'session' => ['value' => ['mode' => 'default', 'handlers' => ['general' => ['type' => 'redis']]]]

sudo apt install redis-server
sudo systemctl enable redis

SSL, Email, and Cron

SSL — Let's Encrypt via certbot in 90% of cases. Redirect HTTP → HTTPS (301), HSTS, TLS 1.2/1.3, OCSP Stapling. In Bitrix, switch to HTTPS in the main module settings. Email: abandon mail() — connect SMTP (Yandex.Mail for domain, Mail.ru for Business). Be sure to configure SPF, DKIM, DMARC. Without SPF, emails go to spam. Test deliverability via mail-tester.com — score 9+/10. Cron: Bitrix agents switch to system cron — * * * * * /usr/bin/php /var/www/bitrix/modules/main/tools/cron_events.php. Schedule 1C exchange (15–60 min), search reindex, backups (mysqldump + rsync, rotation 7+4), temporary file cleanup.

Security and Administration

File system: owner www-data, directories 755, files 644, upload 775. nginx blocks access to configuration files. Enable Bitrix Proactive Protection — WAF, activity control (block after 5 failed attempts), kernel integrity check. For admin panel: two-factor authentication via Google Authenticator or OTP, restrict access by IP via nginx for paranoid.

How Long Does 1C-Bitrix Installation and Configuration Take?

Post-Installation Checklist

1. Performance Monitor (/bitrix/admin/perfmon_panel.php) — aim for 30+ points. Below 20 means serious configuration issues.
2. System Check — automatic check of all parameters. Red items must be fixed, yellow — case by case.
3. Security Scanner — check for typical vulnerabilities.
4. PageSpeed Insights — TTFB < 200ms on VPS, LCP < 2.5s.
5. Test 1C exchange — if integration is planned, verify CommerceML exchange before launch.

Additionally, check software versions, caching settings, cron operation, SSL certificate, SPF/DKIM/DMARC, access rights, delete default users and pages. For projects with 54-FZ, ensure fiscalization is configured via OFD provider.

Deliverables

• Fully configured server for 1C-Bitrix with MySQL, PHP, nginx optimization.
• Installed and activated license of the required edition.
• SSL certificate, email settings, cron and backups.
• Documentation: all configuration parameters, access credentials, cron tasks.
• Content manager training: how to log into admin panel, add products, upload images.
• Post-installation support for 30 days — consultations on settings.

Why Trust Professionals with Installation?

Incorrect installation means lost time and money. We've seen projects where a store on "Start" couldn't handle 50 visitors because innodb_buffer_pool_size wasn't configured. After migrating to VPS with correct configuration, the site "flew". Incorrect configuration can cost 30,000 RUB monthly due to excessive resource consumption. You get a ready-made architecture that scales. Order turnkey 1C-Bitrix installation — get a reliable platform for business growth. Contact us for a free consultation: we'll calculate the cost and time for your project. Over 7 years of experience, 120+ Bitrix projects implemented, including highload stores with million-item catalogs. Get in touch — we'll help configure Bitrix for your project.