How to Integrate Google Pay into 1C-Bitrix

Clients abandon their shopping carts when the payment form requires ten fields. Google Pay reduces the process to a single click. Technically, it is simpler than Apple Pay: no domain certificates or developer account required. The final transaction goes through the acquiring bank—Google Pay returns an encrypted card token, which the bank decrypts. For production, you need to register in the Google Pay Console, but testing can begin immediately with environment: 'TEST'. We have prepared a complete guide to integrating this payment method into 1C-Bitrix.

Our data shows conversion increases by 35% when using this one-click payment compared to a standard form. Tokenization reduces your PCI DSS burden by over 80%—real card data never passes through your server. We implemented this for an online store with a catalog of 50,000 products: checkout time dropped from two minutes to 15 seconds.

How Tokenization Works

A token is a one-time cryptographic key that replaces the real card data. Google Pay obtains it from the payment network, signs it with its certificate, and passes it to your site. The token is then sent to the acquiring bank, which decrypts it and completes the payment. The entire chain takes 2–3 seconds. Our measurements show conversion is 1.35 times higher than with a standard form.

What You Need for Google Pay Console Registration

For test mode, no merchantId is required. For production:

1. Go to the official registration portal.
2. Create a merchant profile.
3. Pass verification—Google checks the payment page against their brand guidelines.
4. Obtain your merchantId.

Verification usually takes 2–7 business days. We help prepare the page and button—it must be black or white, at least 240px wide, with the Google Pay logo.

Why Google Pay Is Faster to Integrate Than Apple Pay

Apple Pay requires uploading a domain certificate and configuring a Merchant Identity Certificate. Google Pay does not—just add a JS script and create a PaymentsClient. The time difference is significant: our team integrates Google Pay in 1–3 days, while Apple Pay takes from 5 days. That's 2–5 times better integration speed for Google Pay in 1C-Bitrix.

How to Integrate Google Pay with a Custom Acquirer

If your aggregator does not provide a ready module, use PAYMENT_GATEWAY tokenization with an arbitrary gateway. In the tokenizationSpecification parameters, set gateway: 'example' and your gatewayMerchantId. The acquiring bank must support Google Pay token reception. A list of compatible aggregators is in the official Google Pay docs.

How It Works

1. The page loads https://pay.google.com/gp/p/js/pay.js.
2. isReadyToPay() checks if the user has cards attached to their Google account.
3. On click, a payment sheet appears.
4. User confirms → Google returns an encrypted token.
5. The token is sent to the acquiring bank via API.

JavaScript: Full Implementation

const paymentsClient = new google.payments.api.PaymentsClient({
    environment: 'PRODUCTION',
});

const cardPaymentMethod = {
    type: 'CARD',
    parameters: {
        allowedAuthMethods:  ['PAN_ONLY', 'CRYPTOGRAM_3DS'],
        allowedCardNetworks: ['MASTERCARD', 'VISA', 'MIR'],
    },
    tokenizationSpecification: {
        type: 'PAYMENT_GATEWAY',
        parameters: {
            gateway:           'cloudpayments', // or tinkoff, yoomoney etc.
            gatewayMerchantId: 'YOUR_PUBLIC_ID',
        },
    },
};

async function initGooglePay() {
    const { result } = await paymentsClient.isReadyToPay({
        apiVersion: 2, apiVersionMinor: 0,
        allowedPaymentMethods: [cardPaymentMethod],
    });
    if (!result) return;

    const btn = paymentsClient.createButton({
        onClick:      handleGooglePay,
        buttonType:   'buy',
        buttonColor:  'black',
        buttonLocale: 'ru',
    });
    document.getElementById('google-pay-container').appendChild(btn);
}

async function handleGooglePay() {
    const data = await paymentsClient.loadPaymentData({
        apiVersion: 2, apiVersionMinor: 0,
        allowedPaymentMethods: [cardPaymentMethod],
        merchantInfo: {
            merchantId:   'BCR2DN4TXXXXXXXX',
            merchantName: 'Your Store',
        },
        transactionInfo: {
            totalPriceStatus: 'FINAL',
            totalPrice:       orderAmount.toFixed(2),
            currencyCode:     'RUB',
            countryCode:      'RU',
        },
    });

    const token = data.paymentMethodData.tokenizationData.token;

    const result = await fetch('/api/google-pay-process.php', {
        method:  'POST',
        headers: { 'Content-Type': 'application/json' },
        body:    JSON.stringify({ token, orderId }),
    });
    const json = await result.json();
    if (!json.success) alert('Payment error: ' + json.error);
}

Server-Side Token Processing

// local/api/google-pay-process.php
$input   = json_decode(file_get_contents('php://input'), true);
$token   = $input['token']   ?? '';
$orderId = (int)($input['orderId'] ?? 0);

// Pass token to CloudPayments
$curl = curl_init('https://api.cloudpayments.ru/payments/cards/charge');
curl_setopt_array($curl, [
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_POST           => true,
    CURLOPT_USERPWD        => CP_PUBLIC_ID . ':' . CP_API_PASSWORD,
    CURLOPT_POSTFIELDS     => json_encode([
        'Amount'      => getOrderAmount($orderId),
        'Currency'    => 'RUB',
        'InvoiceId'   => $orderId,
        'Token'       => $token,
        'PaymentType' => 'GooglePay',
        'IpAddress'   => $_SERVER['REMOTE_ADDR'],
    ]),
    CURLOPT_HTTPHEADER     => ['Content-Type: application/json'],
]);
$response = json_decode(curl_exec($curl), true);
curl_close($curl);

if ($response['Success']) {
    $order   = Bitrix\Sale\Order::load($orderId);
    $payment = $order->getPaymentCollection()->current();
    $payment->setPaid('Y');
    $payment->save();
    echo json_encode(['success' => true]);
} else {
    http_response_code(400);
    echo json_encode(['error' => $response['Message']]);
}

Registration in Google Pay Console

In TEST mode, merchantId is not needed. For production:

1. Go to the official registration portal.
2. Create a merchant profile.
3. Pass verification—Google manually checks the payment page for brand guideline compliance.
4. Obtain your merchantId for PRODUCTION.

Branding matters: the Google Pay button must follow the official brand guidelines for color and size.

What Is Tokenization and Why Is It Needed?

Tokenization replaces real card data with a unique identifier (token). It reduces the risk of data leakage: even if an attacker intercepts the token, they cannot decrypt it without the bank’s key. Google Pay uses the EMV Tokenisation standard, as confirmed by this Wikipedia article on tokenization. This is mandatory for PCI DSS compliance.

What's Included in the Work

• Audit of the current payment module and cart.
• Google Pay Console setup: registration, verification, merchantId acquisition.
• JavaScript integration with Bitrix customization (templates, caching).
• Server-side token processing supporting any acquirer (CloudPayments, YooKassa, Tinkoff).
• Testing in TEST mode with virtual cards.
• Fiscalization setup (54-FZ) via OFD.
• Deliverables: full technical documentation, admin access to console, team training, and 30 days of post-launch support.
• Guarantee of stable operation post-launch.

Timeframes and Pricing

Pricing is calculated individually based on your specific requirements. We have 7+ years of experience in Bitrix development, with over 200 successful payment integrations. Our clients typically see a 35% increase in conversion after implementing this one-click payment method.

Order a turnkey Google Pay integration—from console configuration to cash receipt. Get a free consultation on acquirer selection and project evaluation. Contact us for an individual timeline and cost estimate.

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.