Stripe Integration with 1C-Bitrix: Setup and Implementation

Stripe Integration with 1C-Bitrix: From Design to Deployment

A customer adds items to the cart, enters card details—and the page hangs. The payment doesn't go through, the order is lost, the client leaves for a competitor. This happens when a payment gateway integration with Bitrix is done hastily: no webhook handling, no signature verification, no idempotency. Stripe, as one of the most reliable payment systems, requires a careful connection with the CMS. We have completed over 50 successful Stripe integration projects with 1C-Bitrix—from startups to enterprise stores with turnovers in the hundreds of thousands of dollars. Each integration undergoes load testing and security checks.

Stripe covers the full cycle: card authorization, capture, refunds, subscriptions, 3D Secure. Works with Visa, Mastercard, AmEx, Apple Pay, Google Pay, and local methods (SEPA, iDEAL, Klarna). Stripe Checkout relieves the merchant of PCI DSS responsibility—all card data is processed on Stripe's side (Wikipedia: PCI DSS). Method availability depends on the merchant's country.

Choosing Between Checkout and Elements

For most Bitrix stores, we recommend Stripe Checkout. This approach is roughly 3 times simpler to implement—less code, automatic 3DS updates, and customers see a familiar Stripe interface. If you need full control over the payment form design, use Stripe Elements—it requires more server-side logic but offers flexibility. The choice depends on customization requirements and development time.

How to Integrate Stripe in Bitrix in 5 Steps?

1. Design—choose approach (Checkout or Elements), agree on refund and subscription scheme.
2. Develop handler—write a class extending \Bitrix\Sale\PaySystem\ServiceHandler, implement initiatePay(), processRequest(), refund().
3. Configure webhooks—register endpoint in Stripe Dashboard, subscribe to events. Must verify signature via Stripe-Signature.
4. Test—use test keys and card 4242 4242 4242 4242. Check successful payments, declines, refunds.
5. Deploy—switch to live keys, perform load testing. Timelines: Checkout—3–4 days, Elements—5–7 days.

All test transactions do not charge real funds. More details in Stripe documentation.

What's Included in the Stripe Integration

• Development of the payment system handler (class extending \Bitrix\Sale\PaySystem\ServiceHandler).
• Webhook configuration and idempotency checks.
• Implementation of full and partial refunds via \Stripe\Refund.
• 3D Secure support (Checkout includes it automatically).
• Apple Pay and Google Pay activation (domain verification via .well-known/apple-developer-merchantid-domain-association file).
• Testing on test and live keys.
• Full documentation and staff training.
• Guarantee of correct payment processing—all integrations undergo load testing.

Creating a Checkout Session

\Stripe\Stripe::setApiKey($secretKey);

$session = \Stripe\Checkout\Session::create([
    'payment_method_types' => ['card'],
    'line_items' => [[
        'price_data' => [
            'currency'     => 'eur',
            'unit_amount'  => $amountInCents,
            'product_data' => ['name' => 'Order No.' . $orderId],
        ],
        'quantity' => 1,
    ]],
    'mode'        => 'payment',
    'success_url' => $successUrl . '?session_id={CHECKOUT_SESSION_ID}',
    'failure_url' => $cancelUrl,
    'metadata'    => ['bitrix_order_id' => $orderId],
]);

{CHECKOUT_SESSION_ID} is a Stripe placeholder that substitutes the real ID. In processRequest(), we verify it against the order.

Handling Webhooks

Webhooks are more important than success_url—the customer may close the tab before redirect. Stripe sends checkout.session.completed regardless of browser behavior. More about webhooks on Wikipedia.

Mandatory checks:

1. Signature verification via the Stripe-Signature header—otherwise anyone could fake a payment.
2. Idempotency—check the current status in b_sale_order before changing order status.
3. Return 200 OK within 3 seconds—otherwise Stripe will retry delivery.

Subscribe to events: checkout.session.completed, payment_intent.payment_failed, charge.refunded. More details in Stripe documentation.

$payload = @file_get_contents('php://input');
$sigHeader = $_SERVER['HTTP_STRIPE_SIGNATURE'];
$event = \Stripe\Webhook::constructEvent($payload, $sigHeader, $endpointSecret);

if ($event->type === 'checkout.session.completed') {
    $session = $event->data->object;
    $orderId = $session->metadata->bitrix_order_id;
    // Order status update logic
}

Refunds and Partial Refunds

$refund = \Stripe\Refund::create([
    'payment_intent' => $paymentIntentId,
    'amount'         => $refundAmountInCents,
    'reason'         => 'requested_by_customer',
]);

Stripe allows multiple partial refunds up to the full transaction amount.

Checkout vs Elements Comparison

Based on our data, Checkout saves up to 40% of development and testing time. If you are unsure which to choose, contact us—we will select the best option for your budget and timeline.

Timelines

Settings in Bitrix Admin Panel

Why Stripe is the Optimal Solution for Bitrix?

Over 50 completed payment system integrations. Many years of experience with Bitrix—since the platform's early versions. We guarantee: after deployment, payments run smoothly, refunds work correctly, and you receive full documentation. Contact us for a consultation—we will assess your project and offer the best solution. Order an audit of your current system or development from scratch.

Pricing and Savings

Typical integration cost starts from €500 for Checkout and €800 for Elements. Our clients save up to 40% on development time compared to custom solutions. Checkout is 3 times better than Elements in terms of implementation effort. For a seamless Stripe Bitrix integration, ensure you handle Stripe webhooks correctly. This combination of Stripe and Bitrix provides a robust payment system.

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.