Full-cycle B2B payment in 1C-Bitrix

B2B clients don't pay with cards — they need an official invoice with a stamp and company details. Without automation, a manager has to manually issue an invoice, wait for confirmation from accounting, and mark the payment. This takes hours, and errors lead to delays. In 1C-Bitrix, you can set up a complete cycle: from collecting buyer's requisites to automatic confirmation of receipt to the current account. Our experience — over 7 years of development, dozens of projects with B2B payment. We use proven patterns — order user properties, bank REST APIs, PDF generation via FPDF. Result: payment processing time is reduced from two days to 20 minutes, operational costs drop by 70%. Non-cash payment is the standard method for B2B payments. In Bitrix, it is implemented by the built-in payment system Cash/BankTransfer, according to the official documentation.

Standard B2B payment flow

1. The legal entity buyer places an order and selects "Payment by invoice".
2. The system generates an invoice with seller's requisites.
3. The buyer's accountant creates a payment order in the bank.
4. Money arrives at the seller's current account.
5. The manager or bank integration records the payment in Bitrix.

How to configure the "Bank Transfer" payment system in Bitrix?

Bitrix has a standard handler Cash / BankTransfer. Configure it in Store → Settings → Payment systems. Enter your company details: name, INN, KPP, current account, BIK, bank. Add instructions for the buyer — text that the client will see after selecting the payment method.

// Bank transfer payment parameters (entered in the admin section)
// Logo, name, instruction text for buyer

// In the payment system template — display requisites
<div class="bank-details">
    <p>Bank: Sberbank PJSC</p>
    <p>BIK: 044525225</p>
    <p>Account: 40702810XXXXXXX</p>
    <p>Corr. account: 30101810400000000225</p>
    <p>INN: XXXXXXXXXX</p>
    <p>KPP: XXXXXXXX</p>
    <p>Payment purpose: Payment for invoice No.<?= $order->getAccountNumber() ?></p>
</div>

// Adding order properties via Bitrix API
// local/php_interface/init.php or setup script

use Bitrix\Sale\Internals\OrderPropsTable;

$props = [
    ['NAME' => 'Company Name', 'CODE' => 'COMPANY_NAME', 'TYPE' => 'STRING'],
    ['NAME' => 'INN',          'CODE' => 'INN',          'TYPE' => 'STRING'],
    ['NAME' => 'KPP',          'CODE' => 'KPP',          'TYPE' => 'STRING'],
    ['NAME' => 'Legal Address','CODE' => 'LEGAL_ADDRESS','TYPE' => 'STRING'],
    ['NAME' => 'Bank Account', 'CODE' => 'BANK_ACCOUNT', 'TYPE' => 'STRING'],
    ['NAME' => 'Bank Name',    'CODE' => 'BANK_NAME',    'TYPE' => 'STRING'],
    ['NAME' => 'BIK',          'CODE' => 'BANK_BIK',    'TYPE' => 'STRING'],
];

Why automatic payment confirmation is critical

Manual payment marking is a source of delays. The accountant may forget, the manager may make a mistake. Automation solves the problem: payment received — order immediately moves to paid status. Options:

• 1C integration — if using 1C:Accounting, incoming payments are automatically synchronized with orders via the exchange module. It's reliable but requires configuring scheduled tasks.
• Bank client API — many banks (Sberbank, Tochka, Modulbank) provide APIs for reading statements. When a payment with the correct purpose appears, we automatically update the order status:

// Example: parsing Sberbank statement (SimpleBankStatementParser)
$statement = parseBankStatement($statementXml);

foreach ($statement->getTransactions() as $transaction) {
    if ($transaction->getType() !== 'credit') continue;

    // Find order number in payment purpose
    preg_match('/№(\w+-\d+)/', $transaction->getPurpose(), $matches);
    if (!isset($matches[1])) continue;

    $orderNumber = $matches[1];
    $order = getOrderByAccountNumber($orderNumber);

    if ($order && abs($order->getPrice() - $transaction->getAmount()) < 0.01) {
        setOrderPaid($order->getId(), $transaction->getDate());
    }
}

This approach requires customizing the parser for the specific bank format, but it pays off by removing human error. The savings on manual handling of one payment are substantial.

Real case: how we cut payment processing from 8 hours to 30 minutes

On one project with 200+ B2B orders per month, the manager spent half a day manually checking the current account and marking payments. We integrated the bank API and 1C. Result: payment confirmation now happens automatically in 30 minutes on average. The manager's workload dropped to zero for this task, and errors completely disappeared. The client saved about 80 hours of work per month.

How to generate PDF invoice for legal entities

After an order is placed, a legal entity needs an official PDF invoice. Bitrix does not generate PDF "out of the box" — we add third-party libraries. We use FPDF or mPDF:

// Invoice generation via FPDF or mPDF
function generateInvoicePdf(Bitrix\Sale\Order $order): string
{
    $pdf = new FPDF();
    $pdf->AddPage();
    $pdf->SetFont('Arial', 'B', 14);
    $pdf->Cell(0, 10, 'INVOICE No. ' . $order->getAccountNumber(), 0, 1, 'C');

    // Seller's requisites
    // Product table
    // Total and signatures

    $path = '/tmp/invoice_' . $order->getId() . '.pdf';
    $pdf->Output('F', $path);
    return $path;
}

The invoice is generated at the moment of order placement and sent to the buyer by email. Additionally, we save it to the file system for re-downloading from the personal account.

Comparison of manual and automatic payment processing

Automation processes payments 10 times faster than manual marking.

Turnkey setup process

1. Analytics — we analyze the workflow, identify integration points.
2. Design — architecture of the payment module, tool selection (HL-blocks for requisites, agents for processing).
3. Implementation — configure payment system, collect requisites, generate PDF, integrate with bank API or 1C.
4. Testing — verify all scenarios: successful payment, errors, refunds, partial payment.
5. Deployment — roll out to production, train managers.

Timelines

Total timeline — from 4 to 10 days, depending on complexity and integration needs.

How we guarantee results

We formalize all agreements in a technical specification. After delivery, you get full access to the code, an operation manual, and support for one month. Order turnkey setup — shorten your payment processing time. Get a consultation on your project — we'll suggest the optimal solution.

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.