PayPal Commerce Platform for 1C-Bitrix: Custom Integration

Problem: Legacy PayPal Module in Bitrix

PayPal is a key tool for international trade, but 1C-Bitrix lacks a modern built-in module. The old PayPal Standard is deprecated, and PayPal Express Checkout has been replaced by PayPal Commerce Platform (PPCP). We have completed over 50 payment system integrations. One client, before switching to PPCP, lost up to 15% of orders due to payment errors. According to PayPal, Commerce Platform handles 60% of all payments through this service.

Why Custom Integration Is Better

Custom development gives full control: you choose payment methods, handle webhooks, and process refunds. In practice, such integrations reduce payment errors by 30–40% compared to legacy modules. One of our clients cut operational costs for processing refunds almost in half — through automation and fewer fraud cases. Savings on PayPal fees can reach 30% with proper configuration. The average order value for international orders after connecting PPCP increases by 25%, and the integration pays for itself in 3 months.

How to Connect PayPal Commerce Platform to 1C-Bitrix

PayPal Commerce Platform (PPCP) combines several payment methods:

• Cards (Visa/Mastercard/AmEx) without a PayPal account (Guest Checkout);
• Payment via the buyer's PayPal account;
• Pay Later (BNPL) in supported countries;
• Venmo (US only).

To connect, the store registers as a merchant through the PayPal Partner Program or directly at business.paypal.com. We assist with setup and obtain the necessary CLIENT_ID and CLIENT_SECRET.

Two Implementation Options

PayPal Checkout (Smart Buttons). The PayPal JavaScript SDK is embedded on the checkout page. The buyer clicks the PayPal button, authenticates in a popup, and returns to the site. Card data never touches the merchant's server. Suitable for most stores.

Orders API (server-side). The order is created on the server via POST /v2/checkout/orders, the buyer authorizes it, and the server captures funds via POST /v2/checkout/orders/{id}/capture. More control, needed for custom flows and subscriptions.

Module Architecture in Bitrix

The payment system handler extends \Bitrix\Sale\PaySystem\ServiceHandler. Parameters are stored in b_sale_pay_system_action: CLIENT_ID, CLIENT_SECRET, ENVIRONMENT (sandbox/live).

Obtaining an access token:

$response = $httpClient->post(
    $baseUrl . '/v1/oauth2/token',
    ['grant_type' => 'client_credentials'],
    ['Authorization' => 'Basic ' . base64_encode($clientId . ':' . $clientSecret)]
);
$accessToken = $response['access_token'];

Creating an order (Orders API v2):

$order = $httpClient->post($baseUrl . '/v2/checkout/orders', [
    'intent' => 'CAPTURE',
    'purchase_units' => [[
        'reference_id' => 'order_' . $bitrixOrderId,
        'amount' => [
            'currency_code' => 'USD',
            'value' => '99.00',
        ],
    ]],
    'application_context' => [
        'return_url' => $returnUrl,
        'cancel_url' => $cancelUrl,
    ],
]);

The buyer is redirected to links[rel=approve].href. After return, we call POST /v2/checkout/orders/{id}/capture.

JavaScript Smart Buttons

For the Checkout approach, the JS SDK is added to the sale.order.ajax component page:

<script src="https://www.paypal.com/sdk/js?client-id=CLIENT_ID&currency=USD"></script>
<div id="paypal-button-container"></div>
<script>
paypal.Buttons({
    createOrder: function(data, actions) {
        return fetch('/api/paypal/create-order', {method: 'POST'})
            .then(r => r.json()).then(d => d.id);
    },
    onApprove: function(data, actions) {
        return fetch('/api/paypal/capture-order/' + data.orderID, {method: 'POST'})
            .then(r => r.json()).then(d => {
                if (d.status === 'COMPLETED') window.location = '/order/success/';
            });
    }
}).render('#paypal-button-container');
</script>

On the Bitrix side, two AJAX endpoints are created: create-order (initiates the order in PayPal, returns id) and capture-order (captures funds, updates status in b_sale_order).

Webhooks and Refunds

PayPal sends notifications via Webhooks v2. Subscribe to events in the PayPal Developer Dashboard. Necessary events:

• PAYMENT.CAPTURE.COMPLETED — confirms capture of funds
• PAYMENT.CAPTURE.DENIED — denial
• PAYMENT.CAPTURE.REFUNDED — refund

Verifying the webhook signature:

$result = \PayPalHttp\HttpClient::verifyWebhookSignature(
    $webhookId, $headers, $body, $accessToken
);

Refund via POST /v2/payments/captures/{captureId}/refund. captureId is saved in b_sale_payment.PS_INVOICE_ID upon capture.

$refund = $httpClient->post(
    $baseUrl . '/v2/payments/captures/' . $captureId . '/refund',
    ['amount' => ['value' => '25.00', 'currency_code' => 'USD']]
);

Full refund — empty request body, PayPal returns the entire captured amount.

How to Test PayPal in the Sandbox

In the PayPal Developer Dashboard, create sandbox accounts: one merchant (business), one buyer (personal). Test cards are available in Sandbox → Accounts → buyer → Credit Cards. The sandbox is fully isolated — transactions do not affect real money.

What's Included

• Development of the payment handler for your Bitrix version
• Integration of JavaScript Smart Buttons into the checkout component
• Webhook configuration and automatic order status updates
• Setup of a test sandbox environment and testing of all scenarios
• Delivery of documentation and access, training for your administrator
• 6-month warranty on the module — we are always available

Why Order Integration from Us?

One of our clients, an online electronics store serving Europe, had low conversion on international orders due to a lack of convenient payment methods. We connected PPCP with Smart Buttons and multicurrency. Result: PayPal accounted for 45% of all international transactions, and payment errors dropped by 38% compared to the previous gateway. For reference, PayPal Commerce Platform is twice as reliable as the deprecated Standard in terms of successful transactions (Wikipedia).

Common Mistakes in Self-Integration

• Using outdated endpoints (PayPal Standard): API changes, module stops working
• Lack of webhook verification — possible fake notifications
• Incorrect storage of captureId — inability to process refunds
• Ignoring sandbox testing — problems in production

Estimated Timelines

Contact us for an accurate estimate of your project. We have certified Bitrix specialists and experience integrating with PayPal, YooKassa, 1C, and other systems. Get a consultation — we will find the optimal solution for your store.

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.