Integrating Apple Pay with 1C-Bitrix

We often receive requests to implement Apple Pay in online stores on 1C-Bitrix. Apple Pay is not a separate payment system but an overlay on existing acquiring. Without a bank-acquirer or aggregator supporting Apple Pay, no payment will go through. Many developers underestimate the server part: Apple requires domain verification via a Merchant Identity Certificate, and without it the button won't appear no matter how well the JS code is written. Moreover, the payment session itself requires a three-way handshake between the user's browser, the store's server, and Apple's servers. Let's break down this process in detail.

Apple Developer documentation: "Before you can process payments, you must verify that you control the merchant's domain by uploading a domain association file."

Problems We Solve

Domain Verification in Apple Pay

1. The frontend checks availability: ApplePaySession.canMakePayments() — works only in Safari on Apple devices.
2. When a payment is initiated, the browser requests a Payment Session from the store's server.
3. The store server proxies the request to Apple using the Merchant Identity Certificate.
4. Apple verifies the domain → returns a session object.
5. The user confirms with Face ID/Touch ID → the browser receives an encrypted token.
6. The token is sent to the bank-acquirer to complete the transaction.

Steps 3–4 are critical — without server-side code, no button will work.

Why Direct Integration Takes Longer

With direct integration, you manage Apple certificates and sessions yourself. This gives full control but increases development time 2-3 times compared to an aggregator widget. A widget (CloudPayments, YooKassa) handles all server-side logic — just register the domain in your dashboard and add a few lines of JavaScript.

How We Do It (Proof of Expertise)

Preparing Merchant ID and Certificates

• Apple Developer Program account ($99/year) — to create Merchant ID and download certificates.
• Domain verification: file .well-known/apple-developer-merchantid-domain-association in the site root.
• Bank-acquirer or aggregator supporting Apple Pay.
• HTTPS — Apple Pay is unavailable without SSL.
• Configured 1C-Bitrix with the payment component sale.order.checkout.

Integration via Aggregator (Recommended Path)

If you already use CloudPayments or YooKassa, Apple Pay can be enabled through their widget. All server-side certificate handling is taken over by the aggregator:

// CloudPayments Widget
const cp = new cp.CloudPayments({ publicId: 'pk_XXXXXX' });

// Check availability
if (window.ApplePaySession && ApplePaySession.canMakePaymentsWithActiveCard('merchant.ru.shop')) {
    document.getElementById('apple-pay-btn').style.display = 'block';
}

document.getElementById('apple-pay-btn').addEventListener('click', () => {
    cp.pay('applepay', {
        description: 'Order #' + orderId,
        amount:      orderAmount,
        currency:    'RUB',
        invoiceId:   String(orderId),
        accountId:   customerEmail,
    }, {
        onSuccess: () => confirmOrderPaid(orderId),
        onFail:    (reason) => showError(reason),
    });
});

You need to register the domain in the aggregator's dashboard beforehand — it will automatically add the verification file. This is the fastest path: according to statistics, payment conversion increases by 10-15%.

Server-Side Domain Validation (Direct Integration)

If you need an implementation without an aggregator widget:

// local/api/apple-pay-validate.php
$validationUrl = filter_var($_POST['validationUrl'] ?? '', FILTER_VALIDATE_URL);

// Allow only Apple domains
if (!preg_match('#^https://apple-pay-gateway(-cert)?\.apple\.com#', $validationUrl)) {
    http_response_code(400); exit;
}

$ch = curl_init($validationUrl);
curl_setopt_array($ch, [
    CURLOPT_POST           => true,
    CURLOPT_POSTFIELDS     => json_encode([
        'merchantIdentifier' => 'merchant.ru.yourshop',
        'domainName'         => 'yourshop.ru',
        'displayName'        => 'Your Shop',
    ]),
    CURLOPT_SSLCERT        => APPLE_PAY_CERT_PATH,
    CURLOPT_SSLKEY         => APPLE_PAY_KEY_PATH,
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER     => ['Content-Type: application/json'],
]);
$response = curl_exec($ch);
curl_close($ch);

header('Content-Type: application/json');
echo $response;

JS Code on the Payment Page

const session = new ApplePaySession(3, {
    countryCode:          'RU',
    currencyCode:         'RUB',
    supportedNetworks:    ['visa', 'masterCard', 'mir'],
    merchantCapabilities: ['supports3DS'],
    total: { label: 'Your Store', amount: String(orderAmount) },
});

session.onvalidatemerchant = async ({ validationURL }) => {
    const resp = await fetch('/api/apple-pay-validate.php', {
        method: 'POST',
        body:   new URLSearchParams({ validationUrl: validationURL }),
    });
    session.completeMerchantValidation(await resp.json());
};

session.onpaymentauthorized = async ({ payment }) => {
    const result = await sendTokenToServer(payment.token);
    session.completePayment(
        result.success ? ApplePaySession.STATUS_SUCCESS : ApplePaySession.STATUS_FAILURE
    );
};

session.begin();

Adding to Bitrix

We add the button to the sale.order.checkout template. It is displayed only when canMakePayments() === true. After receiving the token, an AJAX call to a PHP handler sends the token to the bank and calls $payment->setPaid('Y'). Proper events are configured: after successful payment, redirect to the order page.

What We Do (Scope of Work)

• Registration of Merchant ID and certificate generation in Apple Developer.
• Placement of the domain verification file.
• HTTPS and SSL certificate setup (if needed).
• Integration with the chosen aggregator or direct server-side validation.
• Implementation of the Apple Pay button in the 1C-Bitrix payment template.
• Testing on real devices (iPhone, iPad, Mac).
• Documentation of the process for support.

Timelines

Contact us so we can evaluate your project and choose the optimal integration method. Request Apple Pay implementation — increase payment conversion by 10–15% without extra time investment. According to statistics, Apple Pay users spend 20% more than regular card payers.

We also recommend reviewing the Apple Pay documentation (original) and Wikipedia.

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.