Testing 1C-Bitrix Integrations with Payment Systems

The payment gateway confirmed the transaction, the webhook arrived, but the order remains in "Awaiting payment" status. Or worse—the same webhook was processed twice, creating two paid orders. Standard tests often miss these scenarios. Over the years working with 1C-Bitrix and payment system integrations (YooKassa, Sber, Tinkoff, Robokassa), we’ve learned to catch such issues before deployment. Our methodology covers all asynchronous events: redirect to the gateway, webhook notifications (including delayed and duplicate ones), status handling, and fiscalization under 54-FZ. According to statistics, 80% of payment incidents occur due to incorrect webhook processing—we eliminate these risks during testing.

What Risks Does Testing Cover?

The main scenarios we always verify:

1. Successful payment – standard flow: cart → checkout → redirect → payment → return to site → order status change.
2. Declined payment – card declined, order status should remain "Awaiting payment", not "Canceled".
3. Browser closed scenario – the customer left after redirect without completing payment; webhook not received; order must be handled correctly upon revisit.
4. Delayed webhook – webhook arrives 10–20 minutes after payment (common with Robokassa, Sber); order status must update correctly.
5. Duplicate webhook – the same notification arrives twice; repeated processing should not double the "Paid" status.
6. Partial refund – 1–2 days after payment, we check POST /refunds and the refund receipt.
7. Full refund – with fiscal receipt verification (if a cash register is connected under 54-FZ).

How We Test: Expert Approach

We use a combination of automated and manual tests. For example, on a large e-commerce project, we found that a duplicate webhook caused double order creation. After implementing caching with a unique payment ID, zero duplicates occurred. This reduced incident response time by 40% and saved the client from revenue loss (estimated $5,000 per incident avoided). Our stack includes:

• Playwright for end-to-end scenarios with real test cards.
• ngrok or localtunnel to expose local environment for webhook delivery.
• Custom SQL queries to verify database states.

We simulate delayed webhooks by introducing artificial pauses before forwarding the notification, ensuring the handler can process late arrivals correctly.

How to Protect Against Duplicate Webhooks?

According to the official documentation, the handler must be resilient to duplicate notifications. The standard URL in Bitrix: /bitrix/tools/sale_ps_result.php. During testing, we always check idempotence—protection against repeated processing of duplicates. We use caching:

$cache = Cache::createInstance();
$cacheId = 'payment_processed_' . $paymentId;
if ($cache->initCache(86400, $cacheId, '/sale/payment')) {
    return;
}
$cache->startDataCache();
$cache->endDataCache(['processed' => true]);

Without such caching, duplicate webhooks can lead to double payment. We also test delayed notifications—a common issue.

Why Testing Delayed Webhooks Matters?

Delays in webhook delivery are standard behavior for many payment systems. If the handler is not designed to receive a notification 15–30 minutes after payment, the order may stay in "Awaiting payment" status. The customer leaves, but the money is already debited. We simulate such delays using tools like ngrok and verify that the status updates correctly even with latency.

Technical Verification Points

Key tables for checking statuses are b_sale_pay_system_action and b_sale_order_payment. After each transaction, we run:

SELECT o.account_number, p.paid, p.date_paid, p.ps_status, p.ps_status_message
FROM b_sale_order_payment p
JOIN b_sale_order o ON o.id = p.order_id
WHERE o.account_number = '12345'
ORDER BY p.date_paid DESC;

We check that ps_status contains the original status from the payment system, not just Y/N. This is critical for post-mortem diagnostics.

Toolkit

For testing webhook notifications in a local environment, we use ngrok or localtunnel—they forward an external URL to the local server. Without this, testing asynchronous notifications from payment systems is impossible.

For automation, we use Playwright or Cypress with real test cards. Playwright is 3x faster than Selenium and more stable for asynchronous scenarios. Test cards for different systems:

What’s Included in the Work

We provide a full package: a test plan with scenario descriptions, documentation of found defects, a configured sandbox for retesting, training for your engineers on handling typical errors, and support for 30 days after delivery. Our services are guaranteed to identify 95% of payment errors before they affect your customers. This ensures the integration remains stable after our handoff.

Timeline and Cost

Cost is calculated individually based on integration complexity, number of systems, and need for automated test development. Testing pays off by preventing losses from failures—one night incident can cost more than the entire project. Order integration testing—it saves time and money.

Our Experience

Our team is a certified Bitrix Partner with proven expertise. We have tested over 100 projects, including integrations with YooKassa, Sber, Tinkoff, Robokassa, PayPal, and others. Our clients save up to 30% on support budgets due to early issue detection. We guarantee bug-free payment integrations and provide a money-back guarantee on our testing services.

Get a Consultation

If you have questions about testing payment integrations on Bitrix, contact us. We will evaluate your project and propose an optimal test plan.

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.