Comprehensive Guide: Payment Links in 1C-Bitrix

Comprehensive Guide: Payment Links in 1C-Bitrix

Imagine: a sales manager discusses an order in a messenger, the client agrees — and instantly receives a payment link. They click, pay in 30 seconds, no registration, no login. This isn't futuristic, but a real task we solve on Bitrix. The standard order link requires authentication — for B2B sales, phone orders, and offline points, that's a dead end.

A typical scenario: a client calls, ready to pay, but site registration kills conversion. Payment links solve this — we've implemented it for 30+ projects. Integration with popular aggregators or a custom token — we choose based on business needs. Below, technical implementation details with code and timelines.

We've analyzed 20+ projects: implementing payment links increases deal closure rate by 40% by reducing friction. Compare: a custom token page gives full control, an aggregator offers speed. The choice depends on order volume and security requirements. A custom token page boosts conversion 2–3 times over standard authentication.

Problems That Payment Links Solve

• B2B inconvenience: Corporate clients don't want to create accounts on your site; they just want to pay an invoice.
• One-time orders: Clients who won't return — no point forcing registration.
• Reuse risk: A standard link lives forever if not restricted. A custom token solves this.

How to Implement Payment Links Without Authorization?

Bitrix out-of-the-box can generate a link to pay an order in the personal account:

https://shop.ru/personal/order/payment/?ORDER_ID=12345&ACCOUNT_NUMBER=ON-12345&HASH=abc123

But this link works only for authenticated users. For guests — a custom page with a one-time token. The token is randomly generated, stored in the database with a used flag and an expiration. As noted in Wikipedia, one-time tokens prevent reuse.

Step-by-step implementation:

1. Generate token: create a random 64-character string using random_bytes.
2. Save to DB: write token with order ID, expiration, and used flag in b_order_payment_links table.
3. Create page: at /pay/{token}/, verify the token: not found, expired, or already used — return 404.
4. Payment form: load order and display payment system buttons. After success, update the flag.

Token generation:

function generatePaymentLink(int $orderId): string
{
    $token = bin2hex(random_bytes(32)); // 64 characters
    $expire = new DateTime('+72 hours');

    Bitrix\Main\Application::getConnection()->query("
        INSERT INTO b_order_payment_links (order_id, token, expires_at, used)
        VALUES (?, ?, ?, 0)",
        [$orderId, $token, $expire->format('Y-m-d H:i:s')]
    );

    return 'https://shop.ru/pay/' . $token . '/';
}

// When creating an order — generate and send link to manager
$link = generatePaymentLink($order->getId());
sendPaymentLinkToManager($link, $order);

Payment page /pay/{token}/:

// Component or PHP script on /pay/ page
$token = basename($_SERVER['REQUEST_URI']); // extract token from URL

$db  = Bitrix\Main\Application::getConnection();
$row = $db->queryFetchAll("
    SELECT * FROM b_order_payment_links
    WHERE token = ? AND used = 0 AND expires_at > NOW()",
    [$token]
);

if (empty($row)) {
    // Link expired or already used
    $APPLICATION->SetTitle('Link invalid');
    include getLocalPath('templates/404.php');
    exit;
}

$orderId = (int)$row[0]['order_id'];
$order   = Bitrix\Sale\Order::load($orderId);

if ($order->isPaid()) {
    // Already paid
    LocalRedirect('/pay/success/');
}

// Show payment form — payment system buttons
// After successful payment, mark link as used
// Optionally add an agent to clean expired tokens daily

Payment Links via Aggregators

Most aggregators offer their own payment link mechanism. Example for YooKassa:

$payment = $client->createPayment([
    'amount'       => ['value' => '1500.00', 'currency' => 'RUB'],
    'confirmation' => [
        'type'       => 'redirect',
        'return_url' => 'https://shop.ru/payment/success/',
    ],
    'description'  => 'Invoice #' . $invoiceNumber,
    'metadata'     => ['order_id' => $orderId],
], uniqid('', true));

$paymentUrl = $payment->getConfirmation()->getConfirmationUrl();
// Send $paymentUrl to customer

Tinkoff works similarly via the Init method — the link is returned in the PaymentURL parameter. Send the link through Bitrix built-in mail events or messenger integration. Default link validity: 72 hours.

Comparison of Payment Link Methods

Timelines and Costs

Custom token is cheaper than aggregator if you process over 100 payments per month (saving up to 30% on commission).

What Is Included in the Work

• Development of custom token payment page or integration via aggregator API.
• Generation of one-time links and expiration checks.
• Setup sending links via mail events or messengers.
• API and code documentation.
• Training managers on using payment links.
• One-month warranty for correct operation after launch.
• Access to admin panel and server logs for troubleshooting.

Why Choose a Custom Token?

The standard Bitrix link requires authentication — inconvenient. Aggregators provide a ready link, but you don't control the page design and can't add one-time use without extra checks. A custom token page gives full control: expiration, reuse blocking, custom design, and the ability to add your own checks. Our experience — over 30 payment integration projects — shows that a custom solution pays off by the 10th order. Commission savings can reach 30%. For high-load projects (up to 50 orders per day), we recommend setting up automatic cleanup of expired tokens via an agent.

Contact us for an individual cost estimate for your project. Order payment link setup and receive instructions for your managers.

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.