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¤cy=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.
| Scenario | How to Test |
|---|---|
| Successful payment | Sandbox personal account, balance > order amount |
| Insufficient funds | Sandbox account with zero balance |
| Buyer cancellation | Close the PayPal popup, check cancel_url |
| Refund | Via API after successful capture |
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
| Option | Scope | Timeline |
|---|---|---|
| Smart Buttons + capture | Module + JS widget + testing | 4–6 days |
| Fully server-side (Orders API) | No JS dependency, only API | 4–5 days |
| + Subscriptions | Recurring billing via Subscriptions API | +3–4 days |
| + Multicurrency | Currency selection logic, PayPal configuration | +1–2 days |
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.







